Members and roles
Invite members and guests and choose the right level of access for each person.
In a workspace, owner, admin, and member can create issues and post comments. Their permissions differ when managing settings and people. A guest can read and comment on issues only in projects shared with them.
Permissions for owners, admins, and members
| Action | owner | admin | member |
|---|---|---|---|
| View the workspace and collaborate day to day | ✓ | ✓ | ✓ |
| Change workspace settings | ✓ | ✓ | — |
Invite an admin or member | ✓ | ✓ | — |
Change or remove an admin or member | ✓ | ✓ | — |
Grant, revoke, or remove owner | ✓ | — | — |
| Delete the workspace | ✓ | — | — |
A workspace must always keep at least one owner: the last owner cannot be demoted, removed, or leave.
memberCreate and work on issues
- View the workspace and take part in everyday work
- Change workspace settings
- Invite an admin or member
- Change or remove an admin or member
- Grant, revoke or remove owner
- Delete the workspace
- Meimei HanOwner
- YouMember
- Lei LiMember
Guests cannot run agents. Each agent has its own Access scope, and owner and admin cannot bypass it to run agents they were not granted. See Agents.
Roles do not open private projects either. An owner or admin sees a private project only when they are on its member list. See Private projects.
Invite members
owner and admin open Settings → Members, click Invite member, enter an email, pick a role, and send. Invitations can grant admin, member, or guest access; an owner must join the workspace first and then be promoted by an existing owner.

The invitee accepts by logging in with that email — no prior signup is needed. Invitations are valid for 7 days; resend after they expire. On self-hosted instances that restrict signup, a live pending invitation allows that email to create an account without a separate allowlist entry — see Auth setup.
The invitation link appears only in the email; there is no place in the product to view or copy it. If the email fails to send, the invitation record still exists — revoke it and send a new one.
When you need a link you can pass along yourself, generate one under Share links in Settings → Members by choosing a role and an expiry. Anyone with the link can join with that role until it expires or is revoked.
Guests
A guest sees only the projects shared with it. In those projects it can read issues, comment, react, and follow them; it cannot create or edit issues, run or mention agents, or open workspace settings, and it sees no other projects, agents, autopilots, or runtimes.
owner and admin invite a guest by choosing Guest in the invite dialog and picking the projects it can see. From a member's actions menu they can make a member a guest, which takes back its agents, autopilots, and runtime access; make a guest a member; or change a guest's projects with Manage accessible projects. Like everything else about a private project, a guest's access to one is shown and changed only by people on that project's member list; changing a guest's projects leaves its access to private projects you are not on as it is.
Change roles
In the member list, open the actions menu at the right of a member's row and choose Change role. The new role takes effect immediately.
An admin can move roles between admin and member, and can remove members holding those two roles. Any change involving owner — promoting, changing, or removing — can only be performed by an owner.
Remove a member
A removed member loses workspace access immediately. Issues, comments, and other collaboration records they created stay in the workspace.
Removing a member also deactivates the runtimes they own, archives the agents bound to them, and cancels runs that have not finished. Grants the member received in agent Access scopes are cleared as well and are not restored automatically if they rejoin.
Next steps
- Issues — the work members and agents handle together.
- Agents — how workspace roles differ from agent Access.
- Daemon and runtimes — who owns runtimes and where they run.