The Settings hub
Settings is the organised home for everything that configures your organisation, grouped so each thing has a clear place.
What it is
Settings is grouped into five areas: Organisation (general details, branding, capture policy, app configuration), Integrations (API & webhooks, SSO & provisioning, AI, data sources, notifications, SFTP servers, mail log), Data & compliance (data & exports, audit log), Account (your own sign-in security, appearance), and Billing. Which sections you can open, and whether you can view or edit them, depends on your role baseline plus any per-module override.
How to do it
- Open Settings from the sidebar.
- Choose a section from the grouped list — each one opens a focused screen for that area.
- Capture policy changes (on-site GPS requirement, optional modules, currency and units) apply the moment you save them.
- App configuration changes are staged as a draft: an unsaved-changes bar appears with Save changes or Discard, and navigating away with unsaved edits prompts you to confirm first.
- To review or change what a specific member can access, open Members, use their Manage action, and open Granular permissions.
How it integrates
Every member has a role baseline — owner, org admin, manager, coordinator, finance, viewer, surveyor, operative, or contractor — and an authorised administrator can then tune each product module individually from None through Module admin for a non-owner member. The granular permissions table shows, per module, the role baseline, any per-user override, the effective permission, and the effective scope. Surveyor and operative access to evidence, properties, work orders and scheduling always stays limited to their own assigned records, even with an elevated module permission.
Changes to permissions are enforced server-side: the same checks run on every privileged request regardless of what a client shows, and Storage rules resolve a photo’s owning record before permitting an upload. A signed-in screen may briefly show a loading state while an updated permission document resolves, but a stale token or hidden button can never preserve access that’s been revoked.
Common problems
- A member can’t see a section I expect them to. Check their role baseline and any per-module override under Members → Manage → Granular permissions — most access issues are a permission level, not a bug.
- I changed a setting and it hasn’t taken effect for a survey already in progress. Capture policy is read when a surveyor opens a survey; a change mid-survey applies from the next time they open it, not retroactively to a session already running.
- I can’t grant someone system admin. That level is platform-internal and cannot be granted through the organisation’s permissions editor at all.