> 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/upload-anything/felt-servers.md).
# Felt Servers
Publish layers to a Felt Server and reuse them across maps. Data edits and refreshes stay synced wherever the layers appear.
{% hint style="success" %}
Available on the Business and Enterprise plans. [Compare plans](https://felt.com/pricing#compare)
{% endhint %}
A Felt Server lets your workspace reuse layers across maps. Publish a layer from a map or upload a file to the server, then add it to other maps. Data edits and refreshes reach every synced copy; each map keeps its own styles, filters, legend settings, and components.
For public datasets that Felt curates, see [Global Library](/upload-anything/global-library.md).
## Publish a layer to a Felt Server
Publishing a layer needs Edit access to the Felt Server and to the map. Publishing adds the layer to a Felt Server and keeps the map's layer synced to it.
1. On the map, click **Edit map** in the toolbar.
2. In the legend, click the **···** menu on the layer and click **Publish…**.
3. Under **Publish to**, select a Felt Server, and optionally a folder in it.
4. Click **Publish**.
You can also select the layer and click **Publish to Felt Server**, the rocket icon at the top of the detail panel. To publish several layers at once, select them in the legend before you open the menu or click the icon.
## Upload data to a Felt Server
You can add files or URLs to a Felt Server without putting them on a map first.
1. Click **Data sources** in the toolbar, then select the Felt Server.
2. In the server's header, click **Upload**.
3. Click **Upload file** to choose files from your computer, or **From URL** to add data hosted at a URL.
Felt Server uploads accept the same [file types](/upload-anything/files/supported-file-types.md) (including ZIP files) and [URLs](/upload-anything/urls.md) as map uploads, with the same [Data limits](/upload-anything/data-limits.md).
## Add a Felt Server layer to a map
Adding a Felt Server layer to a map needs View access to the Felt Server and Edit access to the map.
1. On the map, click **Data sources** in the toolbar.
2. Select the Felt Server in the dialog's sidebar.
3. Find the layer and click **Add to map**. The layer appears on the map, synced to the Felt Server.
To add a copy that doesn't sync, open the layer, click the arrow next to **Add to map**, turn off **Sync**, and click **Add to map**. To start a new map from a layer, open it on the workspace home page and click **Create map**.
## Real-time sync
By default, a layer syncs with a Felt Server when you publish it to the server or add it from the server to a map.
* Synced across maps: features, attribute values, and columns. Deleting a column removes it from every map, and Felt asks you to confirm when other maps use it.
* Set per map: the layer's name, styling, filters, legend settings, and dashboard components.
* Refreshes: a Felt Server layer doesn't refresh on a schedule. Clicking **Refresh** or **Upload new version** in a synced layer's **Data** tab updates the layer in the Felt Server, so every synced map gets the new data. The update also replaces edits made on every map. See [Refresh data](/upload-anything/refresh-data.md).
* Snapshots: raster layers, tile layers, and layers that refresh on a schedule (with **Live** on) don't sync. Publishing or adding one makes a copy.
* Access: synced edits need Edit access to the Felt Server. With View access, you see updates but can't make synced edits.
* Duplicates: a copy of a synced layer, or of a map with one, stays synced within the same workspace. See [How copies stay in step](/layers/copy-and-duplicate-layers.md#how-copies-stay-in-step).
* Offline: Field App edits made offline sync when you're back online. See [Work offline](/field-app/work-offline.md).
A synced layer shows a green sync badge in the legend, and its **Data** tab shows **Status** as **Real-time sync**. To see which maps use a layer, open it in the Felt Server and open **Synced to** in the **Metadata** tab.
To stop syncing a layer on one map, open its **Data** tab and turn off **Sync**. The layer keeps its data as an ordinary map layer, and other maps aren't affected.
## Organize a Felt Server
Open a Felt Server to rename, move, export, or delete its layers and folders.
* Click the **···** menu on a layer or folder, or right-click it, to see its actions.
* Click **New folder** in the server's header to create a folder, or right-click a folder and click **New subfolder**.
* Drag layers or folders onto a folder to move them. **Cmd**-click (Mac) or **Ctrl**-click (Windows) to select several layers.
{% hint style="danger" %}
Deleting a layer, a folder, or a whole Felt Server permanently deletes its layers from the server. Maps that use them keep their layers and data, but sync turns off.
{% endhint %}
## Share and manage a Felt Server
To give people access, click **Share** in the server's header, then invite them with **Source admin**, **Edit**, or **View** access, or set a default for the workspace. To rename the server, change its description, or delete it, click **Settings** in the server's header.
## Create another Felt Server
{% hint style="success" %}
Available on the Enterprise plan. [Talk to sales](https://felt.com/sales)
{% endhint %}
A workspace can have several Felt Servers, each with its own sharing settings. For example, you can have one that only the operations team can edit.
1. On the workspace home page, click **+** next to **Data sources**.
2. In the dialog, click **Felt Server**.
3. Enter a name and an optional description, then click **Create**.
---
# 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/upload-anything/felt-servers.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.
