> 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/maps/map-settings.md).
# Map settings
Set or remove map constraints for bounds and zoom. Use Map settings to add a description and control viewer permissions.
Use Map settings to limit a map's area or zoom range, add a description, and control what people without Edit access can do.
1. Open the map and click **Edit map** in the toolbar at the top right of the map.
2. Click **Map settings**  in the toolbar. The panel opens on the right.
## Map constraints
Map constraints keep everyone within an area, a zoom range, or both.
1. In **Map settings**, under **Map constraints**, click **Add constraints**. A rectangle appears on the map.
2. Under **Bounds**, drag the rectangle and its corners to cover the area people can see.
3. Optional: Under **Zoom**, enter a **Min zoom** and a **Max zoom**, from 1 to 23.
4. Click **Save**.
To choose where the map opens while letting people pan and zoom freely, set the default view instead. See [Set the default view](/maps/navigate-the-map.md#set-the-default-view).
### Change or remove map constraints
To change or remove a Felt map's constraints, open **Map settings**. Under **Map constraints**:
* To change them, click **Edit constraints**, make your changes, and click **Save**.
* To remove them, click the trash icon next to **Edit constraints**. People can pan and zoom anywhere again.
## Description
Enter the map's purpose, sources, or date in **Description**. The text appears at the top of the legend for everyone. To remove it, delete the text.
## Table settings
Table settings in Map settings control whether people without Edit access can open a layer's table. See [Table](/tools/table.md).
| Setting | What it does | Default |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------ | -------- |
| **Viewers can open table** | People can open layer tables from the legend. | On |
| **Open table by default** | The selected layer's table opens when someone opens the map. Available only when **Viewers can open table** is on. | No layer |
## Viewer permissions
Viewer permissions in Map settings control what people with View or Contribute access, and people viewing a public Felt map, can do.
| Setting | What it allows | Default |
| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- |
| **Duplicate map and data** | People can copy the map and its data into a workspace where they have a seat, or copy its layers to a map they can edit. See [Duplicate and move maps](/maps/duplicate-and-move-maps.md). | On |
| **See map presence** | People see the avatars of others on the map. People with Contribute or Edit access also see live cursors when they aren't editing. | On |
### Let viewers export data
{% hint style="success" %}
Available on the Enterprise plan. [Talk to sales](https://felt.com/sales)
{% endhint %}
The **Export data** setting lets logged-in people without Edit access, and people viewing an [authenticated embed](/developers/authenticated-embeds.md), export a Felt map's layers from the legend. The setting is off by default. To turn it on, open **Map settings** and, under **Viewer permissions**, turn on **Export data**. People with Edit access can always export, and people viewing a public link without logging in can't. See [Export data](/export-and-print/export-data.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/maps/map-settings.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.
