What this guide covers
This guide explains how to confirm production scope and destination ownership for Supported Apps and Production URLs. 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 correct route and confirm workspace context.
- Complete the core workflow action in order.
- 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 https://owner-api.jobsiteon.com and confirm you are operating in the intended workspace and environment.
Route checklist
- https://owner-api.jobsiteon.com
- https://auth-api.jobsiteon.com
- https://onboarding-api.jobsiteon.com
- https://files-api.jobsiteon.com
- https://realtime-api.jobsiteon.com
- https://init-api.jobsiteon.com
Step 2: Complete the core workflow action
Follow the route sequence above from first screen to final save/submit point. Avoid skipping fields or intermediate review states during first-pass execution.
Step 3: Validate downstream impact
After the main action completes, verify that related modules reflect the update. The expected downstream impact for this area is support triage, deployment validation, and route handoff.
Step 4: 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 5: 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.
- Core action completed 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.