Settings

Settings is split into two layers: personal settings that anyone can change, and organization settings that are restricted to admin and owner roles.

Personal settings

The top of /settings is your own profile:

• Display name — what teammates see on comments, assignments, and activity entries.
• Account details — your email, role, and user status such as active.
• Last active — when you last used the app.

Your mobile-specific preferences (notifications, haptics, theme) are configured on the mobile app.

Organization administration

The sidebar below personal settings links admins to organization-level pages:

• Organization — name, logo, and organization-wide defaults.
• Locations — every site in your organization.
• Join requests — approve or decline pending members.
• Label templates — printable label layouts for QR codes on assets.
• Automation rules — event-driven automations for tickets and assets.

Only admins and owners see these sections. Pending member count is shown as a badge on Join requests when there are unread items.

Locations

/settings/locations is the canonical list of your organization's sites. Every asset, ticket, and checklist is tagged by location name, so this list is the backbone of filtering across the app.

Creating a location

Click Create Location on /settings/locations/create. The form captures:

• Name (required) — what appears in every location dropdown across the app.
• Property type — choose from options such as Health Club, Athletic Club, Fitness Club, Tennis Club, Racquet Club, Wellness Center, Aquatics Center, Studio, Multi-Sport Club, Corporate Office, Support Facility, Outdoor Facility, or Other.
• Display order — controls where the location appears in dropdowns when you want a deliberate order.
• Square footage and year built.
• Address — address line 1 and 2, city, state/region, postal code, and country.
• Latitude and longitude — used to render a Google Maps link on the detail page.
• Phone — the site contact number.
• Timezone — defaults to UTC; common North American and European timezones are pre-populated.
• Description — free-form notes about the location.
• Active toggle — inactive locations are hidden from most pickers but keep their history.
• Cover image — uploaded separately after the location exists, on the detail page.

Locations are flat — there is no parent/child hierarchy. If you run multi-building campuses, create a location per building and use naming conventions to group them.

The location detail page

Opening a location shows three tabs:

• Overview — the cover image (if set), a site snapshot card, address, contact and operations, and coordinates. A sidebar shows counts of related assets and tickets.
• Floor Plans & Images — upload and manage images associated with the site.
• Documents — the shared documents card. Attach leases, safety plans, vendor contracts, inspection reports, and so on. The same 10 MB per file limit and safe-type rules apply as elsewhere.

From the header you can:

• Edit — open the full edit form (same fields as create).
• Deactivate / Reactivate — toggle the isActive flag. Deactivating keeps history but hides the location from most pickers.

Editing a location

/settings/locations/{id}/edit exposes every location field, plus cover image upload and deletion. Cover images are stored in a dedicated storage bucket and deleted when replaced or cleared.

Label templates

/settings/label-templates controls the printable label layouts used when you download QR labels for assets (see Assets → Labels and QR codes).

• Create Label Template — build a new layout with name, physical dimensions (width and height in inches), and a JSON-driven layout configuration.
• Duplicate — copy an existing template as a starting point.
• Set as default — one template per organization is marked as the default; it is preselected in the download dialog.
• Edit — change layout, dimensions, and metadata.
• Delete — remove a template you no longer need.

The preview on the template detail page shows exactly how the QR code and text will render at the template's chosen size.

AHU-204

Roof Top Unit 4

North Campus

The same preview component is used in the template editor and the docs.

Automation rules

/settings/automation-rules lets admins build event-driven rules that update tickets automatically. See Tickets → Automation rules for the user-facing picture; this section documents how the configuration itself works.

Rule structure

Every rule has:

• Name and description.
• Trigger — the event that evaluates the rule:
  • Ticket created
  • Asset attached to ticket
• Execution mode:
  • Automatic — the actions apply without any human intervention.
  • Suggestion — the actions are offered to an admin to accept or reject.
• Conditions — zero or more conditions combined with AND. Each condition targets a field on the ticket or the asset and uses one of the operators equals, not equals, contains, or greater than or equal.
• Actions — one or more actions of type:
  • Set field — change one of: name, description, category, location, priority, or status.
  • Assign user — set a specific user as the ticket owner.

Tips for writing good rules

• Start in Suggestion mode while you tune the conditions, then flip to Automatic once you are confident.
• Use Asset attached to ticket to run rules late in the flow — for example, after a guest's QR-scanned ticket gets its asset association, you can route it to the owner of that equipment.
• Combine priority and category conditions to escalate specific combinations (e.g. Plumbing + High → set status to In Progress and assign your on-call plumber).

Join requests

/settings/join-requests is where admins approve or reject people who requested access to the organization. The settings landing page shows a count of pending requests. Approving a request activates the user; rejecting it removes the request.

Organization

/settings/organization holds top-level organization details. Use it to update your organization name and any organization-wide defaults.

Configuration for the taxonomy that shows up on assets and tickets — asset types, subtypes, status sets, ticket categories, ticket statuses, and asset relationship types — is exposed through the same organization settings area.

Related pages

• Assets for the asset taxonomy that lives in organization settings.
• Tickets for how automation rules and categories are applied in practice.
• Users to manage roles and access.

Mobile differences

The mobile app focuses on personal settings — notifications, appearance, and account actions. Administrative configuration (locations, label templates, automation rules, join requests) is available only on the web.