Doxbrix uses role-based access control to manage what each person can do. Roles are assigned at the **workspace** level and can be refined per **project**, so yo...
Doxbrix uses role-based access control to manage what each person can do. Roles are assigned at the **workspace** level and can be refined per **project**, so yo...
Doxbrix uses role-based access control to manage what each person can do. Roles are assigned at the workspace level and can be refined per project, so you can give broad access to your core docs team and scoped access to occasional contributors.
Inviting members
Workspace members are managed in Settings → Workspace → Members.
From the editor, open Project settings, then switch to the Workspace settings and choose Members. (Owners and Admins can manage members.)
Enter the teammate's email address to send an invitation. Pending invitations stay in the members list until they're accepted.
Assign the role the invitee should have — Owner, Admin, Editor, or Viewer (see the role table below).
The invitee receives an email with a link to join your workspace.
The four roles
Doxbrix has four built-in roles, from full administrative control to read-only access. The Members panel shows each person's role as a colored chip.
| Role | Read | Comment | Write & edit | Review / publish | Manage members & settings | Billing & deletion |
|---|---|---|---|---|---|---|
| **Owner** | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| **Admin** | ✓ | ✓ | ✓ | ✓ | ✓ | — |
| **Editor** | ✓ | ✓ | ✓ | ✓ | — | — |
| **Viewer** | ✓ | ✓ | — | — | — | — |
Role descriptions
- Owner — full control of the workspace, including billing and deletion. There is always at least one owner.
- Admin — everything an owner can do except billing and deleting the workspace. Use for team leads who manage members and settings.
- Editor — can create, edit, review, and publish content. The standard role for core documentation team members.
- Viewer — read access plus the ability to comment. Useful for stakeholders and reviewers who need visibility without edit rights.
Project-level roles
A member's workspace role is their default, but you can grant project-scoped access in Settings → Project → Members. Add a member to a single project and pick a Role — Viewer, Editor, or Admin — for that project only. The project members panel shows Eligible reviewers and lets you Filter by role.
This lets you, for example:
- Give an engineer Editor access to one API Reference project while they stay a Viewer elsewhere.
- Grant a contractor Editor access to a single project for the duration of an engagement, then remove it.
To change someone's access, use the role dropdown next to their name; to revoke it, remove them from the project.
Groups
For larger teams, manage access by group instead of person by person:
- Create groups like Docs Team, Engineering, or Support.
- Assign roles to the whole group.
- Add and remove people; their access updates automatically.
Groups can be synced from your identity provider on Enterprise plans via SCIM, so membership stays in step with your directory.
Single sign-on (SSO) and SCIM
On Enterprise plans, Doxbrix supports:
- SAML / OIDC SSO — members sign in through your identity provider (Okta, Microsoft Entra ID, Google Workspace, and many more).
- SCIM provisioning — members and groups are created, updated, and deactivated automatically as your directory changes.
- Require SSO — require all members to authenticate through SSO, disabling password login.
Configure these in Settings → Workspace → Single Sign-On. For the full provider list, step-by-step setup, and every form field explained, see Single sign-on (SSO).
Removing members and transferring ownership
- Remove a member from Settings → Workspace → Members. Their access ends immediately; their authored content and comment history are retained.
- Transfer ownership by promoting another member to Owner, then changing your own role. A workspace must always have at least one Owner.