InnerWeb
Skip to main content

External company and guest registration: questions on accounts and transfers

A guest who changes employer should not start training from zero or receive a new identifier just because the company has changed. We answer the questions of coordinators and safety departments about what stays with the account during a transfer, who is responsible for an external company and how group invitations work.

144
addresses in one group invitation request
Source: karta
5 / 13 min
request limit per user
Source: karta
1
account per person after a transfer to another company
Source: karta

Why a guest account should survive a change of company

In production plants the same contractor is often employed by several companies within a year: a subcontractor takes over a contract, a service technician changes agency, a driver moves to another carrier. From the point of view of safety it is the same person, with the same history of training and entries. If the system treats that person as a new user, the plant loses the evidence that the safety training really took place, and the safety departments repeat the same work.

Moving a guest to a company in the system keeps the same account, so training results, identifiers and gate entries travel with the person. The account is one entity and the company is its attribute. This is also the answer to the auditor's question: for one person you see one history, without duplicates.

What stays with the account and what changes

The most frequent question is: what exactly moves to the new company? Training results, identifiers and gate entries stay. The assignment to the company changes, and with it the contact person on the plant side and, if so configured, the scope of access that depends on the contract.

The second question concerns security: can someone attach another person's account by mistake? Attaching an existing account requires an explicit confirmation, so a coordinator cannot move a person with one accidental click. It is a simple barrier that in practice prevents mix-ups between people with similar surnames.

  • Stays: training results, identifiers, gate entries.
  • Changes: assignment to the company and the contact person.
  • Required: explicit confirmation when attaching an existing account.

Limits of group invitations

Limits of group invitationsBar chart: 144 addresses per request, 5 requests, limiter window of 13 minutes.050100150wartoscAddresses per request: 144 wartosc144Addresses per requestRequests in the window: 5 wartosc5Requests in the windowLimiter window (min): 13 wartosc13Limiter window (min)
Source: Documentation of the external companies and guests module

The contact person of an external company

In the module for external companies each company can have a contact person chosen from the list of coordinators. This is the employee of the company whom the plant calls when a guest does not show up for a visit, or who is reminded about a training that is about to expire.

The server checks that the choice is correct: it rejects a person from another company and a person without the coordinator role. This prevents the situation in which the contact person of company A is an employee of company B, chosen from a drop-down list by surname. Check that every active contractor has an assigned coordinator before you start group invitations.

Group invitations: limits and system behaviour

The Invite several guests window works in three steps: pasting the addresses, preview, sending. One request covers at most 144 addresses, and the limiter allows 5 requests per 13 minutes per user. In practice one coordinator can invite several hundred people to an event within a dozen minutes, but this does not flood mailboxes or load the server.

An important note: a group invitation does not create accounts or activation links. The guest registers personally in the portal, which leaves one entry point into the access request process. The plant therefore has one control path, not two parallel ones, and does not manage the passwords of people who have not registered.

How a guest entry reaches the evacuation list

Recording a guest's entry or exit from the list writes a gate entry, so the guest appears on the list of people on site and on the evacuation list. This has organisational consequences: a secretariat member or a host who marks a guest's entry by hand creates an entry on which the later assembly point list depends.

This should be said during training for hosts: during a group visit it is not allowed to mark entry in advance for the whole list if the guests have not arrived yet. The evacuation list must be real, not planned.

Video

Frequently asked questions

Does a guest who moves to another company have to repeat the training?

The system keeps the same account, so training results travel with the person. Whether the training is sufficient in the new company depends on the rules of the plant, but the history is not lost.

Can I choose a contact person from another company?

No. The server rejects a person from another company and a person without the coordinator role.

Does a group invitation create accounts for guests?

No. The guest registers personally in the portal, and the system does not create accounts or activation links from the address list.

Does marking an entry from the list affect the evacuation list?

Yes. Recording an entry or exit writes a gate entry, so the guest appears on the list of people on site and on the evacuation list.

Let us put external company accounts in order

Book a call about registering contractors and guests. We will show an account transfer and a group invitation on the scenario of your plant.

Let's talk