Getting started
A tour of the Facility Hub web app, how the core entities fit together, and what to set up first.
Overview
Facility Hub on the web is the full-surface version of the product — deeper tables, admin configuration, analytics, and workflows that are impractical on a phone. This page is a short tour you can share with new teammates or read after logging in for the first time.
How the pieces fit together
The web app is organized around five core concepts:
- Locations — the sites your organization operates. Everything else is tagged to a location. Organizations with a single location skip the location picker on create forms — it is filled in automatically.
- Assets — the equipment and fixtures at those locations.
- Tickets — work orders for things that need doing.
- Checklists — reusable templates for recurring work.
- Vendors — outside service providers you hire for specialized work.
Supporting features wrap around those five:
- Service records track what happened to an asset over time.
- Relationships connect assets that interact with each other (serves, powers, contains…).
- Asset groups bundle assets together for shared service configuration.
- Label templates and QR codes let anyone scan into an asset's public landing page.
- Automation rules apply changes automatically when tickets are created or linked to assets.
- Analytics summarize throughput and backlog across locations.
Navigation
The left sidebar has top-level destinations. From top to bottom:
- Dashboard — your organization-wide starting point.
- Assets — list, service records, and relationship graph. See Assets.
- Tickets — the work queue with filters and bulk actions. See Tickets.
- Checklists — templates, schedules, responses, and exports. See Checklists.
- Analytics — charts and tables for ticket and asset performance. See Analytics.
- Vendors — your service-provider directory. See Vendors.
- Users — member management (admin only). See Users.
- Settings — personal and organization configuration. See Settings.
Help at the bottom of the sidebar brings you back to these docs. Notifications (the bell) shows @mentions and assigned work.
Common first steps
- Open Settings and confirm your profile details.
- If you are an admin, review Settings → Locations and make sure every site has a name, address, timezone, and status.
- Import or create your first Assets. CSV import is the fastest path when you are moving from a spreadsheet.
- Set up a default Label template and print labels for the assets you plan to service first.
- Build at least one Checklist template for a recurring routine.
- Try the full loop: scan a QR label, submit a guest ticket against the asset, and triage it from the web.
Roles at a glance
| Role | Typical access |
|---|---|
| owner | Everything, including billing and organization changes. |
| admin | Full admin surface: users, locations, templates, automation rules. |
| employee | Day-to-day use of assets, tickets, checklists, vendors. |
| user | Baseline access — mostly for limited guest or contractor use. |
Exact permissions are enforced per page (for example, admin-only pages such as Users and most of Settings).
When to switch to mobile
Use the Mobile app tab in the docs dropdown for field workflows: completing checklists at a site, creating tickets from a phone, scanning QR labels, and working offline-friendly tasks. Features like Analytics, Users, the asset relationship graph, CSV import, and automation-rule configuration are web-only.