> For the complete documentation index, see [llms.txt](https://help.felt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.felt.com/developers/authenticated-embeds.md).

# Authenticated embeds

Embed private Felt maps in your site or app. Use REST API embed tokens or restrict access to people invited to the map.

Embed a private Felt map on your website, portal, or application with either embed tokens or Felt invitations. For a map anyone can open, use a [public embed](/share/embed-a-map.md).

| Detail                | Embed token                                 | Invited people                                  |
| --------------------- | ------------------------------------------- | ----------------------------------------------- |
| Who can see the map   | Anyone your server gives a token to         | People logged in to Felt with access to the map |
| Felt account needed   | No                                          | Yes, a free account is enough                   |
| How long access lasts | 12 hours per token                          | Until you remove their access                   |
| Setup                 | Code on your server that calls the REST API | The map's share settings                        |
| Plan                  | Platform add-on                             | Team plan and up                                |

## Embed a map with a token

{% hint style="success" %}
Available with the Platform add-on. [Compare plans](https://felt.com/pricing#compare)
{% endhint %}

An embed token lets one visitor view a private embedded map without having a Felt account or joining your workspace. Your server creates the token with the [REST API](/developers/rest-api.md), using an [API token](/developers/rest-api.md#create-an-api-token) that can view the map. The Platform add-on includes this API access.

1. In Felt, open the map in edit mode. In the toolbar, click **Developer Platform** > **Copy map ID**.
2. On your server, call the REST API's create embed token endpoint with the map ID and the visitor's email address. Felt uses the email address for tracking.
3. On the visitor's page, add the token to the embed URL as the `token` query parameter, for example `https://felt.com/embed/map/{mapId}?token={token}`.

The [embed tokens reference](https://developers.felt.com/rest-api/api-reference/embed-tokens) has the request and response.

{% hint style="warning" %}
Create embed tokens on your server, never in the page itself. Creating them in the page would expose your API token to anyone who opens the page.
{% endhint %}

An embed token gives view access to one map for 12 hours. When it expires, the embed asks the visitor to refresh, so get a new token on every page load. Visitors with a token can't edit or comment, and each load of the map counts as a map view. See [Plan usage](/plans-and-billing/plan-usage.md).

Visitors with a token can export the map's data only if the map's **Export data** setting is on. See [Map settings](/maps/map-settings.md).

## Embed a map for invited people

An embed for invited people shows the map only to people who are logged in to Felt and have access to it.

1. On the map, click **Share** at the top right.
2. Click the **Public access** selector and select **None**.
3. In **Emails**, enter the email address of each person who should see the map. Each address must match the one on that person's Felt account.
4. Click **Invite**.
5. Copy the embed code and add it to your site. See [Embed a map](/share/embed-a-map.md).

People you invite need a free Felt account, and people without a seat count as viewers. See [Seats and viewers](/plans-and-billing/seats-and-viewers.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.felt.com/developers/authenticated-embeds.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.