InnerWeb
Skip to main content

Minimum permissions: security and secretariat

At a plant gatehouse two groups often meet: security, which decides on entry, and the secretariat, which prepares visits. The minimum permissions principle requires that each group has as much as it needs for its tasks and no more. Below are recommendations on how to divide permissions and why the secretariat should not be a gate account.

Why security and the secretariat should be separated

Security is responsible for the gate and for entry decisions, often under time pressure and with shift staffing. The secretariat is responsible for preparing visits, for contact with external companies and for inviting employees. Mixing these tasks in one account means the person at the gate gets access to configuration, while the secretariat gets alarms that do not concern them.

In the system, the Secretariat role inherits the permissions of security and additionally manages external companies and guests and invites internal employees. It cannot edit or delete accounts. Inheritance means the secretariat sees what security sees, but not the reverse: security does not get management of external companies.

Recommendations for the gatehouse

The division for the gatehouse rests on one question: who makes the decision at the gate, and who prepares the visit in advance. The answer sets the scope of each role.

What to leave with security

Security should have access to the lists of expected guests, QR code verification and the handling of refused entries. This is its job at the gate, so refusal notifications should go precisely to it. It should not manage external companies or invite employees, because that pulls attention away from watching the entry.

What to give the secretariat

The secretariat gets management of external companies and guests, and the inviting of internal employees. It does not receive refusal notifications and is not a gate account. This is a deliberate design choice, so that it is not mixed with security. For the plant this means a clear division of who reacts at the gate and who prepares the visits.

What not to give either group

Editing and deleting internal accounts stays reserved for the administrator, the manager and OHS. Neither security nor the secretariat should have such scope. Account permissions are a matter for the person responsible for the process, not for the duty officer at the gate.

Sample calculation: accounts with access to managing companies

Sample calculation: accounts with access to managing companiesBar chart comparing accounts with full access to managing companies: 43 with an extended secretariat, 3 with the Inviter role.010203040accountsExtended secretariat (Secretariat): 3 accounts3Inviter role (Secretariat): 3 accounts3SecretariatExtended secretariat (Inviters from departments): 40 accounts40Inviter role (Inviters from departments): 0 accounts0Inviters from departments
  • Extended secretariat
  • Inviter role
Source: Sample calculation based on assumptions: 3 people in the secretariat and 40 inviters from departments.

Inviter as a role below the secretariat

If guest invitations concern many departments, instead of extending the secretariat it is worth using the Inviter role. It gives access only to the external companies and guests module: inviting guests and companies, pre-registering visits and viewing external lists. An account with only this role sees just two tiles.

An Inviter cannot invite an internal account or edit an internal company, and the system answers with access denied. Only roles with full access to the module can grant this role, so the Inviter cannot pass it on further.

Administrative employee as an intermediate role

The Administrative employee role has access to the list and opening of work permits, reports, companies and guests, and to inviting employees, but not to system settings, teams and alerts. It suits people who must view permits but do not change the configuration. In a plant with a large administration it is a sensible role for an HR or purchasing employee involved in external company visits.

Check before assigning roles

Before assigning roles to the gatehouse group, it is worth going through a short list of questions.

  • Does the person make decisions at the gate? If so, the security role.
  • Does the person prepare visits and manage external companies? The Secretariat role.
  • Does the person only invite guests from their own department? The Inviter role.
  • Does the person need to edit or delete accounts? Only the administrator, the manager or OHS.

Video

Frequently asked questions

Can the secretariat edit employee accounts?

No. The Secretariat role does not edit or delete accounts. That scope belongs to the administrator, the manager and OHS.

Why doesn't the secretariat get alerts about refused entry?

The secretariat is not a gate account. Refusal notifications go to the people who decide at the gate, so that those preparing visits are not distracted.

Can security invite guests?

As a rule, inviting is the job of the secretariat and the inviters. Security stays at the gate and verifies entry.

Let's split the gatehouse permissions

In a demo we will show the accounts of security, the secretariat and the inviter, and their views in the system.

Let's talk