How the system understands permissions
Permissions in the system result from roles with inheritance and from a scope matrix that defines the level of access to each area. A role can therefore inherit the permissions of another: for example, Secretariat inherits the security permissions and adds management of external companies and visitors.
For HR this means a simple principle: the question is not what role a position should have, but what tasks the person performs and which areas must be open to them. Roles are a consequence of the answer, not its starting point.
Step 1: list the tasks of each position in the system
For each position, list what the person does in the system: inviting visitors, opening work permits, reviewing reports, editing accounts. The list should have a few items, not dozens. If it is longer, the position combines several functions and should be split.
It is important that the head of the department takes part in this step. HR knows the formal positions, but the manager knows which tasks the shift lead actually performs on the night shift.
Sample distribution of accounts by role in a plant of about 200 people
Step 2: match roles to tasks
The next step is a table of position to role. For an office worker who handles permits and reports, the right role is the Administrative Clerk: it can view and open work permits, reports, companies and visitors, and invite employees, but has no access to system settings, teams and alerts.
For a manager who only invites contractors to meetings, the Inviter role is enough, because it gives access only to external companies and visitors. Editing and deleting accounts stays reserved for the administrator, the manager and the health and safety officer, so this should not be granted additionally through a combined role.
- office worker handling permits: Administrative Clerk,
- contract owner inviting visitors: Inviter,
- reception and secretariat: Secretariat,
- department manager with account permissions: management role, after the administrator's decision.
Step 3: check the seniority ladder
Roles are granted along the seniority ladder: an actor cannot grant a role higher than their own, and the ladder does not recognise equal ranks. In practice this means HR cannot grant a role it does not hold itself, and whoever grants roles must be above the recipient.
Before you build the table, agree with the administrator who holds which rank. Borderline cases, such as a new shift manager promoted from shift lead, are worth describing in advance so that manual workarounds do not appear.
Step 4: watch the names of roles
No role name may contain another as a substring, because user search by role works on text matching, and an automated test enforces this. If HR wants to add its own role in the plant configuration, its name must not be contained in any existing role, nor contain one.
The full list of roles depends on the configuration of the installation, so treat the names in this page as a pattern. Check with the administrator which roles are active in your deployment before you publish the table on the intranet.
Step 5: save the table and review it regularly
The finished table of position, tasks, role and owner of changes goes into a document managed by HR together with the administrator. Every change of position, promotion or transfer to another department triggers a role review, not an automatic addition of another role.
The most common problem is accumulation of permissions: an employee changes department and keeps the old roles. A quarterly review of roles and inactive accounts catches such cases before they become an audit topic.
Checklist
Video
Frequently asked questions
Can HR grant roles on its own?
Only those that follow from its own role and the seniority ladder. A role higher than one's own cannot be granted.
Who gets the Inviter role?
People who invite visitors and external companies, such as contract owners. The role gives access only to this module.
Is the list of roles the same everywhere?
No. The full list depends on the installation configuration, so agree the table with the administrator.
Let us organise the roles in your plant
Together with HR and the administrator we will prepare a table of positions and roles that can be maintained after implementation.
Let's talk