getting started
Admin quickstart (15 minutes)
Stand up your first tenant, invite your team, install one module, and review your first record — in under a quarter hour.
15 min read · 3 sections
Before you start
A tenant is created the moment your email is verified during sign-up. If you skipped the tenant-naming step you can rename it later at /settings/tenant — the slug only changes when you explicitly rename it.
- You are the first member and hold the tenant-owner role — full permissions, no restrictions.
- Your 14-day trial starts when the tenant is provisioned. Billing does not become chargeable until you enter a payment method.
- All your data lives in the region your account was provisioned in (US by default). Enterprise plans can choose EU, UK, AU, CA, or AE.
Step-by-step walkthrough
- Open /settings/members and invite 2–3 teammates by email. Assign them tenant-admin if you want a second pair of hands, or tenant-user for read/write without settings access.
- Go to /modules and browse the template library. Install Inspections, Incidents, or Audits — whichever maps to the first workflow you want to replace.
- On the installed module, open the Composer (pencil icon) and review the default fields, workflow, and permissions. Nothing is locked — rename fields, drop unused ones, and tweak the workflow states.
- Use the Preview tab to run through the form as an end user. The preview hits the real runtime, so you are testing what your team will see.
- Back on /modules, click Create record and submit one. You have just exercised the full round-trip: form → validation → workflow state machine → audit log.
- Open /settings/branding and upload your logo + brand color. The app rebrands instantly — no re-deploy required.
What to do next
- Configure single-sign on — see the Admin guide → SSO setup article.
- Add your location hierarchy so records can be scoped by site / building / floor — Admin guide → Location hierarchy.
- Publish your first Composer change as a versioned release — Composer → Workflows.