Settings and security
Manage shop settings, team access, operational timezone, and account security.
Settings establish the shared operating rules for the shop. Change them deliberately because they can affect every user and workflow.
Shop and scheduling settings
Keep the shop identity and operating information current. Configure the shop timezone once in Scheduling settings; it is the wall-clock authority for staff and customer operations.
Job tabs and work order IDs
In Settings → Shop → Work orders, choose what identifies an open job tab:
- Vehicle (default), with the work order ID as the first fallback
- Customer, with the work order ID as the first fallback
- Work order ID, with vehicle and customer available when an ID is unavailable
You can also set the human-readable format used for new work orders. The default is {shop}-{year}-{number-6}. For a shop named “Mauri Taller,” a new work order looks like MT-2026-000001.
{shop}uses the first character of the first two words in the shop name, or the first two characters of a one-word name.{year}uses the year in the configured shop timezone.{yymmdd}uses the two-digit year, month, and day in the configured shop timezone.{number-1}through{number-9}define the required unique shop sequence and its minimum padding width. For example,{number-4}produces0001.
The sequence expands if it outgrows the selected width, so it never resets or creates a duplicate. You may rearrange or omit {shop}, {year}, and {yymmdd}, add a short prefix or separator, and keep the rendered ID within 32 characters. Changing the format affects new work orders only; existing IDs remain unchanged.
Team access
Give each person the minimum role needed for their responsibilities. Review access when duties change, remove access promptly when someone leaves, and avoid shared accounts.
Provider settings
Payment and communication connections should be managed from their owning setting and provider flow. Use the current state-specific action and confirm before disconnecting or removing a provider. See Integrations.
Account safety
Use unique credentials and protect authentication recovery methods. Never place passwords, API keys, bearer tokens, payment credentials, or provider security codes in customer notes, jobs, documentation feedback, or contact forms.
Operational review
Periodically review team access, provider readiness, shop identity, communication configuration, and scheduling settings. A setting is complete when the downstream workflow reflects the intended behavior, not only when a form reports that it was saved.
Plan and data review
Open Plan & usage to understand capacity, offers, and plan-change outcomes. Use Data handling for customer links, attachments, retention expectations, and safe support reports.
Find Help & support
Open your profile menu in the app sidebar and choose Help & support while signed in with a selected shop. Read the report guide before sending.