InnerWeb
Skip to main content

Approving self-registration guest accounts: notes for administrator and security

A QR poster at the entrance lets a guest create an account on their own, but an account from self-registration does not activate by itself. Notes for the administrator and security during the pilot: who at a food plant approves such accounts, in what order, and what to do with a guest who finished training without setting a password.

4
roles authorised to approve an account
Source: karta
2
ways to create an account: invitation and self-registration
Source: karta

Two ways to create an account

A guest can have an account from an invitation or from self-registration, for example from a QR poster. An account from an invitation activates by itself once the password is set, because a person with permissions invited it. An account from self-registration requires approval by a person with permissions: security, administrator, manager or OHS.

The difference matters at a food plant, because self-registration is an entry route for people nobody in the plant knew about in advance. Approval is the moment when someone at the plant decides that this person may proceed further.

Who approves and when

The authorised roles are security, administrator, manager and OHS. For the pilot we recommend naming one person per shift, rather than leaving the matter open. Most often this will be security, which sees the guest at the gate, but in a plant with a day reception it may be the secretariat escalating the matter to security.

The person must be named in the instructions. Otherwise accounts from the poster will wait for someone who thinks it is not their task, and the guest will be standing at the gate.

What to check before approval

The approver should compare the registration data with an invitation, a visit or a delivery order. If the person is not expected and their company does not appear in the system, approval should not be automatic. The health declaration requirement applies to accounts from external companies and guests, so after approval the account still needs a declaration on that day.

Guest account path: number of actions on the plant side (rough rating)

Guest account path: number of actions on the plant side (rough rating)Bar chart: an invitation requires one action on the plant side, a QR poster requires two.012actionsInvitation: 1 actions1InvitationQR poster: 2 actions2QR poster
Source: Sample calculation: an invitation requires 1 action from the inviter, the QR poster adds approval

Guest after training without a password

A typical situation in the pilot: a guest from the poster completed the training but did not set a password, because they wanted to get in as quickly as possible. The system handles this in a way that does not block entry: a guest after training without a password enters through the gate as an active account with the status No password. Account activity therefore does not depend on the password, which is needed only to log in to the portal.

Recommendation for the administrator: do not treat the No password status as an error. The status is information that the account still needs a password if the guest is to come back. Invite them to set a password at their next visit, or send an invitation with a code.

Pitfalls during the pilot

The first pitfall is a build-up of unapproved accounts after a weekend. If nobody has a morning queue review in the instructions, accounts will wait a day or two. The second is confusing the two routes: security approves the poster account and assumes that guests from invitations also need approval too, which slows deliveries down. The third is failing to distinguish an account after training without a password from an inactive account, which at the gate gets the first denial code.

A reminder of the order of denial codes: inactive account, missing health declaration, missing training, missing qualifications, expired permit, no permit or visit. An unapproved account from the poster stays inactive, so it will be the first cause of refusal.

Recommendations for the pilot

For a pilot at a food plant a few decisions made before the start are enough.

  • Name one person per shift responsible for approving accounts from the poster.
  • Record in the security instruction that the No password status does not block entry.
  • Set a morning review of the queue of unapproved accounts.
  • Make sure a manager or OHS officer can cover for security if needed.
  • Separate the messages: guests from invitations activate themselves once they set a password.

Checklist

Video

Frequently asked questions

Does an account from the poster activate by itself?

No. It requires approval by a person with permissions: security, administrator, manager or OHS.

Will a guest without a password get through the gate?

Yes. A guest after training without a password enters as an active account with the status No password.

Does approval replace the health declaration?

No. The health declaration is required on that day regardless of account approval.

Planning a QR poster at the entrance?

We will agree with you who approves accounts on each shift, and go through the No password status before the pilot.

Let's talk