Admin Quickstart

Open the right desks first

1. Start in the admin dashboard and confirm you are in the correct workspace.
2. Check that owners, admins, and field resources have the right access before you begin entering live work.
3. Invite missing users from the workspace user controls instead of sharing one login across the team.
4. If someone accepts an invite but already belongs to another workspace, tell them to complete the invite flow in the browser and then re-open the admin or mobile app in the target workspace.
5. Before you schedule live work, confirm the members who should appear in field assignment pickers have field work enabled and office-only coordinators do not.

Set the estate register before scheduling work

1. Create or import the customer account, then build out each site with the right address, building context, contacts, and site notes.
2. Add systems and assets in the structure engineers will actually inspect in the field.
3. Keep smoke-control and fire-damper records separated at the system or asset layer so inspections, exports, and reports stay clean later.
4. If another system already owns the register, start from the staged import workflow instead of trying to paste the data record by record.

Schedule the first live work

1. Move into Scheduler once the site register is clean enough for dispatch.
2. Create the inspection or scheduled work from the site context rather than keeping the job in notes or email.
3. Choose Exact date when the day and time are already known, and choose Target month when the job must happen in a month but the office has not slotted the visit yet.
4. If the site is new or still being commissioned, you can create the inspection before the live system is confirmed and let the engineer bind the real system during the visit.
5. Review draft versus deployed work deliberately so field resources only see field-ready assignments.
6. Use the backlog and quick-view controls to keep unscheduled demand visible without losing the main planner.
7. If someone is missing from the assignee picker, check their field-work eligibility before treating it as a scheduler bug.

Review outputs early

1. Open Inspections and Reports as soon as the first records land back from the field.
2. Confirm visit notes, defects, and certificate data read the way the customer expects before you scale the workflow.
3. Use report previews for higher-risk outputs instead of downloading the final file blindly.
4. Keep the notification bell visible in the top bar so mentions and collaboration prompts do not get buried while the office team is triaging outputs.

Keep feature visibility realistic

1. Treat quotes, work orders, AI-assisted actions, analytics, and some finance features as workspace-availability decisions, not guaranteed defaults.
2. If a desk is missing, check workspace access and enabled features before assuming the portal is broken.
3. Collaboration surfaces also follow role rules: notifications are tied to the signed-in user, while the cross-resource Activity Feed is an admin Collaboration desk.

Troubleshooting

Reference surfaces

1. Use the Admin Page Index when you need the full route inventory rather than the onboarding path.
2. Jump into Dashboard, Scheduling, and Reports for desk-by-desk control detail.
3. Use the Admin Route Interaction Matrix when the real question is how one office page hands work to another.