> ## 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.

# Set up your marketplace

> Get your marketplace created, and choose who it's open to, who can turn apps on, and where they show.

## Get set up

Rollout sets up each marketplace owner. [Contact Rollout](mailto:support@rollout.com),
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:

| Value | Where | Used by |
| - | - | - |
| **Client id** (your tenant id) | The **API** page | Your server, as each token's `iss` |
| **Client secret** | The **API** page | Your server, to sign each token. Keep it on your server. |
| **Marketplace id** | **Marketplace → Settings** | The components, and the marketplace API |

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**:

| Setting | What it does |
| - | - |
| **Name**, **Description** | What app publishers see when they browse marketplaces to list an app in. Up to 100 and 5,000 characters. |
| **Visibility** | **Public**: any app publisher on Rollout can list an app, and you review each listing. **Invite only**: hidden from app publishers, except those already listed in it. |
| **Who your users can enable apps for** | **For themselves** (`user`): a user turns an app on for their own account. **For their org** (`org`): an org admin turns an app on for everyone in their org. Choose at least one. |
| **Pages that may show the apps** | The origins of every page that mounts Rollout's components, one per line, for example `https://app.example.com`. Rollout refuses to render in any other page. |

### 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](https://embedded-apps.rollout.com/build/user-tokens.md) on your server.


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