InnerWeb
Skip to main content

Guest roles at a food plant: recommendations for the quality manager and administrator

The health declaration requirement loses its meaning when someone has permissions that let them bypass it. Below are recommendations for the quality manager and the system administrator: how to split the roles of inviter, secretariat and security so that each person does what is theirs to do and the register stays reliable.

3
roles for guest handling: inviter, secretariat, security
Source: karta
4
roles authorised to approve self-registered accounts
Source: karta

Who these recommendations are for

The recommendations are aimed at the quality manager, who is responsible for the evidence for the BRCGS or IFS auditor, and at the system administrator, who grants permissions. A food plant usually has more guests than it seems: service engineers, suppliers, customer auditors, trainers, job candidates. Each of them enters by a different path, and roles decide who can open it.

The health declaration requirement is disabled by default and is switched on with a plant setting in the administrator panel. It applies to accounts from external companies and to guests, while internal employees and accounts without an assigned company are exempt. This is a good starting point for asking who has an account without a company at all.

Recommendation 1: the Inviter role for anyone who brings in guests

The Inviter role gives access only to external companies and guests: inviting, pre-registering visits and viewing external lists. It gives no access to the rest of the system. It can therefore be granted widely, to heads of departments that receive guests, without the risk that someone starts changing the configuration.

The reasoning is simple: the more guests are invited in advance, the fewer decisions are made at the gate. An invitation with a code guides the guest through training and the declaration before they arrive.

Scope of role permissions for guests (number of areas, rough rating)

Scope of role permissions for guests (number of areas, rough rating)Horizontal bar chart comparing the scope of permissions of the guest roles.012areasInviterInviter: 1 areas1SecretariatSecretariat: 2 areas2SecuritySecurity: 2 areas2
Source: Sample calculation: areas are external companies and guests, and the security functions described in the role descriptions

Recommendation 2: the Secretariat inherits from security, but does not edit accounts

The Secretariat role inherits the security permissions and manages external companies and guests, but it cannot edit or delete accounts. This split suits a reception desk that prints labels and registers guests, but should not change employee data.

At reception the verbal declaration field is optional and does not block printing a label. The reason is practical: the secretariat also prints labels for guests who ordered by phone or email and are not standing at the counter. For this reason we recommend that the secretariat is not the only point where declarations are confirmed, and that the gate enforces the requirement.

Recommendation 3: only security confirms verbal declarations

In the security panel the guard confirms a verbal declaration with a button on the person's card, and the entry remembers the confirming person. We recommend that only security uses this route, because every verbal entry then carries the guard's name and time. A separate description of good practice for the security manager is available on the page about the verbal declaration.

Recommendation 4: visits without work are planned by a manager, OHS or the administrator

A visit by a guest with no work to do, such as a conversation, a quote or measurements, is planned by the administrator, a manager or an OHS officer from the panel for external companies and guests. On the day of arrival security can also do it from the refusal card at the gate, always for today. For the quality manager this is a useful distinction: a visit planned in advance has a host, while an ad hoc visit leaves a trace of security.

Recommendation 5: only an internal employee can be the host

Every planned visit has a host, meaning an active internal employee of the plant. The coordinator of an external company does not plan visits, because they would thereby bypass the permit requirement. We recommend not extending this rule with exceptions, even for trusted suppliers.

Recommendation 6: self-registered accounts are approved by a few people

An account from self-registration requires approval by a person with permissions: security, administrator, manager or OHS. We recommend stating in advance who does this on each shift, and describing it in the instructions, so that accounts do not wait without an owner.

Recommendation 7: review roles once a quarter

Each quarter the administrator should check the list of accounts with the Inviter and Secretariat roles and the list of accounts without an assigned company. An account without a company is exempt from the declaration, so it must not be given to people from outside. The result of the review is worth attaching to the audit documentation.

Checklist

Video

Frequently asked questions

Can the inviter change employee data?

No. The role gives access only to external companies and guests.

Can the secretariat delete accounts?

No. The secretariat inherits security permissions and manages external companies and guests, without editing or deleting accounts.

Who is exempt from the declaration?

Internal employees and accounts without an assigned company. That is why accounts without a company should be reviewed regularly.

Sources

Want to put guest roles in order?

We will walk through assigning roles and reviewing accounts without a company, so the declaration requirement has no gaps.

Let's talk