Get set up
Rollout creates your marketplace and turns on its section of your Rollout
dashboard. You get your client id, client secret and marketplace id.Set up your marketplace →
Configure your marketplace
Name and describe it for publishers, choose who it’s open to, whether
agents, admins or both can turn apps on, and which of your pages may show
the apps.Set up your marketplace →
Mint user tokens
Add endpoints on your server that sign a short-lived token for the user
signed in to your CRM: one per contact for the apps, one for the
marketplace.Mint user tokens →
Show the apps on your contact page
Mount
mountEmbeddedApps() where the apps should go, such as an Apps tab.Show apps on a contact →Add the marketplace
Mount
mountEmbeddedAppMarketplace() on a settings page, so users can turn
apps on, or build your own on the marketplace API.Add the marketplace →Review the apps publishers list
Approve the apps you want your users to have, with a live preview of each.Review apps →
Who does what
Before you start
- You don’t need the Universal API. The marketplace works on its own.
- Your pages need to load scripts and frames from Rollout’s origin. If you
send a
Content-Security-Policy, see Your page’s Content Security Policy. - Each user and org needs a stable id. The apps a user or org turns on are stored against the ids you put in their tokens.
Launch checklist
- Your production and staging origins are listed under Pages that may show the apps.
- Every token carries the user’s org, the render token included, if your marketplace lets admins turn apps on for their org.
- Your token endpoint checks that the user may see the contact before it signs a token for it.
- Only your org admins get
embed:enable_org. - You’ve approved at least one app, and turned it on for a test user.
- Your contact page shows something useful when a user has no apps on, such as a link to the marketplace.