Share with your team
Share a workspace, and choose what each person can do in it.
Invite someone
Every invitation, and every change to what someone can do, happens in one place: the workspace’s Team panel. You reach it from any of these:
- Manage workspaces, in the workspace switcher: choose the workspace, then Team.
- Invite, in the header, on your own workspaces.
- Share, on your workspace’s list.
- The team step of the welcome sheet, and of a new workspace, right after it’s made.
- Type their email.
- Choose what they can do: View only, Can screen or Can spend your tokens. Every new invitation starts on Can screen, so an invitation never spends your balance unless you choose it.
- Press Send invite. It goes out at once. They get an email, sign in with Google as that address, and choose Join workspace when the invitation opens on their home page. If they can send screenings and haven’t yet accepted the terms for this type of screening, they accept them first.
Or give them the workspace’s invite code, under the Team panel in Manage workspaces. They enter it under Join an existing workspace, on their home page while it has no applications yet, and join on Can spend your tokens (or, if you’d already invited them, on the access that invitation gives). You can change that afterwards, make a new code, or turn it off.
What each person can do
| Choice | What it means |
|---|---|
| View only | Sees applicants and reports here. Never sends screenings or spends tokens. |
| Can screen | Sends screenings here and pays with their own tokens. Your balance is never touched; results still land here. |
| Can spend your tokens | Sends screenings here on your balance or their own: they pick each time, and picking yours spends this workspace’s tokens. |
Someone looking at a workspace another person shared with them sees that person’s first name in place of “your”: Can spend Priya’s tokens.
What you choose holds in their tools too: people you share a workspace with reach it through their own API keys and connected assistants, at the role you gave them — reading its results and showing its reports as well, if their key was made to. See Concepts.
What each access level can do
| Action | Owner | Can spend your tokens | Can screen | View only |
|---|---|---|---|---|
| See applications and reports | Yes | Yes | Yes | Yes |
| Send screenings | Yes | Yes | Yes | No |
| Set a stage, assign, add notes, move, remind, cancel | Yes | Yes | Yes | No |
| Add and rename buildings, groups and units; set rent; reorder the list | Yes | Yes | Yes | No |
| Delete buildings, groups or units; rename or delete a workspace | Yes | No | No | No |
| Invite people, and change or remove their access | Yes | No | No | No |
| Billing and buying tokens | Yes | No | No | No |
| Custom stages | Yes | No | No | No |
| Spend your tokens | Yes | Yes | No | No |
Managing people
- In the Team panel, everyone is listed under People, you first. Change what someone can do from the menu beside them, or choose Remove from workspace at its foot.
- Invitations not yet accepted wait under Waiting to accept: change what they’ll be able to do, Resend the email, or cancel the invitation with ✕. Team invitations don’t expire.
- Anyone you’ve shared with can leave, from Manage workspaces.
- Workspaces others share with you are listed under Shared with you, in the workspace switcher.
There are no Admin, Reviewer or Builder roles. Access is set per workspace, per person, in its Team panel. Developers who manage your API keys, webhook and allowed sites are added apart, in Developers → Access. That opens no workspace to them. Any key they make sees every applicant’s email; a live key that reads results or shows reports needs you to switch on Can see applicant data for them. They can also revoke any key, change the webhook and change allowed sites.

