Great field operations start with clear guidance

What this guide covers

This guide explains how to configure workspace and company defaults safely for Company Settings Map. 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

1. Open the correct route and confirm workspace context.
2. Complete the core workflow action in order.
3. Validate downstream impact before handoff.
4. Document exceptions and close the loop with your team.

Step 1: Open the correct route and confirm context

Start from /settings/company and confirm you are operating in the intended workspace and environment.

Route checklist

• /settings/company
• /settings/company/branding
• /settings/company/people
• /settings/company/regional
• /settings/company/hours
• /settings/company/service-area

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.

• /settings/company now uses Google Places-backed address search for the main business-address field.
• /settings/company now saves reliably even when optional fields like website, address line 2, or tax ID are left blank, so you can keep only the required company details without triggering a save failure.
• Selecting a suggestion fills the street, city, state, ZIP, and line 2 when available, now commits on the first click or tap, and still leaves manual entry available when needed.

Branding route specifics (/settings/company/branding)

Use this route to configure both app branding and document rendering:

• Company logo uploads now require a crop step before save and support original/wide/standard/square framing.
• Company icon uploads now require a square crop before save.
• Company logo and icon are the same assets used across workspace chrome, PDFs, and branded emails. There is no separate workspace-logo surface anymore.
• Saved icon updates the collapsed workspace mark and browser tab icon after branding refresh.
• Workspace URL and the shared workspace inbox address are edited on this same branding route.
• Primary brand color for in-app accents.
• Document PDF palette (brandColor, textColor, mutedColor, lineColor, paperColor).
• Document labels (quote/proposal/invoice titles plus reference/date/valid-for/due-date labels).
• Header/footer behavior (company-name display toggles, registration-number override).

These settings are consumed by quote/proposal/invoice renderer output and by the default outbound quote/invoice email styling. Quote and invoice draft preview refresh still reflects the current branding values after save.

People route specifics (/settings/company/people)

Use this route for live workspace team management:

• review active members
• create new invites from Create a team or Invite people
• resend pending invites
• cancel pending invites

This is the canonical replacement for the retired Workspace -> People destination.

Regional defaults specifics (/settings/company/regional)

Use this route to control the shared regional defaults consumed by schedule and other customer-facing time/date surfaces:

• The canonical route stays /settings/company/regional, but the settings sidebar now surfaces it from Settings -> General -> Regional Defaults.

• timeFormat switches between the default lowercase 12-hour display (4:00pm) and 24-hour display (16:00).

• weekStartsOn changes weekly calendar ordering and month-grid alignment.

• timezone, dateFormat, currency, and distanceUnit remain part of the same cached company-settings contract.

Regional defaults are now cached client-side and refreshed from the same /settings/company source used by /settings/company, so changing either screen updates the shared frontend settings source for schedule pages.

The same shared date/time picker module is now used anywhere owner-web asks for a date or clock value in the main workflow surfaces, including schedule create/edit, Find a Time, company hours, quiet hours, jobs, requests, quotes, invoices, and dispatch audit/coverage forms. That keeps the interaction model consistent: use the dropdowns for quick selection or type the value directly.

Step 3: Validate downstream impact

After the main action completes, verify that related modules reflect the update. If you changed the business address through address search, reopen /settings/company and confirm the saved fields still match before relying on the location in scheduling or document flows. If you intentionally leave optional fields like website or tax ID blank, confirm /settings/company saves successfully and the cleared fields stay blank after a refresh. If you changed the workspace URL in branding, confirm the updated inbox address is the one your team now shares. The expected downstream impact for this area is more predictable behavior across all modules.

Step 4: Handle exceptions quickly

If the expected result does not appear:

1. Refresh the current page and confirm the record status.
2. Verify required linked entities (contact/property/team/job/invoice context as applicable).
3. 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.
• /settings/company/people shows live team members and pending invites when relevant.
• Quote/invoice draft preview refresh reflects current branding values.
• Saved logo/icon/workspace URL changes render in workspace chrome and document/email surfaces as expected.

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.

Related Articles

• Workspace Settings Map
• Security Commitments Overview