Docs

Members and roles

Invite members and manage workspace permissions with the owner, admin, and member roles.

Everyone who joins a workspace is a member, and each member has one role: owner, admin, or member. Roles only control workspace settings and team management; day-to-day collaboration — creating issues, writing comments — is open to all members.

The three roles

Actionowneradminmember
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.

Try itSettings · Members
Your role
What this role can do
member

Create 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
Members
View only
Only workspace owners and admins can change these settings.
  • Meimei HanOwner
  • YouMember
  • Lei LiMember
The members page as a member sees it.

Roles do not decide who can run an agent. 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 only grant admin or member; an owner must join the workspace first and then be promoted by an existing owner.

Member management: the invite form and the roster with roles

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, as long as the workspace has a free member slot (see below).

Member limit

On Multica Cloud, a workspace on the Free plan can have up to 5 members. Members and pending invitations each take a slot; guests take none. While the limit applies, a new invitation, an accepted invitation or a share-link join that would go past it is refused until a slot frees up (an invitation is revoked or a member removed) or the workspace upgrades. Existing members are never removed. When the workspace is full, admins see Upgrade and invite in the invite dialog: once the payment goes through, Settings → Billing offers to send the held invitation. On Pro and Business each member takes a paid seat. Self-hosted workspaces have no member limit.

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.

On this page