Skip to content

Managing the team

You invite by email address, and you choose the seat’s role at that moment rather than afterwards. Full is the default, because the owner is paying for the seat and the usual reason to invite someone is that you want them working.

Full can generate. Viewer can see the team’s work but cannot spend on it. A viewer who tries to generate is told so directly, and told that the owner is the person who can change it. The refusal names the constraint rather than sending them to a billing page that is not their problem.

A viewer holds a seat. This is the part that surprises people: moving someone from full to viewer does not free a seat, because the cap counts people on the team, not people who can spend. If you need the seat back, remove them.

The owner can move any member between full and viewer at any time. Two things do not change: the seat itself, and the owner’s own role. An owner cannot demote themselves, since a team with nobody able to administer it is not a state worth being able to reach.

The seat count includes the owner, and the cap comes from the plan. See your plan for the number. When a team is at its cap the invite is refused, and the message says how many seats are open and what to do: remove a member, or move up a plan.

Full members are refused with a message that names the team and says the owner is who can fix it. Nobody is left guessing whose billing problem it is, and nothing is deleted: the work is still there when the subscription resumes.