This page lists every permission seeded into a workspace and shows which of the six default roles holds it. Use it as the reference when configuring custom roles or auditing access.
Workspace-scoped. Roles and their permission grants live per workspace (per companyId). Every seeded workspace gets its own copy of the six default roles, and every tenant query is scoped to the workspace by a tenant guard, so a permission grant in one workspace never leaks into another. The platform operator manages workspaces from a separate /operator console that does not use this matrix at all.
Grants, not hard-coding. A user's effective permissions are the union of the grants on every role assigned to them. Endpoints are protected with a permissions decorator, and the guard checks that the caller actually holds the required permission — there is no implicit Super Admin bypass. Super Admin can do everything only because it is seeded with the full permission set.
Fixed for the six default roles. The six default roles are system roles: their grants cannot be changed, from the access-control screen or the API. To give someone a different set, Duplicate the nearest default role into a custom role, adjust it, and assign that instead. The matrix shows the grants a new workspace starts with.
Country packs affect which permissions matter
Payroll, tax, and statutory rules follow the workspace's country pack, so some financial permissions only do something under certain packs. For example tax.configure / tax.certificates drive income-tax handling for a pack that has income tax (such as the Pakistan pack), but carry no tax logic under a pack with no income tax (such as the UAE pack). The permission still exists everywhere; the behaviour behind it is pack-dependent.
Legend: SA = Super Admin, HRM = HR Manager, HRO = HR Officer, ACC = Accountant, DH = Department Head, EMP = Employee.
Manage workspace settings (also gates badge evaluation, manual awards, address-verification admin actions, Billing, and the AI assistant's Usage & credits page; holders have no personal AI credit limit)
See the people directory, each person's card with their reporting line, and the whole workspace's org chart in the portal; write one's own "About" line
✅
✅
✅
✅
✅
✅
The directory's switches are saved with company.settings. See People directory.
No permission of its own. Everyone with employees.view_own reads Home, and each person can leave themselves out of Celebrations. Its sections, banner and quick links are arranged with company.settings. See Portal Home.
These do something only in a workspace with the Skills management feature, which comes with the Growth and Enterprise plans. See Skills.
Permission
Description
SA
HRM
HRO
ACC
DH
EMP
skills.view
Read the skills library, people's skills and résumés, the skills matrix and its export, expiring and lapsed certifications, and the skills a designation requires
✅
✅
✅
❌
✅
❌
skills.manage
Edit the library and skill types, people's skills and résumé entries, and the skills a designation or opening requires; review the skills and résumé entries employees propose; receive the certification-expiry email
✅
✅
❌
❌
❌
❌
skills.view_own
See one's own skills and résumé on the portal profile, and propose changes for HR to review
The employment-agreement portal endpoints (GET /api/contracts/portal/my-contract and POST /api/contracts/portal/my-contract/accept) do not require any of the permissions above. They authorize solely on the authenticated user being linked to an employee record, so an employee can only ever read or accept their own contract regardless of role.
Process monthly payroll, dry-run it, and pause or resume an employee's pay; also lets a salary change update a payroll still open
✅
✅
❌
✅
❌
❌
payroll.approve
Approve a payroll run
✅
✅
❌
❌
❌
❌
payroll.lock
Lock (finalize) a payroll run
✅
❌
❌
✅
❌
❌
payroll.salary_view_all
View all employees' salaries, the PF ledger and contribution funds
✅
✅
❌
✅
❌
❌
payroll.salary_view_own
View own salary
✅
✅
✅
✅
✅
✅
payroll.salary_assign
Assign salaries / structures, adjustments, increments; delete a salary record entered by mistake
✅
✅
❌
✅
❌
❌
payroll.configure
Configure payroll (components, structures)
✅
✅
❌
❌
❌
❌
payroll.manage
Disburse, finalize, mark-paid, hold and release a salary, salary-history import, set up contribution funds, record their entries, and share fund profit with members (or undo a share)
Read and search the articles published for one, and acknowledge the ones that ask for it. The owner and the editors of a knowledge space also write, publish and review that space's articles with it
✅
✅
✅
✅
✅
✅
knowledge.manage
Write in every space: create and edit categories and articles; publish, review, archive and delete them; see who has acknowledged an article and its earlier versions. Add, rename and delete spaces, and choose their owners and editors
Recruitment permissions are seeded to Super Admin only by default. When you roll the module out, give them to a custom role (a duplicate of HR Manager, say) from the access-control screen.
Permission
Description
SA
HRM
HRO
ACC
DH
EMP
recruitment.manage
Manage jobs, postings, candidates, applications, interviews, offers, convert to employee
✅
❌
❌
❌
❌
❌
recruitment.interview
Submit interview feedback (participant gate enforced in the service)
✅
❌
❌
❌
❌
❌
recruitment.view
Read openings, candidates, applications (no edits)
Configure the performance module (settings, scorecard profiles, any task); override daily-report AI verdicts; triage AI-flagged reviews and void scores; link integration identities
✅
✅
❌
❌
❌
❌
performance.review
Assign and grade tasks. Team-scoped on its own: reaches only the holder's direct reports; combined with performance.manage or performance.view_all it becomes company-wide. Recurring task schedules always require the company-wide combination
The employee portal reads a user's own data through the view_own / *_own permissions (for example employees.view_own, attendance.view_own, leave.view_own, payroll.salary_view_own, salary_slips.view_own, loans.view_own, hr_letters.view_own, assets.view_own, expenses.submit_own, performance.view_own, goals.view_own, skills.view_own, timesheets.view_own, roster.view_own). These are granted to every default role, and the endpoints resolve the employee from the JWT — so a user can only ever reach their own records. The employment-agreement portal endpoints (see the Contracts note above) bypass the matrix entirely and authorize on the linked employee record.
The six default roles are seeded per workspace with these grant counts (out of 148 total permissions). Super Admin holds all of them.
Role
Default permissions
Super Admin
148
HR Manager
127
Accountant
64
HR Officer
76
Department Head
51
Employee
35
info
This matrix reflects the default grants at workspace creation. The six default roles cannot be changed; admins with roles.manage shape access with custom roles instead, and a person must sign in again to pick up a changed grant. See Custom roles and Default roles for more.