First-task help
Start with one useful outcome in the right account and property. Your invitation, active role and permitted scope determine which records and actions are available. Public walkthroughs contain synthetic examples and do not create a workspace.
Operator: review one request
Open the work queue, select a request and read its property, current state and responsible person. Check urgency, approved scope and evidence before assigning or updating work. Review the result and reload the record to confirm the saved state.
Owner: review one decision or report
Select the property and period first. Open the pending decision or published report, inspect its costs and supporting evidence, then use the actions permitted to you. If the data is unavailable, ask the operating team to resolve it before treating the page as an empty queue.
Vendor: understand one assigned job
Open an assigned job and review the offer version, access window and required proof. Confirm the appropriate company or technician scope. Review an action's receipt and current job state before retrying an uncertain submission.
Field: complete the correct visit
Select the assigned visit, confirm the property and instructions, then record observations and linked media. Check whether work is saved on the device, queued, synced or submitted. Keep the device copy until the server confirms the required evidence and visit outcome.
Advisor: read one reviewed report
Open an authorized property report and check its period, publication state and version. Follow the source and evidence links available to you. Ask the responsible owner or operator about decisions; the advisor perspective is read-only.
If access or setup is blocked
For an expired invitation, identity-provider problem or MFA question, use access help. Describe the account, role and intended task at a high level. Keep passwords, recovery codes, access codes and private guest data out of the request.
If a save or upload is uncertain
Read the reported state before repeating the action. Device-saved work and queued uploads are not server receipts. Reload the exact record when possible, preserve pending work and ask the operating team to resolve an unknown outcome rather than submitting duplicates.
Choose a role and workflow walkthrough or review the account model.