Onboarding Checklist

A practical checklist to onboard a tenant and prepare a small field team for production use.

Pre-configuration (admin)

• [ ] Create tenant and assign an initial administrator.
• [ ] Configure Mapbox with a per-tenant public token in Settings → Integrations → Mapbox Configuration. (Per-tenant tokens isolate billing and avoid demo token limits.) :contentReference[oaicite:11]{index=11}
• [ ] Configure push notifications and any other tenant integrations needed.
• [ ] Set tenant defaults: timezone, working hours, address format and phone defaults.
• [ ] Create or import sample clients, technicians, and at least 3 sample jobs for a pilot test.

Permissions & users

• [ ] Invite staff and assign roles: at minimum, an admin, a dispatcher/manager, and at least one technician.
• [ ] Verify technician accounts can sign in, are clocked in/out, and have location permissions enabled.

Mobile & Offline testing

• [ ] Verify PWA install on desktop and mobile. See PWA install steps in the Mobile & PWA articles. :contentReference[oaicite:12]{index=12}
• [ ] If using native apps, test local builds (Capacitor: npx cap add <platform>, npm run build, npx cap sync). :contentReference[oaicite:13]{index=13}
• [ ] Test offline behavior: create job updates and photo uploads while offline and verify automatic sync on reconnect. The app queues job updates, photos, payment records, and client notes for automatic sync. :contentReference[oaicite:14]{index=14}

Map & routing

• [ ] Confirm the Jobs Map loads and that sample jobs appear at expected locations. Access via /maps/jobs. :contentReference[oaicite:15]{index=15}
• [ ] Verify technician location updates while clocked in and that the job drawer quick actions (navigate, call/text) work. :contentReference[oaicite:16]{index=16}

Pilot day

• [ ] Run a pilot day with a small team: create real work orders, assign technicians, and validate routing, photos, and sync.
• [ ] Collect feedback from technicians (mobile/PWA experience, camera, offline behavior).
• [ ] Resolve any role or permission issues before full roll-out.

Go-live

• [ ] Confirm production Mapbox token and integrations are in place (no demo tokens). :contentReference[oaicite:17]{index=17}
• [ ] Communicate go-live schedule and required steps to the field team.
• [ ] Monitor the first week for sync failures, map errors, and support requests; escalate to dev/ops as needed.

Tip: Keep a short “cheat sheet” for technicians (how to clock in/out, how to take photos, and how to trigger a sync). This reduces friction during the first days of production.

Updated on: 10/01/2026