> ## Documentation Index
> Fetch the complete documentation index at: https://docs.openwhispr.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Seats — adding, removing and what counts

> What uses up a seat, how to buy more, and how seats come back when people leave.

A workspace buys a number of seats, and each person who can use OpenWhispr
through the workspace holds one. **Settings → Workspace** under **Account**
shows where you stand, on the Members tab: *"4 of 5 seats used."*

## What consumes a seat

* **Every member.** Owner, admin or member — by default they all hold a seat.
* **Every invitation you've sent that hasn't been accepted yet.** This is the one
  that surprises people. A pending invite reserves its seat so the person has
  somewhere to land when they accept. Revoke it, or let it expire, and the seat
  comes back.

**Admins can be given access without a seat.** When you invite someone as an
admin, you can mark them as admin-only, and they'll manage the workspace without
consuming paid capacity — useful for an IT or ops person who administers
OpenWhispr but doesn't dictate. This is available for the admin role only;
regular members always hold a seat.

## Adding seats

If you're out of capacity, inviting someone fails with a message telling you to
add seats first. To add them: open the workspace billing card in **Settings →
Workspace**, and use **Add seat**.

Before it goes through, OpenWhispr shows you the new capacity and the exact
**Charge today** — the change is prorated, so you pay for the rest of the
current period rather than a full month.

A workspace can hold up to **500 seats**. If you need more than that, talk to us
about Enterprise.

## Removing seats

**Seats are released automatically.** Remove a member, revoke a pending
invitation, or have someone leave the workspace, and the workspace's seat count
drops to match — you stop paying for capacity you're not using, without having
to remember to adjust anything.

Because of that there's no "remove a seat" button: seats follow the people. What
you can't do is set the number *below* the seats currently in use — free up the
seat first by removing the person, and the count follows.

## FAQ

<AccordionGroup>
  <Accordion title="I removed someone but the seat count hasn't changed.">
    It updates once Stripe confirms. If it's still wrong after a few minutes,
    tell us — that's a bug worth knowing about.
  </Accordion>

  <Accordion title="I invited someone and immediately ran out of seats.">
    Pending invitations hold their seat. Revoke any invites that aren't going to
    be accepted and the capacity comes straight back.
  </Accordion>

  <Accordion title="Do I get a refund when a seat is released mid-month?">
    The unused portion becomes credit on the workspace's account and comes off
    the next invoice, rather than going back to the card.
  </Accordion>

  <Accordion title="Can a member hold a seat in two workspaces?">
    Yes. Seats are per workspace, and each workspace bills for its own.
  </Accordion>
</AccordionGroup>

<Snippet file="still-need-help.mdx" />

## Related

* [Billing for a team](/help/account/workspace-billing)
* [Why can't I manage billing?](/help/account/who-pays-for-my-plan)
* [Transferring or deleting a workspace](/help/account/transfer-or-delete-a-workspace)