Setup · first-hour checklist
● workspace

Before the first inspection

A clean workspace baseline — roles, policy, defaults.

Lock who can change what, turn on 2FA consistently, and set branding and inspection defaults once so new work does not drift across people or sites.

Roles 2FA Defaults

Spend the first hour here — fixing roles and IDs after go-live costs more than a disciplined pilot building.

Roles & access

Team · role assignments
OwnerBilling · policy
ManagerQA · outputs
InspectorCapture · assigned
Read-onlyCompliance view · no edits
FinanceInvoices · Stripe

Minimal permissions beat “everyone is admin” — fewer surprises at client handover and staff change.

Managers and read-only roles reduce “email me a screenshot” loops while keeping edit rights narrow.

Security policy

Security · 2FA policy
✓All users: 2FA required
✓Two owner accounts with 2FA enabled
✓Recovery codes stored off-device
✓Individual logins — no shared accounts
✓SSO / IdP mapped where required
✓Offboarding checklist · revoke same day

Client data and evidence packs start on day one — decide the rule before the first inspection, not after.

Security IT overview pairs with this page for retention, residency and integration questions.

Branding · defaults · pilot

Settings · consistency
BrandLogo · portal colours · PDF appearance
DefaultsChecklists · severity · pricing map
Door IDsAgree format before first capture
PilotOne building end-to-end, then scale
SupportNamed internal contact for user issues
ReviewWeekly QA slot until programme stable

Full walkthrough lives in the guide below — this is the order teams usually run in the first hour.

Guide below How to use app →

Branding and defaults apply to the next PDF — always preview before the first client-facing pack.