Team
updated
Your team lives in Settings → Members: everyone in the workspace, their role, last activity and pending invitations.
Roles
| Role | Can |
|---|---|
| Owner | Everything an Admin can; created the workspace and can’t be removed |
| Admin | Edit and delete any document or project, manage members, settings, integrations, webhooks and billing |
| Member | Read every project including drafts, create projects, create their own integration tokens |
To let a Member edit a specific project, add them as a project collaborator — see Creating and Configuring Projects. Keep at least two Admins.
Invite people
Select Invite Member, enter an email and choose a role. The invitation is valid for 7 days; an expired one can be resent. Members who can’t invite see Request invite instead, and people who open a workspace link without access can Request access — admins get an email either way.
Change or remove
Change a role from the dropdown next to a name; it applies immediately. Removing someone revokes every integration token they created, so CLI jobs or AI assistants running on those tokens stop working. Their documents stay.
To remove yourself, use Leave workspace under Settings → Danger zone; it has the same effect on your tokens. Two people can’t leave or be removed: the Owner — ownership changes hands only when the owner deletes their account and transfers the workspace — and the last Admin, who has to make someone else an Admin first.
Teams
Group members into teams and grant a team a role on a project in one step. A person’s effective role is the highest they hold from any source.
Only Admins create teams and change who is in them, but anyone in a team can leave it: open the team and select Leave team. You lose the project roles that team gave you right away; roles you hold another way stay. Only an Admin can add you back.
Git accounts
Settings → Members → Git accounts lists the git identities seen in commits from meldoc push and repository sync. Link each one to a member so their edits show under their name. A link only changes the displayed name — it grants no access. Accounts with a verified matching email are linked automatically.
What’s next?
Creating and Configuring Projects — Project access and collaborators.
Integration Tokens — Tokens for the CLI and MCP.