# Felt Servers

A **Felt Server** is a Felt-managed catalog of map layers your workspace can reuse. It sits alongside your external connections — Cloud sources like Postgres or Snowflake, with the same sharing options and permission model. While external sources connect to data that lives elsewhere, a Felt Server is where your published, styled, ready-to-reuse layers live inside of Felt.

When you publish a layer from a map, it lands in a Felt Server with its style, components, and metadata intact, and becomes available as a layer anyone with access can drop onto another map.

{% hint style="success" %}
Felt Servers are available on all paid plans. **Professional** includes one Felt Server; **Enterprise** allows unlimited Felt Servers. See the [pricing page](https://felt.com/pricing) for details.
{% endhint %}

<figure><img src="/files/20YkScOlu1vYJIAsEoPd" alt=""><figcaption></figcaption></figure>

## Multiple servers

A default Felt Server is created automatically with every new paid workspace. Enterprise workspaces can have more than one Felt Server — for example, one for operations, one for infrastructure, one for public-facing assets — each with its own content and sharing settings. To create a new server:

1. From the workspace homepage, click **+** next to **Data sources**.
2. In the **New data source** dialog, choose **Native** → **Felt Server**.
3. Give it a name and an optional description, then click **Create**.

## Folders

Use folders to organize the contents of your Felt Server. To create a folder:

* **Create a folder** — click **New folder** in the server's header.
* **Rename or delete a folder** — **...** menu on the folder. Deleting a folder removes the layers it includes from the server.

## Publishing to a Felt Server

From a map in edit mode:

1. Click the **...** menu on any layer in the legend and choose **Publish…** (or click the rocket icon in the layer panel).
2. In the **Publish to Felt Server** dialog, set the layer's name and description.
3. Pick a **Felt Server** and optionally a **folder** within it.
4. Click **Publish**.

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

### Felt Server layer contents

* **Layer data** — the underlying dataset travels with the layer. The same data is referenced on each map that uses the layer.
* **Styling** — all visual styling (colors, symbols, stroke weights, opacity) expressed as [Felt Style Language](/layers/styling.md) (FSL).
* **Components** — any dashboard components configured for the layer and their settings.
* **Metadata** — the layer's name and description from the **Info** tab appear in the catalog.
* **Thumbnail** — an auto-generated preview based on the layer's bounding box.

## Using a Felt Server layer

Any workspace member with access to the server can add its layers to their maps:

1. Open a map and click ![](/files/qv8POfyKJ00VfTgugMR2) in the toolbar.
2. Pick the Felt Server from the sidebar.
3. Find the layer and click **Add to map**.

Restyling or re-filtering the layer on a map doesn't affect the published layer, and edits to the published layer don't affect the data on other maps.

## Sharing a Felt Server

Click **Share** in the server's header to open the Share dialog. Invite members by email, pick a role (**Source admin**, **Edit**, **View**), or set a workspace-wide default for all members. Read more about sharing at [Sharing a data source](/sharing-and-collaboration/sharing-a-data-source.md).

## Server settings

Click **Settings** in the server's header to rename the server, edit its description, or delete it.

Deleting a server cascades to every folder and layer inside it. Layers already placed on maps are not affected.


---

# Agent Instructions: 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:

```
GET https://help.felt.com/data-sources/felt-servers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.