---
title: Members and roles
description: What each of the three workspace roles — owner, admin, member — can do, and how to bring people in.
---

import { Callout } from "fumadocs-ui/components/callout";

Everyone in a [workspace](/workspaces) has a role, and the role decides what they can do. Multica has three: **owner** (the workspace's owner), **admin**, and **member**. Most day-to-day work — creating [issues](/issues), writing [comments](/comments), using [agents](/agents) — is available to all three roles. **The differences cluster around team management.**

## Permissions at a glance

The table below lists the most important differences across team-management actions:

| Action | owner | admin | member |
|---|---|---|---|
| Invite a new admin or member | ✓ | ✓ | ✗ |
| **Invite a new owner** | ✓ | ✗ | ✗ |
| Demote / remove an admin or member | ✓ | ✓ | ✗ |
| **Demote / remove another owner** | ✓ | ✗ | ✗ |
| Delete the workspace | ✓ | ✗ | ✗ |

**Members can't invite anyone** — inviting is an admin-tier permission. **Only owners can promote someone to owner** — admins can promote and demote members or other admins, but they can't create a new owner. Likewise, admins can remove members or other admins but **can't touch existing owners**. The point is to make sure the highest tier can only be granted by someone who already holds it — permissions don't leak upward.

<Callout type="info">
Agent visibility comes in two flavors: "workspace" and "private." Private agents can only be assigned to issues by owners and admins — this protects configurations meant for a specific set of people. See [Agents](/agents).
</Callout>

## Inviting a new member

Multica invites new members by email:

1. On the workspace settings page, click **Invite member**, enter the email, and pick a role.
2. Multica sends an invitation email containing a unique link.
3. The recipient clicks the link, logs in (or signs up), and **accepts the invitation** to join the workspace.

The invited email **does not need to be registered with Multica in advance** — if no account exists, one is created when the invitation is accepted.

If the invitation email fails to deliver (wrong address, mail service hiccup), the invitation record is still retained; you can resend the email from workspace settings, or share the invitation link through another channel.

Invitations are **valid for 7 days**. After that, clicking the link shows an "expired" message, and the inviter needs to send a new one.

## Always at least one owner

Every workspace **must have at least one owner at all times**. This constraint automatically blocks two operations:

- The last owner can't demote themselves.
- Other owners or admins can't remove the last owner.

<Callout type="warning">
If you're the last owner and about to leave the team, **transfer the owner role to another member first**, then try to leave or hand off the workspace. Otherwise the operation will be rejected.
</Callout>

## Removing a member

Owners and admins can remove other members from a workspace. A removed member loses access immediately; issues, comments, and other content they created are retained in the workspace.

## Next

- [Issues and projects](/issues) — what members work on
- [Comments and mentions](/comments) — collaborating under an issue