> 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 maps with custom permission settings and public or private access.

{% embed url="<https://40056855.fs1.hubspotusercontent-na1.net/hubfs/40056855/Share_HelpCenter.mp4>" %}

## Share menu

{% hint style="info" %}
Looking to manage share and control permissions for your entire org? See [Manage members](/administration/manage-members.md)
{% endhint %}

To share your map, click on the **Share** button on the top-right corner of your map.

From this menu you can:

* invite collaborators directly via email,
* control public access to the map, or
* *(draft maps only)* adjust the access level for all workspace members.

<figure><img src="https://217108486-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmRfGitkyjOEMvVsEyGWN%2Fuploads%2FIRN2C1KMyIsOuUxhGoSk%2FScreenshot%202026-03-05%20at%203.13.49%E2%80%AFPM.png?alt=media&amp;token=ba313d75-8ddc-4f0a-a77f-2cef07ff62a0" alt="" width="375"><figcaption></figcaption></figure>

### Sharing across the workspace

To share maps between teammates, move maps into Projects in the workspace. Projects control which teammates have access to which maps, and Projects can be set to public (to everyone in the workspace) or private. See [Organize maps](/maps/organize-maps.md) for more information.

Members in the same workspace can access maps in public projects and maps in private projects they're invited to.

Project Admin can set the default permission for all members with access to the project. The default permission for each project can be set as: View, Contribute, and Edit.

This default permission will override the member's permission if the default permission grants a lower access level than a member's workspace permission.

For example, if a public project's default is set to **View**, every member's permission will be View in that project:

* A member with **Edit** workspace permission will see the project maps with **View** permission.
* A member with **Contribute** workspace permission will see the project maps with **View** permission.
* A member with **View** workspace permission (or a Viewer seat) will see the project maps with **View** permission.

See [Manage members](/administration/manage-members.md#workspace-permissions) for more info.

### Invite collaborators by email

You can also invite external collaborators or existing workspace members to specific projects and maps. External collaborators can only see maps they’ve been invited to.

### Control public access

Public access sets the baseline permission for your map. It's what anyone gets if they haven't been given access another way, either by a direct invite to the map or through a project or workspace.

<figure><img src="https://217108486-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmRfGitkyjOEMvVsEyGWN%2Fuploads%2Fx1gprbHDWgVXNYgT7q1X%2FScreenshot%202026-07-22%20at%2011.36.45%E2%80%AFAM.png?alt=media&amp;token=2676fe77-96c0-4e0b-866e-bd2055c0d0d7" alt=""><figcaption></figcaption></figure>

| Setting  | Description                                                                                                              |
| -------- | ------------------------------------------------------------------------------------------------------------------------ |
| **None** | Only members directly invited to the map or who have access via the workspace can view the map. The most secure setting. |
| **View** | Anyone with the link can view.                                                                                           |

*On some legacy plans you may also see a **View and comment** option — anyone with the link can view and place location-based comments (requires a Felt login). On current plans, posting comments requires a Full Access seat.*

## Setting your map view

To set the view a map opens to, or share a link to a specific view, see [Setting your map view](/maps/navigate-the-map.md#setting-your-map-view).

## Linking to a feature

To point someone at one feature rather than an area, click the feature to open its popup, open the popup's **···** menu, and choose **Copy link to feature**. This works for a feature in a vector layer and for a pixel in a raster layer.

<figure><img src="https://217108486-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmRfGitkyjOEMvVsEyGWN%2Fuploads%2Fgit-blob-cf7e8f26399a24e4d70ae4b2debdb38ffdd93d4f%2Fcopy-link-to-feature.png?alt=media" alt="" width="439"><figcaption></figcaption></figure>

Opening the link loads the map, flies to the feature, and opens its popup. The recipient doesn't need to be logged in, so this works for anyone you share a public map with.

If the feature can't be found — the layer is hidden or has been removed from the map, or a raster layer doesn't cover that spot — the map opens without the popup and a message explains why.

## Troubleshooting

If a map shows "This browser or computer isn't supported", see [System requirements](/administration/system-requirements.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.felt.com/share/share-a-map.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.