Roles
Roles decide what you see. The two trees decide where cost sits. At sign-up there is one question: do you manage agents, or do you manage people?
Browse the docs
Getting started
Attribute
Account
Reference
The three roles
Roles stack: each one includes everything the one before it can do. A member is anyone in the organization, whatever their role.
| Role | Who has it | What it can do |
|---|---|---|
| Agent manager | Anyone who uses an agent: developers, designers, QA, architects, managers. | Reviews and submits their own token sheets. Sees their own cost. |
| People manager | Tech leads and heads of department for teams. Project managers, directors of delivery and account managers for projects. | Reads reports for the teams or projects they are assigned. Sets token budgets and cadence there. Approves token entries, or rejects them back with a reason. |
| Controller | Whoever answers for the numbers as a whole. | Sees everything. Runs the monthly close. Posts adjustments to closed periods. |
What a people manager sees
A people manager sees cost per person within what they are assigned. A controller sees cost per person for the whole organization. There is no mode that hides people behind team totals; see Scope.
Relationships that are not roles
A ticket has an assignee, the person it is assigned to. Being an assignee grants nothing and costs nothing: the cost of a ticket sits with the agent manager of each token entry on it.
Every token entry has exactly one agent manager, who answers for its cost. For a CI automation that is the person who set it up.
Finance
Finance needs no login and sets nothing up. A controller hands finance the cost sheet or a CSV export.
Roles and plans
On the free Solo plan one person holds every role. Roles for several people come with the Team plan; see Plans and limits.