> 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/plans-and-billing/seats-and-viewers.md).

# Seats and viewers

Learn who needs a seat and what viewers can do for free. Add or reassign seats in your Felt workspace.

You need a seat to create maps, upload or edit data, capture field data, work offline, or use Felt AI. One kind of seat covers field, office, and admin work. People without a seat are viewers, who can view and comment for free on every plan.

Each plan includes a number of seats and viewers. You can add seats to a paid plan. The amounts and seat prices are on the [Felt pricing page](https://felt.com/pricing).

## Seats and access

Access determines what someone can do on each map, project, data source, or workspace. Admin, Edit, and Contribute access need a seat, and View access doesn't. See [Permissions](/administration/permissions.md).

A seat belongs to the workspace, not to a person, so an admin can reassign it to whoever needs it next. See [Reassign a seat](#reassign-a-seat).

## Viewers

Viewers don't have a seat. They can view and comment on maps shared with them for free. How viewers count depends on how you share:

* Public maps need no login, and public viewing doesn't count toward your viewer limit. Each load counts toward your [map views](/plans-and-billing/plan-usage.md).
* Private maps need a free Felt account. Everyone added to the workspace, a project, or a map without a seat counts as one of the workspace's viewers, including external collaborators.

At the viewer limit, you can't invite more viewers. An admin can remove viewers to make room. See [Manage members](/administration/manage-members.md).

## Reassign a seat

To reassign a seat, you need Admin access to the workspace.

1. Click your workspace name in the sidebar, then click **Workspace settings**.
2. Click the **Members** tab.
3. In the **Seat type** column, click the entry for the person who no longer needs a seat, and select **Viewer**. The seat is now available to reassign.
4. In the **Seat type** column, click the entry for the person who needs the seat, and select **Seat**.

To remove someone from the workspace, which also frees their seat, see [Manage members](/administration/manage-members.md).

## Add seats

To add seats, you need Admin access to the workspace.

1. Go to [felt.com/maps/latest/billing](https://felt.com/maps/latest/billing), or click your workspace name in the sidebar, click **Workspace settings**, and click the **Billing** tab.
2. In the **Seats** section, click **Manage seats**.

When every seat is assigned, giving someone a seat shows *You’ve run out of seats*. To free one up, [reassign a seat](#reassign-a-seat).


---

# 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/plans-and-billing/seats-and-viewers.md?ask=<question>&goal=<user_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.