Team and roles
Add colleagues from Users. Each is invited by email and picks their own password; you never set one for them.
The roles
| Role | What it can do |
|---|---|
| Organization Admin | Full access to company settings, users and everything below |
| Manager | Manage users, and full access to assessments |
| Interviewer | Create and edit assessments, and conduct interviews |
| HR | Send invitations and conduct interviews; view-only on assessments |
| Billing | Billing information only |
A user can hold more than one role, and the effect is additive — someone with HR and Billing can do both.
Choosing a role
Most people who run hiring need HR: it covers inviting candidates and interviewing, without the ability to change the assessments themselves. That separation is worth keeping — an assessment edited mid-funnel makes the candidates before and after the edit incomparable.
Interviewer is for the engineers who write and maintain the questions.
Organization Admin should be a small number of people. It is the only role that can reach candidate data erasure and export, and the only one that can change company-wide settings.
Billing exists so you can give a finance colleague invoices without giving them access to candidates.
The account owner
One user is the owner of the company account. Their Organization Admin and Billing roles cannot be removed — the account cannot be left with nobody able to administer or pay for it.
Changing who the owner is is not something you can do from the dashboard — open a support ticket and we will move it.
Departments
Assessments can be scoped to a department, which limits who in your organization can see them. Use it when engineering and, say, sales assessments should not be visible to each other's teams.
This is an organizational boundary, not a security boundary against your own staff — an Organization Admin sees everything by design.
Removing someone
Deactivating a user blocks them from signing in, and the session they already hold cannot be renewed past its short lifetime. Their history — the invitations they sent, the interviews they scored — stays intact and attributed to them, because deleting it would leave your hiring records with holes.
If you use SCIM provisioning, deactivation in your identity provider does the same thing automatically. See Account and security.
Seats
The number of users you can have is a plan limit. When you hit it, adding another is refused until you either deactivate someone or move up a plan — see Plans and billing.