Settings reference
Every Settings tab and every toggle - what each section is for, each control, its default, and what it changes downstream.
Settings (/app/settings) is the Administrator's console - the whole surface requires the Administrator role, and some tabs additionally require a plan feature (noted below). This page walks every tab and every control, in the order they appear in the Settings sidebar: what the section is for, what each toggle does, and where its effect shows up.
Most tabs write to a shared organization-settings record; changes broadcast immediately to the rest of the app, no re-login needed.
Organization
What it's for: your identity and formatting defaults - the things every export, email, and screen inherits.
| Setting | Default | What it does |
|---|---|---|
| Company logo | none | Shown in the app and on PDF exports (max 2 MB, resized; no SVG) |
| Company name | empty | Displayed throughout the app |
| Contact email / phone | empty | Contact address used for system notifications |
| Timezone | Eastern | How timestamps render |
| Date format | MM/DD/YYYY | How dates render app-wide |
| Currency | CAD | One of 10 codes; every money value formats in it (a label, not a conversion) |
| Industry category | none | Your FCI benchmarking peer group |
| Industry benchmarking | off | Opt-in to share anonymized FCI and see industry averages; disabled until a category is set |
| Infrastructure module | off | Turns the Infrastructure surface on; only visible on plans with the infrastructure feature |
| Address | empty | Stored on the organization record |
Notifications
What it's for: which events generate email and in-app notifications, and which roles receive them. Targeting is organization-level by role - users don't have individual preferences.
| Setting | Default | What it does |
|---|---|---|
| on | Master gate for all outbound notification email | |
| In-app | on | Master gate for the in-app notification bell |
| Email notification logo | none | Logo stamped on notification emails; falls back to the company logo |
| Work orders: enable | on | Master toggle for the work-order family |
| Work orders: new assignment | on | Notify on assignment |
| Work orders: status & reassignment | on | Notify on status changes and reassignment |
| Work orders: notify roles | Admins, Managers, Staff | Which roles receive work-order notifications |
| Work requests: new request | on | Notify when a request is submitted |
| Work requests: notify roles | Admins, Managers | Which roles receive request notifications |
| Contracts: expiration | on | Feeds the expiring-contracts check (90-day window) |
| New requester signup | on | Notify when a requester self-enrolls (e.g. via Domain Access) |
Import & Export
What it's for: the import wizard - 22 entity types in dependency order, each with Import, CSV Export, and Template buttons. Rows with unmet dependencies stay disabled until you import what they need. Also home to infrastructure import/bulk-update shortcuts, bulk document upload, and the bulk QR-code export.
Access & Security: Domain Access
What it's for: automatic enrollment - anyone signing up with your verified email domain joins your organization as a Requester, no invitation needed.
One domain per organization. Adding it is a three-step dialog: enter the domain (public providers like gmail.com are rejected), receive a code at an address on that domain, verify with the 6-digit code. Each row shows a Verified/Pending badge; the trash icon removes the domain (and stops auto-enrollment). A verified domain is also the prerequisite for Single Sign-On (below).
Access & Security: Single Sign-On
What it's for: routing your email domain's sign-ins through your identity provider. Enterprise plan (or SSO add-on); requires a verified domain first.
Add a connection (Okta, Entra, Google, or custom SAML/OIDC) via IdP metadata URL or manual entity ID + sign-on URL + certificate. Each connection has an Active switch (default off) - activating routes that domain's sign-ins to the IdP. The screen provides the ACS URL, SP entity ID, and metadata URL your IdP needs. See Security.
Work Management: Work Orders
What it's for: how work orders behave, when they're due, and what the form shows. Three cards.
Behavior:
| Setting | Default | What it does |
|---|---|---|
| Auto-assignment | off | Incoming work auto-assigns by group site + category matching; also gates work-request auto-approval |
| Assign creator | off | New work orders default their creator as assignee |
| Require work category | off | Category becomes mandatory on work orders and portal requests |
| Require manager approval | off | Restricts work-request approval to Manager and above |
| Staff default to My Work Orders | off | Staff land on their own queue instead of the full list |
| Conversation email notifications | off | Emails requesters/staff on new conversation messages |
Due-date calculation - days added to the start date per priority: Urgent 0, High 3, Medium 7, Low 14 (each 0-365).
Form sections - per-section Visible and Collapsed switches for Priority, Work Category, Assignment, Schedule, Financial, Safety, Tasks, Parts, and Attachments (Safety, Tasks, and Parts default to collapsed). Title, status, and priority fields are always present. Hide what your teams never fill in - a shorter form gets filled in more honestly.
Work Management: Requester Portal
What it's for: what requesters see and what they can point a request at.
| Setting | Default | What it does |
|---|---|---|
| Show work order status | on | Requesters see the linked work order's status when tracking a request |
| Show completion notes | on | Requesters see the technician's completion notes |
| Allow location requests | on | "Where is the problem" can target a location |
| Allow asset requests | on | Requests can target a specific asset |
| Allow system requests | on | Requests can target a system |
| Allow infrastructure feature requests | on | Requests can target an infrastructure feature; only shown when the Infrastructure module is on |
At least one request target must stay enabled - the form refuses to save otherwise.
Work Management: Email Intake
What it's for: turning inbound email into work requests - each address you create is a mailbox at requests.assetlab.ca you can hand to tenants or print on signage. Full workflow: Email intake.
Per address (edits save immediately):
| Setting | Default | What it does |
|---|---|---|
| Enabled | on | The kill switch - disabled addresses bounce nothing, they just stop creating requests |
| Default site | none | Stamped onto requests from this address |
| Default priority | Medium | Priority for created requests |
| Default category | none | Work category for created requests |
| Who can send | Any sender | Any sender / Known requesters only / Allowlist only |
| Allowed sender addresses | empty | Shown only for Allowlist policy; newline/comma-separated emails |
Financial & Risk: Financial
What it's for: the math behind asset value and condition metrics. Requires the intelligence plan feature.
Asset valuation metric - a radio pair, default FCI: choose Facility Condition Index (condition-based) or Net/Gross PP&E depreciation (age-based, financial-reporting flavor). Saves immediately and switches the dashboard gauges, lifecycle forecasts, and reports between the two models.
Current replacement value (CRV):
| Setting | Default | What it does |
|---|---|---|
| Calculation method | Inflation-based | Inflation-based (purchase cost escalated by years elapsed) vs. static multiplier (age-independent) |
| Annual inflation rate | 2.0% | Used in inflation mode (0-15%); CRV = purchase cost × (1 + rate)^years |
| Global CRV multiplier | 1.0 | Used in multiplier mode (0.1-10) |
| System-level overrides | off | Multiplier mode only: lets per-system multipliers override the global one |
These settings feed FCI, the lifecycle forecast, and the replacement planner - one basis everywhere.
Financial & Risk: Risk Profiles
What it's for: named consequence-of-failure presets. Requires the intelligence plan feature.
A profile is a name, a consequence score (1-5, Very Low to Critical), and a description - "Mission-critical", "Life-safety", "Cosmetic". Attach a profile to a system and its assets inherit the consequence; likelihood stays condition-derived. Per-profile actions: edit, delete (systems using it lose their default; assets keep current values), and Apply to assets - re-stamps consequence on every asset whose system uses the profile, skipping any asset whose consequence was set by hand. Details: Risk & FCI.
Integrations: Microsoft Teams
What it's for: posting events straight into a Teams channel - no relay needed.
Add a Teams workflow webhook URL, pick from five events (work order created, work order status changed, PM schedule due soon, asset out of service, work request submitted), and toggle Active. Per row: send test notification, edit, delete. A built-in setup walkthrough covers the Teams side.
Integrations: API Keys
What it's for: external access - REST API and MCP/AI assistants. Enterprise plan or API add-on. Full guide: API keys.
Create dialog: key name, rate limit (1-1000 requests/min, default 60), expiry (default 90 days, max 365), and the scope grid - per-resource read/write checkboxes across 14 groups, with Read Only / Full Access shortcuts. The Users scope raises a privacy confirmation before it can be enabled. Per key: an active switch (off = requests rejected immediately) and delete. The plaintext key shows once at creation; a Recent API Activity card lists the last 100 requests, filterable by key.
Integrations: Outgoing Webhooks
What it's for: pushing events to your systems. Same plan gate as API keys. Full guide: Webhooks.
Create dialog: name, HTTPS endpoint URL, and the 8-event checklist (work order created/updated/deleted, asset created/updated/deleted, work request created/updated), plus an Active switch. The signing secret shows once. Per row: send test event, delivery logs (last 100, with retry state), edit, delete. Ten consecutive failures auto-disables a webhook; re-enabling the switch resets the failure counter.
Modules: Infrastructure
What it's for: the Infrastructure module's admin home. Visible on plans with the infrastructure feature; five panels, ordered the way you set them up.
| Panel | What it holds |
|---|---|
| Feature classes | The class catalog - code, label, category, color, sort order, unit replacement rate and unit (m, each, m², m³), service life, and a rate-reviewed date. Built-in classes can't be deleted or have their code changed (details) |
| Networks | Each network's name, its one feature class, and its condition scale (0-100 score, or 1-5 grades in either direction) |
| Esri sync | GIS source connections - service URL, layer, target network, field mapping, filters, and per-source sync enablement (details) |
| Replacement rates | Per-material replacement cost and service life - the middle tier of the rate chain (feature's own value → material default → class rate). Every material your live features carry gets a row automatically, whether it arrived by Esri sync, file import, or manual edit; the first edit saves its defaults |
| Basemaps | Custom raster basemap sources for the map |
User Management: Users
What it's for: billable members and their roles. Full guide: Users & invitations.
The header shows your billable seat count against the seat limit. Add User invites by name, email, and role (default Staff); at the seat limit, only Requester invitations go through. Per row: role select (guarded - you can't demote yourself or the last Administrator, and promotions are blocked at the seat limit), a Workspace select (All / Facilities only / Infrastructure only - shown when the Infrastructure module is on, for Manager/Staff rows; scopes which module's nav the member sees), group badges, edit name, and remove. A pending-invitations card lists outstanding invites with per-row revoke.
User Management: Requesters
What it's for: the non-billable requester population - kept apart from Users so the billable list stays honest.
Same controls as Users (invite with Requester preselected, role select, edit name, remove, pending invitations) with one twist in reverse: promoting a requester to a billable role checks the seat limit first.
User Management: Groups
What it's for: site- and specialty-scoping for notifications and assignment suggestions. Full guide: Roles, groups & permissions.
Creating a group is a five-step wizard: type (Requester or Operational - which member pool is selectable), name/description, members, sites (what the group's users see and where they're suggested for work), and scope (system classes and work categories). A group with work categories is a specialist - matched first when auto-assignment (Work Orders tab, above) runs; one without is the generalist fallback. Deleting a group removes its member, site, and class assignments. An in-app explainer on the tab walks the matching logic with a worked example.
User Management: Labour Rates
What it's for: the rates that turn logged hours into labour cost at work-order completion.
Set a tenant default rate (applied to anyone without a personal rate, so labour cost is never silently zero) and per-member rates. Rates are effective-dated: saving adds a new rate row from a chosen date rather than overwriting, so work completed earlier keeps the rate that was in force. Each member has a rate history view (entries individually deletable). Set loaded rates, not wage rates, or your O&M totals will flatter you.
Catalog maintenance
Several small catalogs live under Settings and quietly shape data quality: asset statuses, work categories, cost categories, building and location types, project phase categories. The shared rule: short lists stay used; long lists get ignored. Merge before you add.