Access to the Compensation module and many Compensation permissions are managed via Leapsome's Feature Access Matrix, which gives admins a single place to control permissions across all modules. In addition, Compensation cycles use cycle-specific roles (Template Owner, Cycle Owner, Proposer, Approver) that determine what stakeholders can do within a given cycle. To view and configure access rights for the Compensation module, navigate to: 'Settings' > 'Employees' > 'Feature access matrix'
📖 For a full overview of the Feature Access Matrix and Access Roles, including how to create and manage custom roles, visit: Feature Access Matrix and Access Roles
In Feature access matrix, you can:
- See which roles have access to each Compensation feature (creating compensation cycles, managing proposals, approving proposals, viewing salary bands, accessing analytics, etc.)
- Toggle individual features on or off per role
Cycle-specific roles
Beyond platform-wide roles, the Compensation module uses cycle-specific roles that are assigned when setting up a compensation cycle:
- Template Owners can create and edit compensation cycle templates that define the structure and workflow for compensation processes.
- Cycle Owners manage specific compensation cycles, including adding or removing participants and configuring cycle settings.
- Proposers are assigned per cycle and can create compensation proposals for specific employees. Proposers can view employee compensation history, see smart recommendations based on configured rules, and submit proposals for approval.
- Approvers are assigned per cycle to review and approve compensation proposals. Approvers can approve proposals individually or in bulk, add notes visible to relevant stakeholders, and manage the approval workflow. In some cases, a user can be both a proposer and an approver in the same cycle.
Custom access roles
You can also create custom access roles with tailored Compensation permissions to meet your organization's specific needs. Custom roles allow you to grant specific users access to selected Compensation features without giving them full admin rights.
To create and configure custom access roles:
- Navigate to 'Settings' > 'Employees' > 'Access roles'
- Create a new custom role with specific feature combinations
- Define which Compensation features users with that role can access
- Assign the role to individual users or in bulk
A reminder on roles
- (Super) Admins typically have the broadest access; exact permissions depend on your configuration
- HRBPs can be granted specific Compensation access by an admin to manage users, teams, or locations
- Template Owners can create and edit compensation cycle templates
- Cycle Owners manage specific compensation cycles and their participants
- Proposers are assigned per compensation cycle to create and submit compensation proposals for specific employees
- Approvers are assigned per compensation cycle to review and approve compensation proposals
- Managers may be assigned as proposers or approvers depending on the cycle configuration
- Users typically do not have access to the Compensation module unless assigned a specific role
- Custom roles can be configured with any combination of Compensation permissions
FAQ
How can a super-admin without direct reports set up and test the Compensation module?
By default, the Compensation module can only be enabled for users who are recognized as managers (i.e., they have at least one direct report). Super-admins without direct reports do not appear in the manager selector and therefore cannot access the module from the sidebar on their own.
To work around this:
- Go to the user's employee profile and open the 'Role' tab.
- Under 'Additional Roles', assign them the 'Compensation module admin' role.
- The user will now be able to access the Compensation module from the sidebar, even if the module is disabled for all managers in 'Admin Settings'.
Please note: Since December 2025, users assigned as Compensation module admins can access the module even without direct reports. Being a super-admin alone does not grant access to the Compensation module - access is controlled separately through the module's role settings.