> ## Documentation Index
> Fetch the complete documentation index at: https://embedded-apps.rollout.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Implementation plan

> The steps from first call to a live marketplace, and who on your team does each.

Adding the marketplace takes one backend endpoint, two components on your
pages, and a few settings. Here's the path, in order.

**1. 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 →](https://embedded-apps.rollout.com/build/set-up.md)

**2. 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 →](https://embedded-apps.rollout.com/build/set-up.md#configure-your-marketplace)

**3. 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 →](https://embedded-apps.rollout.com/build/user-tokens.md)

**4. Show the apps on your contact page**

Mount `mountEmbeddedApps()` where the apps should go, such as an Apps tab.

[Show apps on a contact →](https://embedded-apps.rollout.com/build/show-apps.md)

**5. 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 →](https://embedded-apps.rollout.com/build/add-the-marketplace.md)

**6. Review the apps publishers list**

Approve the apps you want your users to have, with a live preview of each.

[Review apps →](https://embedded-apps.rollout.com/build/review-apps.md)

## Who does what

| Step | Who usually does it |
| - | - |
| Get set up, configure the marketplace | Product, with Rollout |
| Mint user tokens | A backend engineer |
| Show the apps, add the marketplace | A frontend engineer |
| Review apps | Product, or whoever owns partnerships |

## 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](https://embedded-apps.rollout.com/build/show-apps.md#your-pages-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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.