> 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/sharing-and-collaboration/sharing-a-map.md).

# Sharing a map

{% 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 [Managing members](/administration/managing-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="/files/xbr7Z7GPaNthk5d8Zlp8" 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 [Workspaces and projects](/administration/workspaces-and-projects.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 [Managing members](/administration/managing-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="/files/tBz5ZitJYVGALnlxJiig" 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

You can set a default view that workspace members land on when opening the map. This ensures the map opens to a certain location and zoom level by default:

**Felt Menu** (top-left) → **View** → **Set current view as default**

<figure><img src="/files/dBu2M3dg1lK0QqYazrHK" alt="" width="375"><figcaption></figcaption></figure>

When copying a map link through the **Share** menu using the **Copy link** button (bottom-right corner), the link automatically includes some URL parameters that point to your current view. Take the following URL:

<https://felt.com/map/Kontur-Population-yiQAmRZ9CTTK49CHfYp9AauvC?loc=32.55,23.37,3.26z>

The **loc** parameter specifies the center coordinates of the center of the view and the **z** parameter at the end of the URL indicates the level of zoom.

Using these parameters, you can share specific views of your map with people, or even embed different views of a same map on your website.

## Troubleshooting

If you or someone you share the map with sees a "This browser or computer isn't supported" error message when opening a map:

<figure><img src="/files/MC1WFYQQfuihOKA4fG9g" alt="" width="365"><figcaption></figcaption></figure>

This is due to either:

1. WebGL not being enabled on the browser (most common)
2. The device or browser not supporting WebGL

To verify and fix:

1. Go to <https://get.webgl.org/> to verify WebGL is enabled. If enabled, you should see a spinning cube on this page:

<figure><img src="/files/7RB2ROC06D092oZboqGb" alt="" width="375"><figcaption></figcaption></figure>

2. Confirm graphics/hardware acceleration is enabled for your browser. Search “Enable WebGL in \[browser + version]” to find the location of the setting.
   1. Chrome: available in chrome://settings/system

      <figure><img src="/files/20r28Fg6suW5LASNlysS" alt=""><figcaption></figcaption></figure>
   2. Firefox: available in performance settings: <https://support.mozilla.org/en-US/kb/performance-settings>.


---

# 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/sharing-and-collaboration/sharing-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.