Skip to main content
All user and group management is under Admin → Users and Admin → Groups.

Instance roles

Every user in Collabase has one of two instance-level roles. This role controls what the user can do across the entire platform.
Instance roles and space roles work together. A User can be given the space role of Manager or Space Admin in a specific space, which grants them elevated rights inside that space. See Permissions for how the layers interact.

Inviting users

1

Open Admin → Users

Click Add New User in the top-right corner.
2

Enter the user's details

Fill in their name and email address.
3

Set a temporary password

Enter a temporary password. The user will be prompted to set their own password on first login.
4

Assign an instance role

Choose User or Admin. Most new users should receive the User role.
5

Click Create User

The account is created immediately. Share the Collabase URL and temporary credentials with the new user.

Managing existing users

From Admin → Users, you can take the following actions on any account:
You cannot disable or delete your own account. Ask another admin to do this if needed.

The Identity column

Every row in Admin → Users shows an Identity badge indicating how the account was created: Local, LDAP, SCIM, SAML, or the OAuth provider it signed in with (Google, GitHub, Microsoft, etc.).
For users synchronized from LDAP, SCIM, or an OAuth/SAML sign-in, profile fields such as name and email are managed in your directory or identity provider. Changes made there sync to Collabase automatically — editing them directly in Collabase is not possible for synchronized fields. See Identity Providers for exactly which fields sync for each method.

Groups

Groups let you grant space access to entire teams at once, instead of adding each person individually to every space. When you add someone to a group, they immediately gain access to all spaces the group has been granted access to. When you remove them from the group, that access is revoked across all those spaces at once.

Creating a group

1

Open Admin → Groups

Click New Group.
2

Name the group

Enter a name (e.g. “Engineering”, “Marketing”) and an optional description.
3

Add members

Open the group and go to the Members tab. Search for users by name or email and add them.
4

Grant space access

Go to the Space Access tab. Select a space and assign the space role that all members of this group will have there. Repeat for each space the group should access.

Adding or removing a member from a group

Open the group from Admin → Groups, go to the Members tab, and use the add or remove controls. Changes take effect immediately — the user gains or loses space access right away.

Using groups in space settings

You can also manage group access from inside a space. Go to Space Settings → Members → Add Group, select the group, and assign a space role. See Space Settings for details.

Global module access

Some Collabase modules are instance-wide — not tied to any space. Access to these modules is controlled by assigning a group a role for the module. Admin → Roles & App Access is where you manage these assignments. Automation does not use group-based module roles — permissions are set per individual rule.

Assigning module access to a group

1

Open Admin → Roles & App Access

The page lists all global modules and their current group assignments.
2

Click Add Access

Select the module, select the group, and choose the role.
3

Save

Members of the group can now access the module with the selected role immediately.
To remove access, click the remove icon on the group’s row for that module. Access is revoked immediately.

Permission Schemes

Permission Schemes define what Managers, Members, and Viewers can do inside a space. A scheme is assigned to one or more spaces and controls all space modules at once (Projects, Docs, Test Management, and more). Schemes are managed under Admin → Permission Schemes.

Built-in schemes

Collabase ships with four system schemes that cannot be deleted:

Creating a custom scheme

1

Open Admin → Permission Schemes

Click Clone on any existing scheme to create an editable copy.
2

Rename the clone

Give it a descriptive name so space admins can identify it when assigning it.
3

Edit the permissions matrix

Toggle which actions each role (Manager, Member, Viewer) can perform per module area.
4

Preview affected spaces

Before saving, the editor shows a list of all spaces currently using this scheme, so you can assess the impact of your changes.
5

Save

The updated scheme takes effect immediately in all spaces using it.
See Permissions for the full permission matrix by role and module.

Automated provisioning (SCIM 2.0)

SCIM provisioning requires an enterprise license and must be turned on separately from generating a token.
SCIM 2.0 connects your identity provider (Okta, Microsoft Entra, JumpCloud, etc.) to Collabase so user accounts and group memberships are created, updated, and deactivated automatically — no manual steps required when someone joins or leaves the organization. SCIM is set up and managed from Admin → Identity Providers → SCIM Provisioning, not from this page. See Identity Providers for the full setup steps, the token generation and revoke flow, and exactly which fields sync automatically. Once configured, check back here in Admin → Users — the Identity column on each row confirms whether an account was provisioned via SCIM, LDAP, SAML, or an OAuth provider. SCIM does not delete accounts — it only deactivates them. Content created by the user is preserved.
Last modified on July 6, 2026