> For the complete documentation index, see [llms.txt](https://helpdesk.smaply.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.smaply.app/account-and-team/billing-and-plans/how-to-check-seat-usage.md).

# How to check seat usage

See at a glance how many seats your account has used, who's holding them, and how many are left. The Account settings **Users** tab carries a seat summary, and a detailed view breaks usage down by access level.

{% hint style="warning" icon="list-check" %}

#### Prerequisites

You need Admin permissions at the account level. The seat views live in Account settings.
{% endhint %}

{% hint style="info" icon="clipboard-list" %}

#### In this guide

1. [Read the seat summary](#read-the-seat-summary)
2. [Open the detailed seat allocation view](#open-the-detailed-seat-allocation-view)
3. [How seats are counted](#how-seats-are-counted)
   {% endhint %}

#### Read the seat summary

The seat summary sits at the top of the **Users** tab in **Account settings**, which opens from the account name at the top of the left sidebar. **User seat allocation** shows **Seats used** as a count out of your total allocation, the number of seats remaining, and a breakdown of who's using them.

<figure><img src="/files/2K8HmRy8ZAE6WwqFXeFw" alt="Account settings with the Users tab selected. A User seat allocation panel shows Seats used as a count out of the total, with Account, Workspace only, Map only, and Pending tiles, and a seats-remaining line with a View seat allocation button."><figcaption><p>Account settings > Users tab, seat summary</p></figcaption></figure>

The four tiles split your used seats by where each person's access sits:

* **Account** - People with admin or editor access across the whole account.
* **Workspace only** - People with admin or editor access scoped to specific workspaces, but not the whole account.
* **Map only** - People with admin or editor access scoped to specific journey maps, but not a workspace or the account.
* **Pending** - People you've invited who haven't accepted yet. They don't use a seat until they accept.

#### Open the detailed seat allocation view

To see exactly who holds each seat, click **View seat allocation**. The detailed view repeats the summary at the top, then lists people in a section per access level. Each person shows their name, email, joined date, access level, role, and status.

<figure><img src="/files/jYfsbaXZJzx1nxltmkiN" alt="The seat allocation detail view. Below the seat summary are sections for Account user seat allocation, Workspace user seat allocation, and Journey map user seat allocation, each listing name, email, joined date, access, role, and status. A Viewer license management section at the bottom shows viewer licenses used with Account viewers, Workspace viewers, and Pending invitations tiles."><figcaption><p>Seat allocation detail view</p></figcaption></figure>

* **Account user seat allocation** - People with admin or editor access on the whole account.
* **Workspace user seat allocation** - People with admin or editor access on specific workspaces.
* **Journey map user seat allocation** - People with admin or editor access on specific journey maps.
* **Viewer license management** - Sits at the bottom and tracks viewers separately. Viewer licenses are counted out of their own allocation, split into **Account viewers**, **Workspace viewers**, and **Pending invitations**.

A section with no one in it shows an empty state rather than a table, so you can tell at a glance which access levels are in use.

#### How seats are counted

Only admins and editors count toward your seat allocation. A person uses one seat no matter how many levels they have access to: an account admin who is also an editor on three workspaces and two journey maps still counts as one seat, at their highest level. Inviting someone to a single journey map still uses a seat once they accept, so map-level access isn't free.

A seat is counted once the person accepts their invitation, not while it's pending. If your used count looks lower than the number of people you've invited, check the **Pending** tile.

{% hint style="info" icon="tag" %}
Viewers are a separate license type and don't count toward your admin and editor seats. How many viewer seats you have depends on your plan.
{% endhint %}

Viewers can view journey maps and add comments, but can't edit content. To bring people in or change what they can do, see [How to invite users](/account-and-team/users-and-roles/how-to-invite-users.md) and [Access levels and permissions](/account-and-team/users-and-roles/access-levels-and-permissions.md). To change how many seats your account has, see [How to upgrade or downgrade](/account-and-team/billing-and-plans/how-to-upgrade-or-downgrade.md).

#### Related topics

<table data-column-title-hidden data-view="cards"><thead><tr><th>Article</th><th>What it covers</th><th data-hidden data-card-target data-type="content-ref">Target</th></tr></thead><tbody><tr><td><strong>How to invite users</strong></td><td>Add people at the account, workspace, or journey map level and pick their role.</td><td><a href="/pages/F1Nzd1jlynqOnRaG0WSM">/pages/F1Nzd1jlynqOnRaG0WSM</a></td></tr><tr><td><strong>Access levels and permissions</strong></td><td>What Admin, Editor, and Viewer can do, and how account access cascades to workspaces and maps.</td><td><a href="/pages/escpmNlj3DUgMgLSjGAl">/pages/escpmNlj3DUgMgLSjGAl</a></td></tr><tr><td><strong>How to upgrade or downgrade</strong></td><td>Change your plan and the number of seats your account has.</td><td><a href="/pages/0SirL7EgmpC7vVsowZHs">/pages/0SirL7EgmpC7vVsowZHs</a></td></tr><tr><td><strong>What is included in each plan</strong></td><td>Feature and seat availability by plan tier, including viewer seats.</td><td><a href="/pages/cVo65js50L1JDRFJTSTu">/pages/cVo65js50L1JDRFJTSTu</a></td></tr></tbody></table>


---

# 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://helpdesk.smaply.app/account-and-team/billing-and-plans/how-to-check-seat-usage.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.