InnerWeb
Skip to main content

Checklist before granting access to a new user

Excess permissions usually come from haste: a new person needs access from today, so they receive a role with a margin. This checklist forces five questions before the click and takes a few minutes. Each point comes with a comment on why it is on the list.

How to use this list

The list is gone through by the person granting the role, ideally the administrator or the Secretariat, for each new account and for each change of scope. The answers do not need to be archived in a separate tool: a short note in the access request, with the date and the name of the approver, is enough.

If the answer to any question is I do not know, the role is not granted. The rule sounds strict, but in practice it saves time, because unknowns surface only during an audit, when they are most expensive.

Questions about the person and the tasks

The first question concerns the need: which specific tasks in the system will this person perform in their first month. For a contract owner who is to invite visitors, the Inviter role is enough, not an administrative role.

The second concerns the minimum scope. The Inviter role gives access only to external companies and visitors, while the Administrative Clerk adds work permits and reports, but not settings, teams and alerts. Choose the narrowest role in which the tasks can be performed.

Example: accounts with an excess role out of 20 checked

Example: accounts with an excess role out of 20 checkedBefore and after chart: 6 accounts with an excess role without the checklist, 1 account with the checklist (sample values).0246accountsWithout checklist: 6 accounts6Without checklistWith checklist: 1 accounts1With checklist
Source: Illustrative example to be measured in your own plant, 20 accounts assumed

Questions about the permissions of the person granting

Roles are granted along the seniority ladder: an actor cannot grant a role higher than their own. Before granting, make sure that you, and not a colleague from another department, have the right to grant this role, because a higher role rejected by the system means lost time and an unnecessary workaround.

The Inviter role is granted only by roles with full access to external companies and visitors. This means an employee without such permissions cannot pass them on to another account. If the administrator sees an attempt to get around this, it is added to the list of events for review.

Questions about reserved actions

Editing and deleting internal accounts stays reserved for the administrator, the manager and the health and safety officer. If the new person is to perform this action, it is not solved by granting a general role, but by a deliberate decision about who in the position fulfils the administrative function.

The settings tab for the e-mail of external companies is available only to the administrator, and the protection is a role requirement in the API, not merely hiding it in the interface. Do not count on the absence of a button being enough: check whether the role allows the action, not whether the menu shows it.

Questions about role names and documentation

No role name may contain another as a substring, because user search by role works on text matching. If the plant has its own roles, check before granting that searching by this role does not return users from another role.

Finally, record who granted which role to whom, on what basis, and set a review date. The entry should be readable for a person who does not know the matter, because that person will open it during an audit.

Checklist

Video

Frequently asked questions

Can a new user receive a role with a margin for later?

No. A role is granted for current tasks, and any extension requires a separate decision. A margin is the most common source of excess permissions.

Who can grant the Inviter role?

Roles with full access to external companies and visitors. This prevents the permissions from being passed on by someone who does not hold them.

Is hiding a button in the interface enough protection?

No. The protection is the role requirement in the API, and hiding a button is only a convenience for the user.

Let us put the checklist into your process

We will help turn the list into an access request form and a role granting protocol for your plant.

Let's talk