Skip to main content

Get set up

Rollout sets up each marketplace owner. Contact Rollout, and we’ll:
  • turn on the Marketplace section of your Rollout dashboard, and
  • create your marketplace, tied to your CRM.
Then collect three values from the dashboard: You don’t need the Universal API to run a marketplace. The Marketplace section has three tabs: Listings, your review queue; Apps, the apps you’ve approved; and Settings.

Configure your marketplace

On Marketplace → Settings:

Pages that may show the apps

  • Each line is reduced to its origin: scheme, host, and port when it isn’t the default. Pasting a page’s full URL works. Wildcards are refused.
  • Add each environment you use, such as https://app.example.com and https://staging.example.com.
  • Use https. http is accepted only on localhost and 127.0.0.1, for development.
A page whose origin isn’t listed gets no error from Rollout: the browser refuses to load the Rollout frame, and logs a frame-ancestors violation in its console.

Who can turn apps on

If you stop allowing a scope, the page warns you with how many users or orgs have any app on in your marketplace. They keep the apps they have on and can still turn them off, but no one can turn on more apps in that scope. The Settings tab also shows both components’ snippets, already filled in with your marketplace id, and the token claims your server signs.

Next

Mint user tokens on your server.