Inviting users and roles

Add teammates to your organisation, pick the right role, and manage who has access to what.

Updated 2 Jun 2026

Clment is built around teams. This page covers the invite flow, role choices, role changes, and removing access.

The two roles

Every member of an organisation has exactly one role:

Role	Can do	Can’t do
Admin	Everything below + manage users, edit playbooks, billing, SSO, audit log	n/a
Member	Upload, review, redline, edit metadata, mention teammates, ask AI questions	Billing, team management, SSO config

Roles are per-organisation. The same person can be Admin in one org and Member in another.

Every org needs at least one Admin. The last Admin can’t be demoted or removed without first promoting another user.

Inviting one person

Settings → Team → + Invite team member.
Enter email + pick a role.
Click Send invitation.

The invitee gets an email with a magic-link button. Clicking it:

Opens Clment with the invitation accepted automatically.
If they don’t have a Clment account, walks them through sign-up.
If they already have one, drops them straight into your org.

Invitations stay valid for 30 days. Re-send from the Team page if they expire.

Bulk inviting from a CSV

For onboarding a whole team at once, use Settings → Team → Bulk invite.

The CSV format is one row per person, email,role:

alice@example.com,admin
bob@example.com,member
carol@example.com
dave@example.com,admin

Notes:

Role is optional. If omitted (like Carol above), the row uses the default role you’ve picked in the dialog.
A header row is optional. If the first row contains the literal word email and no @, it’s treated as a header and skipped.
Up to 200 rows per upload. For larger lists, split into multiple batches.
Live preview. As you paste, the dialog tells you how many valid rows it sees and flags any with issues (missing email, unknown role) before you submit.
Partial results are fine. If 195 rows succeed and 5 fail (already a member, malformed email, etc.), the 195 invitations go out and the 5 problem rows are shown in a summary — you can fix them and re-upload just those.
Seat cap. If the batch would put you over your plan’s seat limit, the whole batch is rejected with a clear message; shrink the CSV or upgrade the plan and retry.

A success summary lists every email that was invited; a “skipped rows” table lists anything that didn’t go through and why.

Changing roles

Settings → Team → ⋯ menu next to a user → Change role.

Role changes:

Take effect immediately.
Are logged in the audit trail (who changed whose role, when).
Don’t invalidate the user’s current session — they keep working but with the new permission set.

Removing users

Settings → Team → ⋯ menu → Remove from organisation. Removed users:

Lose access immediately. Their session is terminated within about a minute.
Stay in the audit log (history isn’t deleted — they’re shown as <email> (removed)).
Historic attributions don’t change. A review signed off by them still shows their name on the record.
Any MCP connector tokens they personally issued are revoked.

If you’re removing someone who was the Owner on contracts, you’ll be prompted to reassign ownership before the removal completes.

”I can’t remove the last Admin”

By design. Promote someone else to Admin first, then remove yourself if needed.

If you’re a sole Admin and need to hand over the org (e.g. you’re leaving the company), the workflow is:

Invite your replacement.
Promote them to Admin once they’ve accepted.
Hand over MCP connectors (if any) by having them re-add the connector under their account.
Remove yourself (or leave the org via Settings → Profile → Leave organisation).

Free tier vs Pro

The Free plan supports one user per organisation. Inviting a second member prompts an upgrade to Pro on the Team page.

Pro has no per-seat charge — billing is on credit consumption only, not headcount. You can have a 100-person legal-ops team on Pro and pay nothing extra for users.

Cross-org membership

The same email can be invited to many orgs. From the user’s side, switching between orgs uses the Org picker at the top of the sidebar — no separate logins.

Still have questions?

Instant article search