Skip to content

Settings

Members and roles

The three workspace roles, who can see which project, and how to invite, change and remove people.

People belong to a workspace with one of three roles, and are added to the projects they work on. The role decides what someone can change; project membership decides what they can see.

Owner Admin Member
See the workspace, its Members and projects lists Yes Yes Yes
See every project Yes Yes Only projects they belong to
Approve, reject, comment and ask for reviews on a project they can see Yes Yes Yes
Change a project's settings, rules, webhooks and token; create projects Yes Yes No
Add anyone to a project, remove anyone from it Yes Yes No, except leaving a project themselves
Change workspace settings, integrations, sign-in and storage Yes Yes No
Invite and remove people, change roles Yes Yes No
Delete anyone's comment Yes Yes Own comments only
Delete the workspace Yes No No

A project that someone can't see doesn't exist for them: they get "not found" rather than "forbidden", so the existence of a project isn't revealed. Only the author of a comment edits it or moves its region, whatever their role.

Separately from these, an instance admin runs the whole installation: accounts, all workspaces, health and instance settings. It isn't a workspace role. See Instance administration.

The table above is the short version. This one lists every kind of action by the role the server checks. "Anyone who sees the project" means an owner, an admin, or a member added to that project. A person who can't see a project gets "not found" for all of it.

Action Who
Create a workspace Instance admins; every signed-in person when the instance setting Who can create workspaces is anyone. Not someone signed in through a workspace's own single sign-on
Delete a workspace Owners. Typing the workspace's address confirms it. It disappears at once and is purged after 30 days unless an instance admin restores it
Change workspace settings, picture, merge gate and triage defaults Owners and admins
Sign-in methods, the workspace's single sign-on, email domains Owners and admins
Connect, change or remove integrations; import repositories Owners and admins
Invite, remove people, change roles Owners and admins. Only an owner removes an owner
Create a project Owners and admins
Change a project's settings, appearance, GitHub link, hosted sites and custom domains Owners and admins
Add webhooks, regenerate their secrets, remove them Owners and admins
Rotate the project's CI token Owners and admins. Anyone who sees the project sees facts about the current token (never the token itself)
Delete a project Owners and admins
Create, edit, reorder and delete review rules; set the triage rotation Owners and admins. Anyone who sees the project reads the rules
Add and remove ignore regions Owners and admins
Approve, reject, request a review, comment Anyone who sees the project
Triage: assign, snooze, dismiss, re-run a comparison Anyone who sees the project
See baselines, hosted sites and the project's integration links (such as Figma frames) Anyone who sees the project
Add, remove or auto-link a project's integration links Owners and admins
Edit a comment or move its region Its author only
Delete a comment Its author, owners and admins
Put off or bring back a review request The reviewer it was assigned to
Take back an action with Undo The person who did it
Add anyone to a project, or remove anyone Owners and admins. A member can remove only themselves

An instance admin runs the installation (accounts, every workspace's existence, instance settings, health, the GitHub App) and isn't a workspace role: inside a workspace, what someone can do follows their membership. An instance admin is never refused by a workspace's sign-in method switches, so a change of methods can't lock out the people who run the server. See Instance administration and Authentication.

Open it from Settings in the workspace menu, then Members. It's the one workspace settings page every member can open. Each person is a row with their name and email, tags for how they sign in (for example a password or a connected account), the projects they're in, and their role. The header counts people, and the find field filters by name, email or role.

CirCI
The Members page of the Acme workspace, seen by its owner. Nine people are listed with name, email, how they sign in, the projects they are in, and a role control set to Admin or Member, with an actions menu on each row. The owner's own row shows Owner. An Invite button sits in the header.
The Members page as an owner sees it: a role control and an actions menu on every row but their own.

Owners and admins also see:

  • Invite in the page header.
  • A role control on every row except their own, and an actions menu with Remove from workspace.
  1. Choose Invite.

  2. Enter the Email and a Role: Admin or Member. Owners aren't invited; a workspace's first owner is whoever created it.

  3. Choose Send invite. The toast says "Invitation sent to …".

An invitation is valid for 7 days. Inviting an address that already has a pending invitation replaces it: the earlier link stops working, and the toast says so. The people you've invited but who haven't joined yet are under Pending invitations, each with its role and when it expires. Resend sends it again, and Revoke cancels it.

Invitations need mail: see Instance administration. Without an invitation, people can also join through a verified email domain or the workspace's single sign-on; see Workspace settings.

Choose Admin or Member in the person's role control. A dialog confirms first ("Make Ann an admin?"):

  • To admin: they can invite and remove people, change roles and change every project's settings.
  • To member: they can no longer invite or remove people, or change settings.

The owner's role isn't changed here, and nobody changes their own. The dashboard can't make someone an owner. With access to the server, circi admin member add --role owner adds an existing account to a workspace as an owner. See Admin CLI.

Remove from workspace asks first: they lose access to the workspace and its projects, and you can invite them again later. A removed person's earlier comments and decisions stay in the builds, shown under their name or as "someone who has left".

Being in the workspace isn't enough to see a project. A member sees a project only when they're added to it. Owners and admins see all of them, and add or remove members in Project settings, Members. The roles shown there are the workspace roles. A project member can Leave project themselves. See Project settings.

Project membership also decides who can be asked to review: the request list, review rules and triage rotation draw only from a project's members. See Review requests and rules.