A team is the space you share with your colleagues. It holds the members and their roles, the projects, and the settings that apply to everyone. This page shows how to bring people in and where each team setting lives.
To open the team settings, choose your team's name at the bottom of the sidebar, then Team settings. The list on the left shows the team sections, with your Personal settings (account, security, preferences and personal tokens) above them. You only see the sections your role can use.
Invite members
Sign-up is by invitation, so new colleagues join through a link you send them.
Open Members
In team settings, choose Members, then Invite member above the list.
Enter the email and the role
Enter the person's Email and choose a team Role. Roles and permissions explains what each role can do. Leave Invitation expires at 7 days or pick 1 to 7 days, then choose Send invitation.
Add them to projects
A team role alone doesn't open private projects. Once the person has accepted, add them to the projects they work in: open the project, choose Settings at the bottom of the sidebar, then Members, and give them a project role.
Invitations that haven't been accepted wait under Pending invitations. Choose Resend if a link expired, or Revoke to cancel it.
Change a role or remove someone
In the member's row, open the menu at the end and choose Manage. Pick the new Role and choose Save changes. To take away someone's access, choose Remove in the same menu; you can invite them again later.
Rename, switch or create a team
Rename the team under Team in team settings: change Team name, and Team handle if you like, then choose Save. To switch to another team or start a new one, open the account menu at the bottom of the sidebar and use Teams or Create team.
Team settings at a glance
| Section | What you do there |
|---|---|
| Team | Team name and handle, sign-in policy. |
| Members | Invite people, change roles, remove members, resend or revoke invitations. |
| API keys | Team API keys for scripts and integrations. |
| Audit log | Who did what in the team. |
| Usage & billing | Usage and limits for the current period. |
| Storage | Recording and export storage, and storage per project. |
| Webhooks | Webhook endpoints and their delivery history. |
| Secrets | Values that workflow steps read as environment variables. Once saved, they can't be read back. |
| Notifications | Which alerts you get in the console and by email. |
| Data and privacy | Legal holds and closing the team. |
API keys and personal tokens
A team API key is for a script, a CI job or an integration that works on behalf of the team. In API keys, choose Create API key, describe what it is for, set an expiration date, choose which projects it can reach and which permissions it needs. Permissions are fixed once the key exists. The full key is shown only once, so copy it before you close the dialog.
For your own command-line work, use a personal token instead: open Account from the account menu, then Personal tokens, and choose Create token. Owners, Admins and Researchers can create personal tokens. See API keys and Personal access tokens.
Storage
Storage shows how much the team stores for recordings and for exports, with the total and the time the figures were taken. Recording storage counts toward billing; export storage doesn't. Usage by project lets you search for one project. Owners, Admins and Billing admins can also refresh the storage check, which compares the stored files with the recorded usage. It only reports differences and never changes your data.
Audit log
The Audit log records what happened in the team: invitations, role changes, API key activity, project changes and more. Choose a range of up to 31 days, narrow it with Advanced filters if you need to, and save the entries with Download CSV.
Webhooks
Webhooks send team events, such as a finished run or a ready export, to a URL you run. You create endpoints through the API or the CLI for now. Once one exists, the Webhooks page shows its delivery history, and you can send a test ping or replay a delivery. The event types and signatures are in Webhooks.
Usage
Usage & billing shows the team's usage and limits for the current period. The console tour explains what is on that page.