Security & Compliance

Single sign-on, approved devices and an office network secured the browser and nothing else. The workspace security policy now governs the AWRA app too: per-install device approval, an IP allowlist on every request, and session limits a fingerprint cannot stretch.

Your records are never on a clock; only the audit trail and the logs are. What a retention period removes, what it never touches, and why a plan can cap the audit trail but never shortens it.

What a support transcript has to carry to settle an argument three weeks later — every line, the files themselves, who ended it, and a second copy — and what ours does.

Every operations system is also a mail server. A one-afternoon audit of every message it sends — recipient, switch, second channel, cadence and payload — and how AWRA OpsHub answers each column.

On a shared service your records sit beside other organizations’ and the software keeps them apart. On a dedicated instance they sit in a database of your own. Same product, same releases — a shorter answer to one question.

Separation, keys, region, sub-processors, access, backups, exit and growth: ten questions that reveal how a vendor holds your records, what a good answer sounds like, and how we answer each one.

The questions every vendor security questionnaire asks about hosting, answered for a shared workspace and for a dedicated instance, with what sits behind each answer and the positions we hold.

Most board data policies cover laptops and email and never name the system holding payroll, supplier bank details and the asset register. Seven clauses that close the gap.

A workspace policy and an MDM profile can both reach the same phone, and they answer different questions. The rule is that the stricter one wins on every setting, and that neither can loosen the other.

A crew signs out at the end of a shift and drives back to a site with no coverage. Whether they can open the app comes down to a twenty-four hour window, a sealed session, and a password check that never leaves the phone.

Audit entries here are permanent: no administrator can remove the record of what they just did, because we took that button out. The cryptography we shipped alongside it is the interesting half; the permanence is the important one.

An email address can be an organisation owner, a staff account or a supplier login, and it cannot be two of them. The check that enforces it is deliberately unscoped — because its failure direction points the wrong way.