What this guide covers
This guide explains the current owner-app navigation structure, including the main sidebar modules and the lower account-menu actions for billing and help. It is written for the current JobsiteOn implementation and avoids assumptions about unshipped behavior.
Before you begin
- Confirm you can access the relevant route(s) for this workflow.
- Use sandbox first when testing a new process or policy update.
- Keep this article open while you execute each step so your team can follow one consistent path.
Workflow overview
- Open the main route you need from the sidebar.
- Use the lower account menu for workspace, billing, theme, and help actions.
- Validate downstream impact before handoff.
- Document exceptions and close the loop with your team.
Step 1: Open the correct route and confirm context
Start from /dashboard and confirm you are operating in the intended workspace
and environment.
Route checklist
- /dashboard
- /inbox
- /schedule
- /contacts
- /properties
- /team
- /quotes
- /jobs
- /invoices
- /settings/company
- /settings/workspace/billing
Step 2: Use the sidebar and account menu intentionally
Use the main left sidebar for day-to-day production work:
/dashboardfor the owner overview/inboxfor communication/schedulefor appointments and dispatch/contacts,/properties,/team,/pricebook,/quotes,/jobs, and/invoicesfor record workflows
Use the lower-left account menu for personal and workspace-level controls:
- The compact
REMAINING CREDITScard sits above the account menu, opens/settings/workspace/usage, keeps the remaining-percent line above the bar, and shows the reset date below it - The remaining-credit bar is blue above 70%, orange from 31%-70%, and red from 0%-30%
- Clicking your profile row opens
/settings, which now lands on theYour Profilepage Settingsis a direct account-menu entry to/settingsBilling & Plansis a direct account-menu entry to/settings/workspace/billingfor live subscription and billing detailsTheme,Help and resources,Sandbox mode,Beta features, andSign outremain directly accessible from the same menuHelp and resourcesopens support destinations without leaving your current owner-app session context first
Step 3: Use Help and resources
From Help and resources in the account menu:
Help Centeropens/helpon the public JobsiteOn siteGetting startedopens the owner onboarding article at/help/getting-started/first-login-checklist-for-ownersSuggest improvementsends a feedback email tofeedback@jobsiteon.comReport an issuesends an issue email toissues@jobsiteon.com
Feedback and issue submissions include the signed-in user, workspace, billing state, page URL/title, request timestamp, and IP address when available so the support team can triage without asking the owner to re-type their account context.
Step 4: Validate downstream impact
After the main action completes, verify that related modules reflect the update. The expected downstream impact for this area is faster first-week execution and fewer setup errors.
Step 5: Handle exceptions quickly
If the expected result does not appear:
- Refresh the current page and confirm the record status.
- Verify required linked entities (contact/property/team/job/invoice context as applicable).
- Re-run the action in sandbox if live-state confidence is low.
Step 6: Keep the process repeatable
Capture the final operating sequence for your team and reuse this article as the reference runbook. When behavior changes, update this article in the same change set as the product update.
Validation checklist
- Primary route opened successfully.
- Help Center and Getting started open the expected help routes.
- Feedback and issue submissions open the correct dialog and submit without blocking errors.
- Downstream module behavior matches expected workflow.
- Team handoff information is complete.
Troubleshooting
I cannot access one of the listed routes
Confirm account permissions and environment selection. If access is still blocked, route the issue to your admin/support path with the exact URL.
I saved changes but I do not see the result
Reload the route, confirm linked records, and validate whether this workflow is beta-gated in your workspace.
My screen layout looks different
Layout can vary by feature flags or viewport size. Keep following route names and workflow checkpoints from this guide.
FAQ
Is this available in every workspace?
This guide documents generally available behavior in current production routes.
Should we run this in sandbox first?
Yes. Sandbox-first execution is recommended for process changes and first-time team rollout.
How often should this process be reviewed?
Review whenever related auth/onboarding/module/release behavior changes.
Notes
This article covers currently available behavior in active production routes.