Administration, roles & security

Administrators manage people in the users/org area: invite new users, edit roles and departments, deactivate leavers and set reporting lines. What each administrator can do is bounded by their own role and scope.

Access is role-based with data scopes — company, branch, department, team, reporting line or self. A branch administrator sees their own branch, not the whole company. Every permission check reads effective permissions on the server, and you can grant or revoke individual permissions on top of a role.

Yes. Companies can define custom roles with their own permission set and data scope, alongside the built-in roles. A guard prevents anyone from creating a role that grants more than the creator holds.

Create branches, departments and teams in the organisation structure. They drive data scopes and reporting, so a manager or branch administrator automatically sees only their part of the company.

Set a person's manager to build a reporting line. The "reports" data scope then lets a manager see the people who report to them (directly or down the chain), separate from department or team scope.

For sensitive changes you can require a second administrator to approve them — a four-eyes gate. The change is parked until approved, then replayed exactly as requested. You choose which changes are sensitive.

In Settings → security, enable the company two-step sign-in requirement. Platform operators always require it. Each person then enrols an authenticator the next time they sign in.

Password policy (a company may only tighten the baseline), lockout after repeated failures, password expiry, idle sign-out, concurrent-device limits and, for operators, an IP allowlist. These live under Settings → security.

Open your sessions view to see where you are signed in. You can revoke one session, all others, or every session; administrators can end sessions for their users. Sign-ins are recorded in the audit log.

Administrative actions — sign-ins, permission changes, exports, downloads, payments, settings and support access — are written to an audit log the company can read and export. It is the record of who did what, and when.

Settings → feature controls lets an administrator switch whole modules on or off company-wide. A disabled feature is hidden from navigation and blocked on the server, not just visually removed.

Governance settings are opt-in switches for automatic behaviours — asset auto-mapping, network discovery and duplicate detection — and the Automation panel adds a periodic sweep plus a run-now control with a summary of what it did.

Upload your logo and choose an accent colour under Settings → company branding. The console applies them for everyone in the company, keeping contrast accessible, and your logo appears on exports.

Yes. An administrator can export the company's tenant data. The export is the company's own data only — tenant isolation is enforced at the query layer — and it is audited.