This guide explains how user access and permissions work in our platform. It’s intended for customer administrators and anyone managing user profile or access rights within your organization.
Our access control system ensures that:
- Each user only sees and edits what they’re allowed to.
- Sensitive data (e.g. financials, allocations) is protected.
- Administrators have tools to manage users efficiently and securely.
We use a , structured like this:
These are individual permissions such as:
- View project details
- Edit employee profiles
- Approve resourcing requests
Users don’t get rights directly - instead, they’re bundled into profiles.
A profile is a predefined set of rights (permissions).
For example, a “Line Manager” profile might include:
- View and edit projects
- View team members
- Edit resourcing data
These are used to manage users in bulk.
- You assign profiles to a group, and then add users to that group.
- This helps you easily give multiple people the same level of access.
There are :
- Apply across the whole system.
- Example: A user with a global “Viewer” profile can see all projects and people (if viewer access is granted).
In addition to global profiles, our access model supports that dynamically filter access based on relationships, organizational structure, or custom logic.
- Limited to a specific part of your organization.
- Example: A “Organization Manager” profile limited to the organization node at hand.
:You cannot assign permissions for a specific or .For example:
"Alice can view Project A, but not Project B" is supported.
"Alice can view all projects in a specific organization node" supported. When checking access to an object (e.g., User
, Project
, Customer
, etc.), we use the right module for that domain to interpret special profile names such as:
Grants access to everyone
Grants access to the user’s own record
Grants access to users in the same organization subtree
Grants access if the user is part of the project
Grants access if the user is the project lead
Assisting project manager
Grants access if the user holds a special profile defined in config
Grants access if the user is leading the associated program
Grants access to subordinates in the user hierarchy
Node admin /manager/member
Grants access based on organization nodes where the user is a node lead
You :
- Assign multiple profiles to the same group
- Add a user to multiple groups
- Limit profiles to organization nodes or customer units
You :
- Customize profiles per customer or user
- Give one-off permissions to a specific item (like a single project)
- Edit individual rights within a profile
By default:
- can manage user access within their organization.
- They can:
- Add/remove users
- Assign profiles through groups
- View who has access to what
- Use like
Nordic PMs
or HR Viewers
. - Keep access — fewer profiles and groups = easier maintenance.
- Use the group to grant wide visibility to trusted users.
→ , access is always defined at the profile/group/context level. You can limit by department or node, but not a specific project.
→ At this time, all profiles are defined centrally. If you have a suggestion, feel free to contact our support.
→ Yes! A user will receive all profiles from all groups they belong to.