The seniority ladder principle
Roles are assigned along a seniority ladder: an actor cannot assign a role higher than their own, and the ladder has no equal rungs. This means no one hands out permissions they do not have, and even two people in similar positions cannot raise each other's roles.
For the administrator this is a convenient safeguard: an error in one decision does not spread across the whole structure. For audit it is a simple argument that permissions are decided by hierarchy, not by chance.
Assignment practices
The practices cover three moments: assigning, changing and withdrawing. Each has its own pitfalls.
Assigning: start with the narrowest role
A new account gets the narrowest role that lets it perform its tasks on day one. The Inviter role may be granted only by roles with full access to external companies and guests, so that an employee without those permissions cannot give them to another account. Raising a role happens on a justified request, not upfront just in case.
Changing: watch the role names
No role name may contain another role name as a substring, because searching users by role relies on text matching. An automated test guards this. The practical conclusion: when custom role names are added on the plant side, if that option is in play, first check that the new name is not part of an existing one.
Withdrawing: do not wait for an audit
A role should be withdrawn on the day of a change of position or departure from the company. In practice, link this to the HR process: information from HR triggers a task for the administrator. Editing and deleting internal accounts stays reserved for the administrator, the manager and OHS, so withdrawing a role is carried out by exactly this group.
Sample calculation: roles to review after one year
Rules for the administrator account
The administrator assigns roles within their own scope. The e-mail settings tab for external companies is available only to the administrator, and the protection is a role requirement in the API, not merely hiding the option in the interface. The practical conclusion: we do not rely on someone not finding the button. We rely on the role being checked on the server side.
Roles differ between installations, because the full list of roles depends on configuration. Before assigning a role we do not know from another plant, we check its scope in the permission matrix of that installation.
Documenting decisions
Every assignment or withdrawal of a role above the basic level should have a short record: who asked, who approved, from when and for how long. This way, at the quarterly review, the administrator does not have to reconstruct the reasons from memory. In plants with several halls the record also includes the area the role concerns.
It is also important that a request for a role comes from a supervisor, and that the decision is made by a person with the appropriate place on the ladder. The administrator should not be both the requester and the approver for the same change.
Role lifecycle in three steps
For most plants a simple cycle is enough, repeated for each change.
- A supervisor's request with justification and a time scope.
- A decision by a person holding a higher role on the ladder, and assignment of the narrowest role.
- Quarterly review: confirmation or withdrawal.
Checklist
Video
Frequently asked questions
Can an administrator assign a role higher than their own?
No. An actor cannot assign a role higher than their own, and the seniority ladder has no equal rungs, so every change requires a person higher up the ladder.
Why can't role names contain each other?
User search by role relies on text matching. If one name contained another, a query for the lower role could return accounts holding the higher one. An automated test guards this.
Is the list of roles the same in every plant?
No. The full list of roles depends on the configuration of the installation, so before assigning an unfamiliar role, check its scope in the permission matrix.
Let's organize role assignment
We will show the seniority ladder of roles in a demo and help prepare the procedure for assigning and withdrawing permissions.
Let's talk