Workspace setup

The person who creates the workspace becomes its billing owner and an active Admin. In Settings → General, confirm the organisation name, country and timezone. These settings affect scheduling, report dates and service communications.

Use branches to separate locations or operating teams. Assign members only to the branches they need and test access with a non-admin account before importing production work.

Set terminology, report branding, email defaults and a starter template before inviting the wider team. Consistent defaults reduce corrections during the first live inspections.

Terminology settings determine what the interface and reports call things. Aligning them with the language your organisation already uses reduces friction for inspectors and makes reports read naturally to clients who never see the software.

Report defaults — branding, email settings, the report filename pattern — are worth setting before the first live inspection, because existing reports keep the settings that applied when they were generated.

Branches separate locations or operating teams inside one workspace. They are easier to introduce at setup than to retrofit once inspections, templates and assignments already exist across an undifferentiated workspace.

If you are unsure whether you need them, the practical test is whether two groups of people should be unable to see each other's routine work. If the answer is no, a single branch is simpler and easier to administer.

Three recur often enough to be worth naming: inviting the team before templates exist, granting administrative access by default, and leaving the report configuration until after the first client-facing report has already gone out.

All three are recoverable, but each costs more to fix than to avoid. Test access with a non-administrator account before importing production work — it surfaces permission problems while they are still theoretical.