Who these recommendations are for
The recommendations are addressed to the OHS or security manager of the group who introduces the same system in several plants and must set a uniform layout of roles. They concern three groups that cause the most problems: security, reception desks, and people who invite guests and external companies.
The basis is common to all plants: permissions come from roles with inheritance, a permissions matrix and a grant ladder. A role higher than one's own cannot be granted, which protects against accidental expansion of permissions when duties are delegated.
Recommendation 1: start with inherited roles, not individual permissions
Instead of granting individual permissions to people, choose a role that inherits them. Across a group of plants this gives one table: role, scope, who may grant it. A plant manager does not invent their own combinations, so after a year all plants still have the same layout.
Access scope of selected roles: number of areas (illustrative example)
Recommendation 2: reception gets the Reception role, not the security role
The Reception role inherits the security permissions and additionally manages external companies and guests and invites internal employees, without editing or deleting accounts. This is exactly the scope of reception and secretariat work. Granting the security role would require closing gaps by hand, and a higher role would give permissions the reception desk does not need.
Control principle: reception may invite and register, but may not delete an employee's account. Changing or removing an account stays with the administrator and the manager.
Recommendation 3: give the administrative employee permissions, without system settings
The Administrative employee role has permissions for work permits, reports, companies and guests, and inviting internal employees, but has no system settings, team settings or alerts. This is a good fit for a person in the administration department who handles plant documents but should not configure alarms or the structure of teams.
Recommendation 4: give inviters the Inviter role
The Inviter role gives access only to the External companies and guests module: inviting, pre-registering visits and viewing lists. It does not take an active user licence in the training module. In a group with dozens of employees who invite a supplier once a month, this matters, because inviting does not increase the licence cost.
If an employee both invites and takes part in training, a separate internal role is granted to them. The Inviter role is not meant for that.
Recommendation 5: enforce the grant ladder
A role higher than one's own cannot be granted. In a group of plants this means that the manager of one plant will not extend their own permissions beyond what the group administrator has assigned to them. Plan who is the administrator at group level and who is at plant level, and record it in the standard.
Recommendation 6: role names must be unambiguous
No role name in the system may contain another role name as a substring, because searching by role works on text matching. An automated test enforces this. If you introduce your own naming conventions in the group's documents, apply the same principle: a name in documentation should be distinct from the names of other roles, so that permissions are not confused.
Recommendation 7: once a quarter, compare roles across plants
The quarterly review consists of listing people and roles in each plant against the standard table. A discrepancy means that someone granted a role outside the rules or that duties have changed. At the end of the review, record decisions, not just the statement that roles are correct.
- Security: the security role, without managing external companies.
- Reception: the Reception role, invitations and registration, without editing accounts.
- Administration: Administrative employee, permissions and reports.
- Inviters: the Inviter role, only the guests and companies module.
Video
Frequently asked questions
Does the Inviter role take a training licence?
No. The role gives access only to the External companies and guests module and does not take an active user licence in the training module.
Can reception delete employees' accounts?
No. The Reception role invites internal employees and manages guests, but without editing or deleting accounts.
Can a manager grant a role higher than their own?
No. The grant ladder does not allow granting a role higher than one's own.
A role layout for your group
We will prepare a table of roles and scopes for your group of plants and review it with the OHS and IT teams. Arrange a short meeting.
Let's talk