> 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/share/share-a-map.md).
# Share a map
Share a Felt map by email or public link. Give invited people View, Contribute, or Edit access.
Click **Share** at the top right of a Felt map to invite people or turn on public link access. Anyone who can open the map can click **Copy link**.
## Share menu
The **Share** menu on a Felt map lets you [invite people by email](#invite-people-by-email), [set public link access](#set-public-link-access), copy the map's link with **Copy link**, or [embed the map](/share/embed-a-map.md) with **Embed**.
## Invite people by email
1. Click **Share** at the top right of the map.
2. In **Emails**, enter one or more email addresses.
3. Select an access level: **View**, **Contribute**, or **Edit**.
4. Click **Invite**. Felt emails each person a link to the map.
| Access | What people can do on the map |
| ---------- | ----------------------------------------------------------------------------------- |
| View | Open the map, use the legend and tools, and comment |
| Contribute | Everything in View, plus add and edit features and draw annotations |
| Edit | Everything in Contribute, plus add and style layers, upload data, and share the map |
People with Contribute or Edit access need a seat. People with View access don't. See [Seats and viewers](/plans-and-billing/seats-and-viewers.md) and [Permissions](/administration/permissions.md).
Invited people log in, or sign up for a free Felt account, with the email address you invited.
To change or remove someone's access, open the **Share** menu, click the access level next to their name, and select a new level or **Remove**.
## Set public link access
Public link access controls what people can do without an invitation. It doesn't reduce any access they already have through an invitation, project, or workspace. You need Edit access to change it.
1. Click **Share** at the top right of the map.
2. Click the **Public access** selector.
3. Select **None**, **View**, or **View and comment**.
| Public access | Who can open the map |
| ---------------- | ------------------------------------------------------------------------------- |
| None | Only people invited to the map, or with access through its project or workspace |
| View | Anyone with the link, without logging in |
| View and comment | Anyone with the link, without logging in. Logged-in people can also comment. |
{% hint style="warning" %}
With **View** or **View and comment**, anyone with the link can open the map, including anyone who receives a forwarded link. Search engines can find a map whose link is posted publicly. Set public link access to **None** for maps only invited people should see.
{% endhint %}
To check what people with the link see, open it in a private browser window.
## Let anyone with the link comment or edit
Public link access has no edit option. With **View and comment**, people with the link can comment but not edit.
* To let anyone with the link comment, set public link access to **View and comment**. People need a free Felt account to post. A comment marks a place on the map; it doesn't draw a shape. See [Comments](/share/comments.md).
* To let people add features, draw annotations, or edit layers, invite each person by email with Contribute or Edit access. Both access levels need a seat. See [Invite people by email](#invite-people-by-email).
## Share with your workspace
To share maps with your workspace, move them into a project. Everyone with access to the project can open its maps. People who get access through the workspace can do no more than the project's default access allows. See [Organize maps](/maps/organize-maps.md).
## Link to a feature or view
A Felt feature link takes people to a specific feature on the map and opens its popup.
1. Click the feature on the map to open its popup.
2. In the popup, open the **ยทยทยท** menu.
3. Click **Copy link to feature**.
**Copy link** in the **Share** menu saves your current view in the link. To set the view a map opens to, or share a link to a specific view, see [Set the default view](/maps/navigate-the-map.md#set-the-default-view).
## Troubleshooting
### A person can't open a map you shared
* Invite the email address the person uses to log in to Felt.
* For people you didn't invite, set public link access to **View** or **View and comment**.
* If the workspace has used all its map views for the month, people outside the workspace see *Map view limit reached*. See [Plan usage](/plans-and-billing/plan-usage.md).
### Map shows "This browser or computer isn't supported"
The browser or device can't run WebGL. See [System requirements](/administration/system-requirements.md) to turn WebGL on or find a supported browser.
### A feature link shows "The feature was not found in layer"
The link points to a feature that's no longer in the layer. The feature was deleted, or the layer's data was replaced, for example with **Upload new version**, which can give features new IDs. Copy a fresh link from the feature's popup.
---
# 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/share/share-a-map.md?ask=&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.
