Users, seats and projects
What counts against your plan, and how to manage users and projects day to day.
Users
Invite people from Settings → Users & roles, and set their role there: Owner, Admin, Developer or Viewer. See Users, roles and the audit log for what each role can actually do.
What counts as a seat: an active user with the Owner, Admin or Developer role, meaning anyone who can write tickets or control a run. Viewers don't count. They're free and unlimited on every plan, so adding someone read-only access never costs you a seat.
Deactivating a user frees their seat immediately. Their history, meaning tickets they created and runs they approved, stays exactly as it was in the audit trail; they just can't sign in or occupy a seat anymore.
Seats are named users: the license agreement doesn't allow one login shared between people. Promoting a Viewer to Developer uses a seat, and is refused outright if none is free. See Licensing & billing for adding one.
Projects
A project is one connected git repository, with its own queue, checks and settings. A monorepo holding all of a company's code still counts as a single project.
Archiving a project (Settings → Projects & repository → Archive) frees its slot on your plan. Nothing is deleted, and its tickets, runs and audit trail stay fully readable, but no new job can start on it, and Autopilot turns off.
Unarchiving is refused if you don't currently have a free project slot. Add one, or archive something else first.