Why the administrator must be named before the rollout ends
In the first weeks of operation, changes to accounts, roles and teams appear every day. If no administrator is named, the changes go to the vendor, which lengthens response times and ties the plant to external support. Naming the administrator before the rollout ends makes it possible to train them on live cases.
The administrator is not the same as the process owner. The owner decides the rules, and the administrator applies them in the system settings.
IT or OHS: selection criteria
There is no single answer. A decision based on three criteria works well.
Scope of changes in the system
If most changes concern accounts, roles and integrations, IT is the natural administrator. If they concern teams, permit templates and areas, OHS or maintenance fits better. Editing and deleting internal accounts is reserved for the administrator, the manager and OHS, so both groups hold this permission.
Availability
The administrator must be reachable during the plant's working hours, including shifts. If IT has no staffing for every shift, a sensible arrangement is a pair: an administrator from IT and a deputy from OHS.
Responsibility for the consequences
Changes to teams and roles affect the safety of people. Therefore an administrator from IT should carry out changes on the instruction of the process owner from OHS, not on their own initiative.
Sample calculation: who makes changes after the rollout
What the administrator takes over from the vendor
The handover should cover explicitly named tasks, so that after the rollout there is no dispute over who is responsible for what.
- Management of accounts and roles within the seniority ladder.
- Management of teams, areas and report categories in settings.
- E-mail settings for external companies, available only to the administrator.
- Quarterly review of roles and teams.
- Contact with the owners of the access control, time and attendance and HR systems on integration matters.
What the administrator does not take over
The administrator does not take over responsibility for the safety process: decisions on approving work remain with the people named in the process. The system does not replace the person managing the works or the authorizing person: it enforces rules, and responsibility stays with the people named in the permit. The administrator also does not approve particularly hazardous work unless they are a user on the plant side with the appropriate role.
The administrator does not take over neighbouring systems either. InnerWeb is an independent system that complements access control, time and attendance, HR and ERP, so their administration remains with the owners of those systems.
Handover step by step
A well-prepared handover takes several short meetings spread over the final weeks of the rollout. The first covers roles and the seniority ladder, the second teams and areas, the third integrations and notifications, and the fourth the emergency procedure and contact with the vendor.
After the handover it is worth agreeing how requests go to the vendor: what the administrator does alone and what they report. Roles differ between installations, so the administrator's scope is recorded in the handover document, not left to general documentation.
Video
Frequently asked questions
Can the administrator be a member of the OHS staff?
Yes. Editing and deleting internal accounts is reserved for the administrator, the manager and OHS, and handling teams and permit templates naturally falls to OHS.
Does the administrator need to know the integrations with access control and time and attendance?
They should know their scope and owners. Technical details stay with the owners of those systems, because InnerWeb works as an independent, complementary system.
After the rollout, is the vendor still needed?
Yes, for development and for changes beyond the administrator's scope. Daily changes to roles and teams, however, are carried out by the plant.
Let's prepare the handover to the administrator
We will plan administrator training on live cases and a handover document with the division of tasks.
Let's talk