Your Workspace
How a workspace is organised: teams that own projects, the people in them, the roles that say what each person may do, and groups that grant more.
A workspace is made of teams. A team owns projects and holds the people who work on them; every page you open acts within the team marked as current, and the account menu lets you switch between the teams you belong to. Inside a team, a role says what each member may do, and a group hands a further set of permissions to several members at once.
The pieces
| Piece | What it is |
|---|---|
| Team | A container for projects and people. Someone owns it; everyone else is a member with a role. A person can be in several teams. |
| Member | A person invited into the team. Staff hold a role with team-wide permissions; a client stakeholder joins as a guest of one project. |
| Invitation | An emailed, signed link that creates the account if there is none and adds the person to the team when followed. |
| Role | A named set of permissions. Every team starts with eight default roles and can add its own. |
| Group | A named set of permissions handed to several members on top of their roles. |
Teams are not tenants of separate workspaces. They are how one company organises its work: one team per department or per client account, with projects living in the team that serves them.
Pages
Teams
Create a team, switch between yours, rename or delete the ones you own, and open their members.
Members and guests
Invite staff with a role or a client as a guest of one project, change roles, remove people, and manage pending invitations.
Roles
The eight default roles, custom roles, and the permission catalogue they draw from.
Ability reference
Every permission a role or a group can grant, entity by entity, with a sentence on what each lets a member do.
Groups
Grant a set of permissions to several members at once, on top of their roles.
Activity log
Read every change recorded in the team, who made it and where it came from, and open a record's field-by-field history.
AI settings
Read where the team's monthly AI budget stands, set the cap and the warning line, and read the usage statement per feature and model.
For developers and pipelines
API tokens
Mint a personal access token for the REST API, the MCP server or a pipeline, scoped to a team and optionally one project.
Webhooks
Register endpoints that receive signed event payloads, and read and replay the delivery log.
Who may do what
The owner of a team may do everything in it. Every other member is limited by their role, and by the groups they are in. The permissions that govern this section itself are:
| Permission | Lets a member |
|---|---|
team-member:view-any | Open a team's members page. |
team-member:invite | Send and withdraw invitations. |
team-member:update-role | Move a member to another role. |
team-member:remove | Remove a member from the team. |
role:view-any | See the team's roles on the roles page. |
role:create | Create a role in the team. |
role:update | Rename, describe and re-permission a role. |
group:view-any | See the team's groups on the groups page. |
group:create | Create a group in the team. |
group:update | Edit a group and choose its members. |
group:delete | Delete a group. |
activity:read | Read the team's activity log. |
Renaming and deleting a team, and deleting a custom role someone else created, are the owner's alone.
Related
- Your account: the account an invitation creates and the ways to sign in.
- Accepting an invitation: what the person you invite sees.
How is this guide?
Last updated on
Timezone and Language
Choose the timezone every date and time in the application is read and shown in, understand how it was detected, and pick the interface language.
Teams
Create a team, make one of yours current, open its members, and rename or delete the teams you own, with what each action changes.