InnerWeb
Skip to main content

Migrating security and secretariat roles: implementation notes for the administrator

Changing an account's role from security to the secretariat or to an administrative employee looks like one click, but it changes what the person can see and do. An administrator who moves accounts in bulk risks someone losing access to the gate panel, or gaining more than they should. Below are the migration stages and pitfalls, based on what each role actually covers.

3
target roles: Secretariat, Administrative employee, Inviter
Source: card
4
checks after a role change on the test account
Source: card

Why the migration needs a plan

Permissions in InnerWeb follow from roles with inheritance and a matrix of scopes. The Secretariat role 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. The Administrative employee role has work permits, reports, companies and visitors, and inviting internal employees, but it has no system settings, teams or alerts.

It follows that moving an account from security to the Secretariat extends its permissions, while moving it to the Administrative employee role changes its profile: the person gains permits and reports, and loses what the seniority of the security role gave them. Before you start, you need to know which of these effects is intended for each account.

Stage 1: inventory of accounts

List the accounts that are to change role and record for each one: the current role, the target role, the reason and the tasks the person performs every day. It is good to base the list on a conversation with the head of security, because that person knows who in practice registers guests and who handles the gate.

For each account ask three questions. Does the person need access to the gate panel? Will they manage external companies and visitors? Do they need work permits? The answers point to the target role, not to the job title.

  • Current role, target role, reason for the change
  • Daily tasks of the person
  • Need for access to the gate panel
  • Management of companies and visitors, or permits

Migration stages: how many accounts you move at once (example plan)

Migration stages: how many accounts you move at once (example plan)Bars of the example plan: 1 test account, then three groups of 5 accounts each012345accountsTest account: 1 accounts1Test accountGroup 1: 5 accounts5Group 1Group 2: 5 accounts5Group 2Group 3: 5 accounts5Group 3
Source: Example calculation: a plan of 16 accounts in four stages, illustrative assumption

Stage 2: the order of granting roles

The seniority ladder decides who may grant a role: a role cannot grant a higher role, and the Secretariat cannot grant the Administrative employee role. The first changes should therefore be made by the administrator, or by a person with a role higher than both target roles. An attempt to migrate from a Secretariat account will be refused for the higher roles.

Start with one test account. Change its role, log in on that account and check what is visible in the gate panel. Only then move further accounts in groups of a few, preferably outside peak hours, so that reception is not left without access when visitors arrive.

What to check after a role change

After the change, log in on the account and check four things: whether the person sees the gate panel, whether they can register a visitor, whether they see external companies, and whether they have no access to settings. If anything is missing, note it before you move the next accounts.

Stage 3: accounts that only invite

People who only invite visitors need neither the Secretariat nor the administrative role. The Inviter role gives 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.

If during the migration it turns out that some security accounts in practice only invited visitors, move them to the narrowest role. Fewer permissions mean a smaller risk of error, not more work.

Pitfalls and a rollback plan

The first pitfall is assuming that the Secretariat has everything that security has. It inherits the security permissions, but it has no read-only mode of security and no editing or deleting of accounts. If a person was to do something that the Secretariat does not cover, this must be agreed before the migration.

The second pitfall is changing all accounts in one day without a rollback plan. For each group record the previous role, so that it can be restored within a few minutes if there is a problem. The third is the lack of a review after a week. Go back to the list and check whether anyone has reported a lack of access that follows from the scope of the new role.

Video

Frequently asked questions

Can the Secretariat change the role of another account to Administrative employee?

No. The seniority ladder does not allow granting a higher role, and the Secretariat cannot grant the Administrative employee role.

Will an account moved to the Secretariat keep the security permissions?

Yes. The role inherits the security permissions and adds management of companies and visitors, but it has no read-only mode of security and no editing or deleting of accounts.

Can the Administrative employee change system settings?

No. The role has no system settings, teams or alerts.

Plan the role migration

Book a conversation with the administrator and the head of security. We will prepare the list of accounts, the target role for each one and the order of changes.

Let's talk