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

# People and roles

> Who is in the firm and what each role may do. People are never counted.

Zeno is invite-only. An owner adds an address under **Settings → Team**,
and that row *is* the authorization — there is no code to share, and
forwarding an invite grants nothing, because the gate is the address rather
than the link. People then sign in with Google, Microsoft, or Intuit on the
address you listed.

Revoking someone before their first sign-in is a delete, with nothing left
behind to clean up.

## Roles

| Role           | What it is for                                                                                         |
| -------------- | ------------------------------------------------------------------------------------------------------ |
| **Owner**      | Runs the firm. Everything below, plus the team and the subscription.                                   |
| **Operator**   | Does the books and signs off on what gets posted.                                                      |
| **Member**     | Does the books. Does not approve what gets posted — the reviewer's counterpart, not a lesser operator. |
| **Cardholder** | Carries a company card. Sees their own charges and nothing else.                                       |

What each may do:

|                                                                                      | Owner | Operator | Member | Cardholder |
| ------------------------------------------------------------------------------------ | :---: | :------: | :----: | :--------: |
| See the console                                                                      |   ✔   |     ✔    |    ✔   |            |
| Work the queue, import statements, work the inbox, teach rules through the assistant |   ✔   |     ✔    |    ✔   |            |
| Approve a plan or an expense claim                                                   |   ✔   |     ✔    |        |            |
| Connect banks, map feed accounts, configure expense cards                            |   ✔   |     ✔    |        |            |
| Manage the team                                                                      |   ✔   |          |        |            |
| Manage billing                                                                       |   ✔   |          |        |            |
| Submit their own card charges and attach receipts                                    |   ✔   |     ✔    |    ✔   |      ✔     |

These are enforced by the server on every request. The console mirrors them by
hiding what a person cannot use, but the check that matters is the server's.

<Note>
  A cardholder does not get the console at all. Handing someone whose whole
  business here is the card in their pocket the full firm console would expose
  work they cannot act on. They get a page for their own charges instead. See
  [expense claims](/docs/cloud/expenses#what-the-cardholder-sees).
</Note>

## Client access

An owner can limit an invite to named client companies. Leave the selection
empty for an owner, operator, or member who should see the whole firm. A scoped
person sees only the selected companies wherever the console or MCP tools list
client work.

A cardholder must be scoped to at least one company. With no company selected,
the cardholder sees no claims.

## Nobody is a seat

Pricing follows client books and nothing else. Invite as many owners,
operators, members, and cardholders as the work needs; who may approve is a
permission you grant, not a purchase. The Team page says how many people can
approve a posting, which is a fact about the firm's review and not a count
against anything. Current pricing is on
[zenofirm.com/pricing](https://zenofirm.com/pricing).

## Removing someone

Removing a person ends their sessions immediately. Work they approved keeps
their name on it — a verdict is a record of what a specific person decided, and
it does not become anonymous because they left.

## Changing a role

Re-role someone in place from the same page. It takes effect on their next
request, not on their next sign-in.

To change an existing person's company scope, remove the address and invite it
again with the intended clients selected. Their recorded approvals keep their
name.