Skip to content
CP SHEQ Control Plane Docs

The Control Panel

What the Control Panel is, who uses it, and how it's different from the SHEQ application itself — companies, deployments, and getting from one into the other.

Last updated 12 September 2026 · v1

Overview

The Control Panel (portal.sheqcontrolplane.com) is a separate application from SHEQ Control Plane itself. It's where a customer's own SHEQ manager or administrator manages the companies they administer and the deployments (sites) under each — not where day-to-day SHEQ work (incidents, hazards, permits, and the rest) happens. Everything documented elsewhere on this site — the modules, the workflows, the registers — belongs to the SHEQ application, reached from inside the Control Panel or directly at a deployment's own address (for example <deployment-id>.sheqcontrolplane.com).

Think of the Control Panel as the administrative layer above the product: one login can administer several companies, each company can have several deployments, and each deployment is its own running instance of the SHEQ application with its own users, data, and address.

Why it matters

An organisation with more than one site — several mines, several branches — doesn't want to manage each one as a completely separate product. The Control Panel is where an administrator sees all of it in one place: which companies they administer, which sites belong to each, and a single click through to the actual working application for the site they need. Someone who only ever works in one deployment's SHEQ application day-to-day may never need to open the Control Panel at all.

How it works

Signing in to the Control Panel is a separate account from any deployment's own SHEQ application login — creating a Control Panel account (Create an account on the sign-in page) does not by itself create a user in any deployment. Sign-in is the same style of branded, direct-API form used elsewhere in SHEQ Control Plane (no redirect to a bare hosted login page); after signing up, a verification code is emailed before the new account can sign in.

Once signed in, the Control Panel shows the companies the account has a role on. Selecting a company shows its deployments — each with a tier, region, current status, and an Open app button. Open app doesn't just link to the deployment's address: it hands the browser off already signed in, in a new tab, as the same person, with the Control Panel role mapped onto the equivalent role inside that deployment's SHEQ application (a company administrator lands as an admin-level user there; a viewer lands with view-level access). There's no second login to do.

Note: Open app is only enabled once a deployment actually has a recorded application URL. A deployment that's still being provisioned, or has none recorded yet, shows the button disabled rather than sending you to a broken link.

What happens next

See Companies and deployments for how the two relate, what a company administrator can do that a viewer can't, and what a deployment's tier and status actually mean.