InnerWeb
Skip to main content

FAQ: permissions of the Secretariat, administration and inviters

When reception at a new plant starts handling external companies and visitors, the first question is who can do what in the system. In InnerWeb the answer follows from three roles with different scopes: Secretariat, Administrative employee and Inviter. Below we explain how they differ and how to assign them, so that no one has more permissions than they need.

How does the system grant permissions in the first place?

Permissions in InnerWeb are not a list of individual checkboxes next to each user. They follow from roles with inheritance, a scope matrix and a ladder for granting roles. Inheritance means that a role at a higher level includes the permissions of a lower one and adds its own. The scope matrix defines which modules and actions a role can reach.

The most important rule for reception and administration is this: no one can grant a role higher than their own. If the Secretariat invites employees, it does not promote anyone above its own level. As a result, expanding the reception team at the next plant does not open a path to granting administrative permissions.

What can the Secretariat role do?

The Secretariat inherits the permissions of the security role and additionally manages external companies and visitors, and invites internal employees. It does not edit or delete accounts. This setup suits a reception that admits a contractor company, registers a visitor and adds a new employee to the system, but should not change the data of existing users.

In practice the Secretariat is the first role worth activating at a new plant. It lets visits be handled even before the implementation manager passes wider permissions to department managers. It is responsible for company and visitor data, not for system configuration.

Number of system areas open to a reception role (sample classification)

Number of system areas open to a reception role (sample classification)Bar chart comparing role scopes: Inviter 1 area, Secretariat 3 areas, Administrative employee 4 areas01234areasInviterInviter: 1 areas1Administrative employeeAdministrative employee: 4 areas4SecretariatSecretariat: 3 areas3
Source: Sample calculation: areas listed in the role descriptions (Inviter: companies and visitors; Secretariat: security, companies and visitors, inviting; administration: permits, reports, companies and visitors, inviting)

What can an Administrative employee do, and what can they not do?

The Administrative employee has permissions for work permits, reports, companies and visitors, and can invite internal employees. They have no access to system settings, teams or alerts. This role is meant for the person who handles the plant's paperwork: prepares permits, processes reports and keeps track of contractor data.

The boundary is deliberate. System settings, team structure and alerts affect the safety of the entire plant, so they stay with higher-level roles. The Administrative employee works on the data but does not change the rules according to which the system operates.

What is the Inviter role, and why does it not use a license?

The Inviter role gives access only to the External companies and visitors module: inviting people, pre-registering visits and viewing lists. It is meant for a production employee or a department manager who receives a guest or a service crew and wants to register them directly, without asking the Secretariat.

The Inviter role does not take up an active-user license in the training module. For a group of plants this matters when planning licences: dozens of people can invite visitors without increasing the number of active training users. Details about documents for visitors on arrival are described in another material on roles.

How do you assign roles at the next plant?

At each new plant check three things. First, who will receive visitors and external companies: these are the candidates for the Secretariat role. Second, who prepares permits and reports: this is the Administrative employee. Third, who in the departments will invite crews themselves: these are the Inviters.

Role names must be unambiguous. In the system no role name may contain another role name as a substring, because searching by role relies on text matching, and an automated test enforces this. When you create your own roles within a group, keep this in mind so that you do not break filtering.

Video

Frequently asked questions

Can the Secretariat delete employee accounts?

No. The Secretariat invites internal employees and manages external companies and visitors, but it does not edit or delete accounts.

Can the Administrative employee change alert settings?

No. They have permissions for work permits, reports, companies, visitors and inviting employees, but system settings, teams and alerts are outside their scope.

How many people can hold the Inviter role?

The system does not tie this role to an active-user license in the training module, so it can be granted to a wide group of people who receive visitors.

Can a plant administrator grant someone a role higher than their own?

No. The role-granting ladder blocks such an assignment, so permissions cannot grow beyond the level of the person granting them.

Opening reception at a new plant?

We will show you a role layout for the secretariat, administration and inviters, matched to the structure of your group.

Let's talk