Organization Settings
Organization Settings in Command Center is where your tenant configures branding, company profile, project behaviour, and module-related defaults. During a pilot, this is how you align REACTOR with your site — especially settings that affect PTW and who can access pilot modules.
Purpose
Organization-wide settings apply to every user in your tenant. They define how REACTOR presents your organization, which project defaults apply, and which configuration panels are available to admins. Correct setup here prevents pilot users from hitting the wrong workflow options or missing module access.
Who uses this
- Tenant Owner / Tenant Admin — owns org configuration during the pilot
- HSE lead — validates PTW and safety-related project settings with the admin
- Cerb.works — configures baseline pilot settings and assists with changes within scope
Organization Settings lives in Command Center. Personal account preferences are in Control Panel; platform-wide client operations are in Control Room (typically Cerb.works operators, not day-to-day tenant admins).
What the admin configures
The settings area is organized in tabs. For the pilot, focus on what affects daily operations:
- Branding — organization name, logo, and visual identity
- Company — company profile and contact details visible in admin surfaces
- Project settings — project defaults, shifts, permit/PTW configuration, inductions, risk-assessment governance, and project access rules where enabled
- Members & access panels — org-level membership and access policy helpers tied to your tenant
- Elements — reference data and lookups used across modules (when your pilot enables them)
Tabs such as billing, procurement, and document control may be present but are not central to the initial safety pilot unless explicitly scoped.
Typical setup workflow
- Review bootstrap settings applied by Cerb.works at pilot start (org name, enabled modules, baseline project).
- Confirm Branding so users recognize they are in the correct tenant.
- Complete Company contact details your process owner wants visible to admins.
- Open Project settings and walk through pilot-critical sections with your HSE lead — especially permit workflow options and project access.
- Align project settings with how your organization actually runs PTW, observations, and incidents on site.
- After user provisioning, verify a sample Operator and Supervisor see the expected modules and project context.
- Document changes your team makes locally; larger workflow changes should go through Cerb.works so configuration stays supported.
Roles and responsibilities
- Tenant Admin — applies agreed settings and coordinates updates during the pilot.
- Process owner — confirms settings still match operational practice (recommended quarterly in pilot).
- HSE lead — signs off on PTW and safety-related project configuration.
- Cerb.works — implements baseline configuration and supports in-scope adjustments.
Access / permission implications
Organization settings shape what every user experiences:
- Project settings can change PTW steps, permit types, and project-scoped behaviour visible in SHARD.
- Project access policy controls how users relate to projects and sites when that feature is enabled.
- Module-related panels determine which reference data and governance rules modules use.
- Only users with Command Center admin access (Tenant Owner, Tenant Admin, or Cerb.works platform operators) should change these values.
Pilot-safe caveats
- Treat Cerb.works-applied baseline configuration as the starting point — avoid experimental changes without coordination.
- Do not assume SSO, automated identity sync, custom integrations, or tenant-wide security policy enforcement unless explicitly enabled for your pilot.
- Not every tab or sub-panel is required for pilot go-live; stay focused on branding, company profile, and project settings that affect SHARD/PRISM workflows.
- Procurement, billing, and advanced document-control settings are out of scope unless your pilot agreement includes them.
- If a setting change breaks a workflow, roll back with Cerb.works support rather than patching around it in parallel processes.
Where to open it in REACTOR
- Command Center → Organization Settings — branding, company, project settings, and related tabs
- Project settings deep links use tab parameters in the URL when sharing a specific panel with your team
- Related: User Management, Access Control, PTW System (to verify settings in use)