Admin and Settings

Admin & Settings

The configuration and governance surface. Most of it lives under the Admin and Documents nav groups (admin/owner roles).

Users — roster, invites, role assignment, deactivation.
Roles & permissions — a granular resource.action permission matrix on top of the built-in roles; nav visibility is permission-driven. Reference docs: role_permissions.md and Role & Nav Naming Conventions.
SSO — single sign-on setup.
Session policy — token/session security settings.

Settings — branding (company name, logo, colors), integrations, email (SMTP) configuration, tax jurisdictions, defaults — plus a Feature Settings tab for workflow toggles (e.g. hide line-item prices on customer documents, require an invoice before completing a job, estimate expiry, flagging jobs re-closed-out after billing).
Accounting Settings — chart of accounts, posting maps, and the master switch for the internal general ledger; lives in the Accounting nav group, covered in Accounting, Payroll & Reports.
Onboarding — a first-run wizard (profile, catalog, technicians, notifications) that can seed a starter catalog and generate demo data — and clean the demo data up again.
Custom fields — define per-tenant fields on customers and jobs (text, number, date, select, boolean).
Tags — custom labels for customers/jobs, with color and description.
Customer alert tags — admin-managed customer classifications.
Notification templates — the automatic messages the system sends and their SMS/email toggles.
Tech Mobile Settings — per-tenant feature flags for the technician mobile app.

Documents — shared file library (Outlook attachments sync in).
PDF templates — a WYSIWYG editor for invoice/estimate/proposal layouts: drag-and-drop blocks (header, line items, terms, signature), brand colors, fonts, header/footer. The saved template drives the real estimate and invoice PDFs (what you design is what customers receive), including document-level fields — valid-until and signature on estimates, invoice date and paid-to-date on invoices.
Resources — folder structure for job docs (specs, safety sheets, …).

Activity / audit log — virtually every mutation in the app is audit-logged (action, entity, user, details); browse per company, per job, or per customer, export CSV. Entries carry the actor (who did it) and a named subject, and the Recent Activity feed reads the same trail.
Tamper evidence — audit entries form a hash chain, and the chain is verifiable: an admin endpoint (and a nightly check) walks it and reports the first broken link, so silent edits to history are detectable.
GDPR & compliance — data export/erasure requests; destructive erasure requires a server-enforced typed confirmation.
Feedback portal — in-app bug reports and feature requests from your team, stored per-tenant with a "my tickets" list for the submitter.

System Admin / Admin Operations — health and diagnostics, data export/import, the version badge + update check (see Updating).
Database — migration status, ORM-drift detection, on-demand backups (see Backup & Restore).
Server logs — error visibility.
Plugins — install/enable third-party modules (see Using Plugins).
Webhooks — outbound event subscriptions (see Integrations).