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

# Workspaces in Pilot Status — Shared Accounts for Teams

> A workspace is the account your team shares: its numbers, its conversations, its bill. Learn how one person can belong to several workspaces and switch between them.

A **workspace** is the account itself: the numbers connected to it, the conversations that arrive on them, the templates, the API keys, and the invoice at the end of the month. Everything in Pilot Status belongs to exactly one workspace.

Before workspaces, an account was one person. Now an account is a **place**, and people are invited into it.

## One person, several workspaces

The same login can belong to more than one workspace — your own, plus every workspace that invited you. A workspace switcher in the header tells you which one you are looking at, and every page below it follows that choice: numbers, chat, logs, billing.

Two things are worth knowing up front:

* **Your role can differ per workspace.** You may own yours and be an agent in a client's. Pilot Status recomputes what you can do on every request, from the workspace you currently have open.
* **Nothing crosses between workspaces.** A number belongs to one workspace and cannot be moved to another. Neither can conversations, templates or API keys. If you need the same number somewhere else, connect it there.

<Note>
  Your original account did not change. It became your **home workspace** — same numbers, same history, same bill. What changed is that it can now have other people in it.
</Note>

## What lives in a workspace

| Belongs to the workspace               | Belongs to you                    |
| -------------------------------------- | --------------------------------- |
| WhatsApp numbers and their connections | Your login, name and password     |
| Conversations, messages and media      | Which workspace you had open last |
| Templates, labels and webhooks         | Your notification preferences     |
| API keys and integrations              |                                   |
| The plan, the wallet and the invoice   |                                   |

Because API keys belong to the workspace, a key created by a teammate keeps working after they leave — unless someone decides otherwise. See [Members](/dashboard/members) for what happens to credentials during offboarding.

## Seats

Every plan includes a number of **seats**. A seat is taken by an active member and also by a **pending invitation** — otherwise you could invite thirty people and only find out at the next invoice.

An invitation that expires releases its seat automatically. There is nothing to clean up.

## Who owns it

Each workspace has exactly one **owner** — the person who pays. The owner is the only one who can move money, reveal credentials in plaintext, destroy numbers, or change who is inside. Ownership is transferred deliberately; it is never granted by an invitation.

See [Roles and permissions](/concepts/roles-and-permissions) for what each role can do, and [Members](/dashboard/members) for how to invite people.