InnerWeb
Skip to main content

Role split during system rollout at a packaging plant

A corrugated packaging manufacturer with a plant in Poland and headquarters in Germany launched visitor registration by phone and had to decide who in the system could do what. Settling the role split before the first invitation kept the gatehouse free of administrative work and kept hosts away from employee data.

2
tiles visible to an account with only the Inviter role
Source: internal card
55 min
window for grouping calls into one per company
Source: internal card

Starting point: one gatehouse and many hosts

A corrugated packaging plant receives drivers, service technicians, customer auditors and staff of external companies every day. Entry requires a health declaration, which the BRCGS standard makes mandatory, and an OHS induction in several language versions. Guests register with their own phone, and QR code labels are printed on request.

Before go-live, a question came up that returns first in most rollouts: who may invite guests, who approves them, and who sees the full list. If every employee received broad permissions, the gatehouse would have to verify every invitation. If only security had permissions, inviting would become a bottleneck.

The rollout team therefore started by matching roles to what people already do in the plant, not from a list of system functions.

Three roles, three scopes

The system is built on inherited roles and a scope matrix that defines the access level for each area. At this plant three roles were used for guest handling, built on the principle that the narrower the task, the narrower the role.

Security: gate and verification at entry

Security handles entry, checks the guest's QR code and sees the lists of expected visitors. It remains the owner of gate decisions: admit, refuse or call the host. It does not manage permissions or edit company data.

Secretariat: administration of guests and companies

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. The Secretariat 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 and not flooded with alarms from people who make no decisions at the gate.

Inviter: a narrow role for departments

The Inviter role gives access only to the external companies and guests module: inviting guests and companies, pre-registering visits and viewing external lists. After logging in, an account with only this role goes straight to the external companies view and sees just two tiles. A purchasing or quality manager therefore does not see permits, reports or settings.

Sample calculation: accounts by role

Sample calculation: accounts by roleBar chart of sample account numbers: security 8, secretariat 3, inviters 40, administrator 2.010203040accountsSecurity: 8 accounts8SecuritySecretariat: 3 accounts3SecretariatInviters: 40 accounts40InvitersAdministrator: 2 accounts2Administrator
Source: Sample calculation based on assumptions: 1 gatehouse running 4 shifts of 2 people each, 3 people in the secretariat, 40 inviters from departments and 2 administrators.

Boundaries the system enforces on its own

An Inviter cannot invite an internal account, edit an internal company or read its coordinators. The system answers with access denied. This matters at a plant where employee data flows to HR and to the access card system, while guests run in a separate workflow.

Only roles with full access to external companies and guests can grant the Inviter role, so an employee without those permissions cannot hand them to another account. Editing and deleting internal accounts stays reserved for the administrator, the manager and OHS. There is also a licensing benefit: an Inviter does not take an active user license in the training module, so a large group of inviters does not raise the cost of training licenses.

An external company may have a default contact person who acts as coordinator. At this plant it was set for regular suppliers, so an alarm about a guest without valid training reaches the right person on the company side, not the plant security. Calls are grouped into one per company within a 55-minute window.

Rollout sequence

The rollout team followed a sequence that works in plants with one gatehouse and several dozen inviters.

  • First the security and secretariat accounts, since they will run the first registration tests.
  • Then a short list of inviters from the departments that invite most often: purchasing, quality, maintenance and logistics.
  • Next, default coordinators for regular external companies.
  • Finally the language versions of the induction and the notification channels, once the roles are stable.

Outcome and lessons

After go-live the gatehouse handled guests who held invitations rather than invitations themselves, and the list of inviters could grow without changing the scope of security. Access card events stayed with the provider of that system, and InnerWeb took them only to the extent needed to connect with attendance and working time records.

The main lesson concerns the order of decisions: first establish who invites, who verifies at the gate and who administers, and only then configure the modules. Roles differ between installations because the full list depends on configuration, so the split is worth writing down in a short document before start.

It is also worth remembering that InnerWeb is an independent system that complements the plant's existing systems. The owners of access control, time and attendance and HR remain in the responsibility matrix as separate parties.

Video

Frequently asked questions

Can an inviter see the list of plant employees?

No. The Inviter role gives access only to the external companies and guests module. An attempt to invite an internal account or to read the coordinators of an internal company ends with access denied.

Why doesn't the secretariat receive refusal alerts?

It is a deliberate design decision. The Secretariat is not a gate account and does not make gate decisions, so alerts go to security and to the people responsible for the team.

Does a large number of inviters increase the cost of training licenses?

No. An Inviter account does not take an active user license in the training module.

Let's settle roles before the first invitation

In a demo we will show how the role split works for security, the secretariat and inviters in a plant like yours.

Let's talk