> 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/administration/licenses.md).

# Seats

Felt uses a simple seat model: **Full Access seats** for people who create and edit, and **Viewer seats** for everyone else. Seats set the ceiling on what someone can do in your workspace; [permissions](/administration/felt-permissions.md) determine what they can do on a specific project, map, or data source.

## Seat types

<table data-header-hidden><thead><tr><th width="180"></th><th></th></tr></thead><tbody><tr><td><strong>Full Access</strong></td><td>Required to create maps, upload data, edit layers, or contribute changes. 10 Full Access seats are included on the Professional plan. Enterprise plans scale to your organization.</td></tr><tr><td><strong>Viewer</strong></td><td>Free. Viewers can open maps shared with them, browse data, and read comments. They can't edit, upload, or create maps.</td></tr></tbody></table>

## Seats vs. permissions

Seats are workspace-level. Permissions are granular and apply to a specific project, map, or data source.

* **Seat** = "Do you have a paid seat in this workspace?" (Full Access or Viewer)
* **Permission** = "What can you do on this specific project / map / data source?" (View, Contribute, Edit, or Admin)

A Full Access seat can be granted **any** permission level. For example, an analyst with a Full Access seat might have **Edit** access on the Operations project but **View** access on the Marketing project. The seat is the ceiling; permissions decide where they sit beneath it.

For the full permission matrix — what each permission level can do at the workspace, project, map, and data source level — see [Permissions](/administration/felt-permissions.md).

## Admin access

Admin is granted on top of a Full Access seat. Admins manage workspace settings, members, and billing. There must always be at least one Admin in the workspace.

## Switching a member’s seat

Workspace Admins can change member seats on the [members page](https://felt.com/maps/latest/members). For step-by-step instructions on inviting members and assigning seats, see [Managing members](/administration/managing-members.md).

## Commenting

Posting comments requires a Full Access seat — any member with a Full Access seat can comment, even on maps where they only have View permission. Viewer seats can read comments on maps they're shared with but can't post them. *(Workspaces on some legacy plans still allow Viewer seats to comment; if yours is one, nothing changes for you.)*


---

# 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/administration/licenses.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.