Chapter 5 of 8 · Assurance
Built to be inspected
Trust shouldn't rest on a sales deck. These are the standards the showroom itself is built to, and most of them you can inspect inside it.
Permissions enforced by the database
Every business table carries row-level security, so a role's permissions apply the same way on every screen and report a signed-in person uses. The few server jobs that need wider access, such as demo set-up and scheduled clean-ups, are limited to their task.
Admin › Roles in the showroom
Organisations kept apart, and tested
An automated check seeds one organisation with a row in every table, then confirms another organisation, an anonymous visitor and a signed-out client can't read, change or delete any of it.
Runs on every change, before release
A complete audit trail
Creates, edits, stage moves, assignments and decisions are recorded with the person, the time and what changed.
Admin › Audit in the showroom
Tested on every change
Database tests check each rule and policy; end-to-end tests walk the key journeys on desktop and mobile; automated accessibility checks test pages against WCAG 2.1 AA rules.
Automated in the delivery pipeline
Sign-in built for real inboxes
Passwordless one-time codes, emailed links that corporate scanners can't use up, rate limits on every step, and two-step verification for platform administrators.
Try it when you open the showroom
Releases that can't outrun the database
Schema changes reach production only through the pipeline, and a new release won't serve traffic until the database it needs is in place. The previous release keeps running until then.
How every release is deployed
Inspect it yourself
Decide an approval, then find the evidence
The approval tour takes three minutes: you decide a real request in the demo company, then see exactly what was recorded about it, and by whom.