Inviting Members

Admins invite members by email with a pre-assigned role.

Send an invitation

1. Sidebar → Team → Invite Member
2. Enter the invitee's email
3. Pick a role: Admin, Member, or Viewer
4. Send Invitation

REPLACE: Screenshot of the Invite Member dialog

The invitee gets an email with the workspace name, the role they'll have, and an accept link.

Acceptance flow

New users — sign in using whichever identity method your deployment supports (local password, SSO, etc.); the invitation auto-accepts on first sign-in.

Existing users — click the link, get directed to the workspace (log in if needed), accept, access is immediate.

Pending invitations

Listed on the Team page below active members. Each row shows email, assigned role, and when sent.

• Revoke — invitation link becomes invalid, invitee can no longer join.
• Resend — fires another email with the same link.

Invitations expire after 7 days.

Remove a member

Team page → Remove next to the member → confirm. Access is revoked immediately. Past configuration they made is untouched.

You can't remove yourself if you're the only Admin — promote someone else first or transfer ownership.

Change a role

Team page → dropdown next to the member → pick the new role. Takes effect on the member's next page load or API request.

Best practices

• Viewer for stakeholders who only need to watch document flow — no accidental config changes.
• Few Admins — reduces the blast radius of accidental settings changes or workspace deletes.
• Separate workspaces per environment (dev / prod) — role-based separation alone is fragile.
• Periodic review — drop members who no longer need access, especially after departures.

Next steps

• Roles & Permissions
• Team Management
• Workspaces Overview