User Management
User Management in Command Center is where your organization adds people to REACTOR, assigns tenant roles, and controls which modules they can reach. Getting this right is the first step before pilot users can work in PTW, Observations, Incidents, JADE procurement, or PARTICLES reference data.
Purpose
Every person who logs into REACTOR needs an account tied to your organization with the right role and module access. User Management is the operational surface for provisioning those accounts, updating memberships, and deactivating people who leave — without relying on ad-hoc shared logins.
Who uses this
- Tenant Owner / Tenant Admin — day-to-day user provisioning for the pilot
- HSE or operations lead — validates that the right supervisors and field users are onboarded
- Cerb.works — assists with initial bootstrap users and configuration within agreed pilot scope
This is a Command Center admin task — not the same as Control Panel (personal profile and preferences) or Control Room (platform operator tools).
What the admin configures
- User identity — name, email, active/inactive status
- Organization membership for the active tenant
- Tenant role per membership (Admin, Supervisor, Specialist, Operator, Viewer)
- Module access so users only see pilot cores enabled for your organization (SHARD, JADE, and PARTICLES)
- Optional org teams when your organization has teams enabled
Typical setup workflow
- Confirm your organization context in the REACTOR shell (you manage users for the active org).
- Open Command Center → Users and review who already exists from pilot bootstrap.
- Create or invite each pilot participant with the correct tenant role:
- Tenant Admin — org configuration and user management
- Tenant Supervisor — oversight and approvals where modules allow
- Tenant Specialist — advanced module actions (for example HSE reviewers)
- Tenant Operator — standard field and office users
- Tenant Viewer — read-only access
- Edit memberships to grant module access for SHARD, JADE, and PARTICLES pilot modules.
- Open a user's detail page to review effective access and grant assignments when needed.
- Deactivate users who leave the pilot; avoid deleting accounts if you need audit continuity.
How to add a user
Provision a demo-safe account in Command Center: open user management, start create user, fill identity fields, assign role, and confirm the new list row.
- 1
Step 1
Step 1
User management overview Command Center → Users lists organisation members, roles, and provisioning status — where administrators manage access.
Requires tenant admin or equivalent Command Center access for capture.
- 2
Step 2
Step 2
Add or invite user Use Create user for a new account, or Invite existing person to link a pulse_people record.
- 3
Step 3
Step 3
User identity Enter first name, last name, and a demo-safe email such as demo.help.user+kattegat@example.invalid — never real customer addresses.
Capture opens Create user dialog — do not submit during automated capture unless using a disposable demo account.
- 4
Step 4
Step 4
Assign access Set tenant role, organisation scope, and functional permissions before creating or inviting the user.
Assign-access capture may require opening Create user dialog manually if selectors are dialog-scoped.
- 5
Final step
Final step
Created user record After create or invite, the user appears in the list with role and status — confirming provisioning succeeded.
Roles and responsibilities
- Tenant Owner — ultimate authority over org membership; rarely used for daily provisioning.
- Tenant Admin — maintains the user list, roles, and module access during the pilot.
- Process owner — defines who should be Operator vs Supervisor vs Specialist for each workflow.
- Cerb.works — supports bootstrap accounts and troubleshooting access issues within pilot scope.
Access / permission implications
A user's ability to use pilot workflows depends on three layers working together:
- Active account — inactive users cannot sign in.
- Tenant role — sets the baseline for admin vs operational vs read-only behaviour.
- Module access — limits which cores and modules appear even when the role would otherwise allow them.
Fine-grained workflow permissions (for example PTW approve vs issue) are enforced inside modules and may also depend on grant assignments reviewed in Access Control.
Pilot-safe caveats
- Pilot user onboarding is typically manual — do not assume automated HR or identity provisioning unless Cerb.works has enabled it for your tenant.
- Users are provisioned in the active organization context; switching orgs in the shell changes which directory you manage.
- Keep pilot roles simple: a small set of Admins, Supervisors/Specialists for HSE, and Operators for field staff.
- Prefer deactivate over delete when someone leaves mid-pilot.
- If someone cannot see a module, check membership, module access, and Access Control grants before raising a support ticket.
Where to open it in REACTOR
- Command Center → Users — user list, create user, memberships
- User detail pages — effective access, grant assignment shortcuts
- Related: Organization Settings, Access Control
- Personal preferences (not user admin): Control Panel → Profile