Protected controls and the journal
Decide how much checking each control needs before it acts, from none to a second person's approval, and keep a record of everything done at the site that cannot be changed afterwards.
Protection levels
On the site's Controls tab, Protection of each control lists every control on the site's devices. Choose one level for each:
| Level | What happens when someone uses the control |
|---|---|
| No extra check | It acts at once. |
| Confirm the change | The person confirms the new value first. |
| Confirm who you are | The person confirms with their authenticator app, passkey or a recovery code. |
| Second person approves | The change waits until someone else approves it. |
Protection belongs to the device template, so every device built from it is protected the same way. It applies wherever the control is used: dashboards, diagrams and MaxwellTrack AI.
Before you protect a control
Confirm who you are and Second person approves need two-step verification on the account of whoever uses the control. Turn it on in Settings > Security; see Account security.
Automations
For controls at Confirm who you are or Second person approves, the Automations may operate box decides whether automations can still use the control. Leave it unticked for equipment that must only ever be operated by a person.
Confirming who you are
After you confirm once, further protected controls on the same device in the next 5 minutes do not ask again.
Second person approval
- 1
Someone asks
Using a control at Second person approves creates a request instead of acting. It shows under Waiting for approval on the site's Controls tab.
- 2
Someone else approves
Anyone else with control access to that device can approve it; the person who asked cannot. Approving asks them to confirm who they are, then sends the change to the device. Reject turns it down.
- 3
Or it expires
A request nobody approves within 10 minutes expires, and nothing is sent.
If nobody else has control access to the device, the request is refused: share the device at Control level with a second person first. See Workspace.
The journal
The site's Journal tab records what happens at the site, in order: controls and who used them, controls held for a check or refused by an on-device rule, confirmations, approvals and rejections, alarms raised, cleared, acknowledged and shelved (with the reason), on-device rule trips, rules sent to and applied by devices, diagrams saved, and controls used on a gateway's site screen with the operator's name and the time they were made.
Each entry is chained to the one before it. The journal checks the chain every time it opens: it shows Chain intact through entry with the number checked, or the entry from which something was changed after it was written. Export with signature downloads the journal with a signature, for an auditor or an insurer.
Something unclear or out of date on this page? Tell support.
