Two permission worlds
The diagram shows the two worlds: global modules apply to the whole instance, space modules follow the of each Space. System Admins bypass both worlds — they have full access to everything, everywhere.Instance roles
Every user account has an instance-level role. This is the broadest layer.
Instance roles are set under Admin → Users.
Global modules
Global modules are not tied to any space. Access is controlled per module by assigning groups a role in Admin → Roles & App Access.Registry
Users without a Registry group assignment cannot see the Registry module at all.
Per-schema permissions — each schema has its own access configuration:
Configure per-schema access from the schema’s Settings → Permissions tab.
Intranet
Studio
All authenticated users can build and manage their own automation rules. There are no group-based module roles for Studio, and access to individual rules is controlled per rule:
The rule’s creator always has all permissions. You can share specific permissions with individual users or groups in the rule’s Settings → Permissions tab.
Run as — each rule has a “Run as” setting:
Times
Times is one app with three roles. A group gets the role under Admin → Roles & App Access, and a person holds the highest role of all their groups. Without a role on Times, the app does not appear in the sidebar.
Booking time on a work item does not depend on the Times app. It depends on the person’s rights in the space the work item belongs to, so a person without a role on Times can still log time there.
---|---|
| Admin | View all time entries across all users and spaces, manage billing rates, lock periods, approve time |
| Manager | View time entries from spaces where they are a member — entries outside their spaces are not visible |
| (users without a group assignment) | Can log and view only their own time entries |
Space roles
Within each space, every member has one of four roles. The Space Admin role grants fixed space-management rights; the other three roles are configured through a Permission Scheme.
Space roles are assigned in Space Settings → Members.
Permission Schemes
A Permission Scheme is a named, reusable template that defines exactly what Managers, Members, and Viewers can do in a space. One scheme can be assigned to many spaces at once — when you update a scheme, all assigned spaces are updated together. Collabase ships with four built-in schemes. These cannot be deleted but can be cloned and customized.Open Scheme (default)
A maximally open scheme — ideal for trusting teams where everyone should be able to contribute freely.Default Software Scheme
A balanced scheme for engineering and product teams. Members can create and edit their own work; Managers control structural operations like cycles and project settings.Client / Read-only Scheme
For external stakeholders — clients, auditors, or partners who need visibility without edit access.Restricted / Confidential Scheme
For sensitive spaces — HR, Finance, Legal. No public access; detailed audit log always active.Assigning a scheme to a space
1
Open Space Settings
Navigate to your space and open Settings → Permissions.
2
Select a scheme
Choose a scheme from the dropdown. A preview shows how many spaces are currently using this scheme.
3
Save
The scheme takes effect immediately. All members of the space now operate under the new rules.
Managing schemes
All schemes are managed under Admin → Permission Schemes. You can:- Clone any scheme to create an editable copy
- Edit a cloned scheme’s rules per role and module
- Preview which spaces will be affected before saving changes
The four built-in system schemes cannot be edited directly. Clone them first, then customize the copy.
Full permission reference
Projects: Tasks
Moving a work item to another project also requires Create tasks and View tasks in the
destination Space, because the move creates a work item there.
Projects: Cycles
Projects: Admin
Comments & Attachments
Docs: Pages
Test Management
Time Tracking (in-space)
Page-level permissions
The space role decides who can read and edit pages in a Space at all. To keep some pages with a smaller circle, put them in a private folder: only the people and groups on the folder’s list see it and every page below it. The folder’s author, the Space owner and instance administrators always see restricted content. See Restrict access to pages. ---|---| | View | The user or group can read the page | | Edit | The user or group can edit the page | Set page permissions from the Share button on any page. Page permissions are independent — they are not inherited from the parent page or from the space role.Groups
Groups let you assign space roles and module access to entire teams at once.1
Create a group
Go to Admin → Groups and create a new group. Add the users who belong to it.
2
Grant space access
In Admin → Groups, open the group, go to the Space Access tab, pick the Space and assign a space role. Every member of the group gets that role immediately. The Space’s Members settings list the group under Inherited group access.
3
Grant module access
In Admin → Roles & App Access, assign the group a role for Registry, Intranet, or Times.
Common scenarios
Related pages
- Users & Groups — create users, manage groups, set instance roles, configure module access
- Space Settings — assign Permission Schemes, manage space members
- Spaces — visibility settings (Private, Internal, Public)
- Permission Schemes — create and manage custom schemes