InnerWeb
Skip to main content

Access control roles: 7 recommendations for reception and security

Reception, the secretariat and the employee inviting visitors need different permissions from security or the administrator, and a single account with full access makes errors easy. The head of security can split the roles so that everyone does their own job and sees no one else's settings. Below are seven recommendations based on what each role can actually do.

3
roles for handling visitors: Inviter, Secretariat, Administrative employee
Source: card
7
recommendations for reception and security
Source: card

Who these recommendations are for

The recommendations apply to a plant where visitors and external companies are registered by several people: security at the gate, the secretariat, administrative employees, and employees who invite their own visitors. The addressee is the head of security, who assigns roles, and the system administrator, who configures them.

The starting point is the rule that permissions in InnerWeb follow from roles with inheritance and a matrix of scopes. Roles are granted according to a seniority ladder: a role cannot grant a higher role, and the Secretariat cannot grant the role of Administrative employee. This limits the risk that someone promotes themselves or a colleague.

Recommendations 1 and 2: start from the narrowest role

Recommendation 1: give people who only invite visitors the Inviter role. It provides access only to external companies and visitors: inviting visitors, pre-registering visits and viewing lists of external parties. It cannot invite an internal account, and after logging in the user goes straight to this screen, so they see nothing beyond their scope.

Recommendation 2: do not grant a wider role just because it is more convenient. An employee who invites a supplier once a week does not need access to permits or settings. A narrower role means fewer places where a mistake can cause damage.

Number of areas each role covers (illustrative view)

Number of areas each role covers (illustrative view)Illustrative bars: Inviter 1 area, Secretariat 2 areas, Administrative employee 4 areas01234areasInviterInviter: 1 areas1SecretariatSecretariat: 2 areas2Administrative employeeAdministrative employee: 4 areas4
Source: Illustrative view from the role description: Inviter (companies and visitors), Secretariat (security, companies and visitors), Administrative employee (permits, reports, companies and visitors)

Recommendations 3 and 4: the secretariat without account editing

Recommendation 3: assign the Secretariat role to the secretariat. It inherits the security permissions and additionally manages external companies and visitors, but it has no read-only mode of security and no editing or deleting of accounts. Reception therefore registers visitors and companies without touching user accounts.

Recommendation 4: for people who also handle permits, use the Administrative employee role. It has work permits, reports, companies and visitors, and inviting internal employees, but it has no system settings, teams or alerts. This is the natural choice for an office that coordinates the work of external companies.

  • Inviter: external companies and visitors, no internal accounts
  • Secretariat: inherits security, manages companies and visitors
  • Administrative employee: permits, reports, companies, visitors
  • None of these roles: system settings, teams, alerts

Recommendations 5, 6 and 7: inheritance, review and exceptions

Recommendation 5: plan the roles on paper before configuration, because a role inherits permissions. Draw the ladder from Inviter up to the administrator and check who may grant which role. If two people should grant roles to each other, a role above both of them is needed, not a workaround.

Recommendation 6: once a quarter review the list of accounts and roles. A person who changed position often keeps the old role. A review takes a dozen minutes for a few dozen accounts and reveals inactive accounts that should be blocked.

Recommendation 7: record exceptions. If someone receives a role wider than the standard, note the reason and the review date. An exception without a date becomes a rule over time.

What these recommendations do not solve

Roles govern access to the InnerWeb panel, not to doors. The plant's access control system, its readers and cards remain a separate world: InnerWeb does not manufacture readers and integrates with the client's existing system. The recommendations therefore concern who registers visitors in the panel, not who opens a specific door.

A role also does not replace a procedure. If reception is to know what to do with a visitor without a health statement, this must be described in the instructions. The system will show the gate verdict, but the instructions say what the security officer then says and does.

Video

Frequently asked questions

Can the Secretariat edit accounts?

No. The role has no editing or deleting of accounts, and it manages external companies and visitors.

Can the Inviter invite an internal employee?

No. The role gives access only to external companies and visitors; internal accounts are invited with a different role.

Who grants roles?

The seniority ladder decides: a role cannot grant a role higher than its own, and the Secretariat cannot grant the Administrative employee role.

Let's set up the roles in your plant

Book a conversation with security and the administrator. We will go through the role matrix and choose the narrowest permissions for reception, the secretariat and inviters.

Let's talk