InnerWeb
Skip to main content

Courier, supplier and guest roles: setup recommendations

Without an invitation, a person can join training on their own only in three transitional roles: supplier, courier and guest. The effect depends on which companies the administrator assigns to these roles. Below are recommendations on how to set the three roles so that the plant does not open registration wider than it intended.

3
roles available for self-registration
Source: feature card
3
separate company settings, one per role
Source: feature card

For whom and why

The recommendations are intended for the IT administrator and the head of security, who are responsible for who can create an account without an invitation. Employees of the plant and of external companies enter through an invitation or the registration module. Only the transitional roles, namely supplier, courier and guest, allow self-registration.

This boundary is an advantage: nobody can create an employee account for themselves. However, the boundary lies in the settings: it is the administrator who names the companies for each role. A wrong configuration turns a controlled channel into an open door.

Recommendation 1: three roles, three separate settings

Which company acts as supplier, courier and guest is a piece of data for the installation, not a fixed part of the system. Each of the three roles has its own setting, because the name and identifier of the "Courier" differ in every plant. Do not copy the configuration from another plant and do not assume that the identifiers are the same.

Reason: two installations can have entirely different companies with names close to "Courier", and the system does not recognise roles by name.

Recommendation 2: one company per role, no multi-purpose companies

Assign to the courier role a company intended only for couriers, to the guest role a separate one, and to the supplier role a separate one. Avoid a collective company called "External". Only separate companies allow lists to be filtered, entries to be reported and different training requirements to be set.

Reason: the training scope, the zone rules and the security report usually differ for a courier and for a guest. A shared company forces shared rules.

Recommendation 3: check that the setting is not empty

The company to which a registering guest is assigned comes from the self-registration settings. When the setting is empty, the system reports an explicit error instead of guessing. Before go-live, register a test courier, a test supplier and a test guest, and check which company the accounts were assigned to.

Reason: an explicit error is convenient, but someone has to see it before the first real courier arrives.

Recommendation 4: do not assign companies that have employees to the roles

If you assign to the guest role a company in which there are also people with long-term access, self-registration mixes two populations: transitional visitors and people with permissions. Transitional roles should contain only accounts that are by nature one-time.

Reason: access control starts from clean lists; once the populations are mixed, an audit requires manual separation.

Recommendation 5: for deliveries with a notice, use a separate module

Truck drivers arriving with a plant delivery notice follow a different path: the notice card code fetches the delivery data from the client's system over SOAP and pre-fills the form. The courier role is for a courier with a parcel, not for a truck driver.

Reason: putting truck drivers into the courier role hides the delivery data and duplicates registration.

Recommendation 6: once a quarter, review the accounts in the roles

Accounts in transitional roles multiply quickly. Once a quarter, review the list, remove expired accounts and check that nobody has stayed in a role that no longer matches their real situation. The review takes a dozen minutes and closes the risk of old accounts.

Reason: self-registration is convenient, but it needs periodic clean-up so that the list remains reliable for security.

How to check the configuration in 15 minutes

The acceptance test has four steps. First, open the three company settings and note which companies are assigned. Second, register three test accounts, one in each role, and check their companies on the list. Third, try to join as an employee and confirm that the self-registration path does not allow it. Fourth, record the result in the implementation protocol.

The protocol is evidence for an audit: it shows that registration without an invitation is limited to genuinely one-time roles. InnerWeb is an independent system that complements the client's existing systems, so the same protocol can be attached to the access control documentation without any changes to the readers.

Most common configuration mistakes

The first mistake is assigning one company to all three roles because "it is faster". The result: reports cannot tell a courier from a guest, and the training scope is shared. The second mistake is leaving a temporary company from the test period. The third is assuming that a courier identifier from a previous plant is valid in the new one, which the installation data does not confirm.

The fourth mistake concerns communication: reception and security do not know that self-registration exists, and they register by hand people who could have joined by phone. A short briefing for reception shortens the queue in the lobby and reduces the number of accounts created twice.

Video

Frequently asked questions

Can an employee join on their own?

No. Employees of the plant and of external companies enter through an invitation or the registration module.

Who decides which company is the courier?

The installation administrator, in three separate settings. The name and identifier differ in every plant.

What happens if a company setting is empty?

The system reports an explicit error instead of guessing the company.

Is a truck driver a courier?

No. Truck drivers with a notice are handled by a separate delivery module.

Let's talk about one-time entries at your plant

We will show the path of a guest, a courier and a service technician on sample data and agree what the plant needs to prepare. Book a short presentation.

Let's talk