Settings, Features & Integrations

Settings is the shop’s configuration workspace. Tabs are shown only when the signed-in person has the applicable access and the feature exists.

Business and document identity

Maintain shop name, address, contacts, locale, currency, timezone, branding, document terms, and related public identity. Setup Wizard writes through these same settings; it does not maintain a second copy.

Customer documents

Settings → Documents governs every printed or shared customer document — estimates, invoices, credit notes, receipts, statements of account, work orders and inspection reports — from one place, with a live preview that renders sample data through the same engine that produces the real PDFs.

• Branding — logo (any aspect ratio fits a fixed box), trade or legal name, contact lines, tax registration numbers (the business tax ID and/or the per-tax registrations entered under Financial → Taxes), accent colour, footer and paper size.
• Customer & vehicle — which identity details print: phone, email, address, VIN, plate, odometer in/out, fleet unit number. Odometer readings follow the shop's distance unit (General → Region & Currency).
• Pricing disclosure — choose a preset: Detailed (hours × rate, quantities × unit prices, part numbers, brands), Standard (descriptions, quantities and extended prices), or Simplified (job and package totals only). Advanced overrides adjust individual fields; part numbers are independent of brand, quantity and unit price. Subtotal, discount, tax and the total are always shown — presentation settings never change the figures.
• Authorization — status (pending, authorized, partially authorized, declined, deferred, reauthorization required), date and time, method, authorized amount, per-job decisions and the captured signature. Only recorded facts print; nothing is inferred.
• Payments — history, method, reference, store credit and the remaining balance. Invoices carry a payment state: Balance due, Partially paid, Paid, Credit balance, Refunded or Void, always derived from the payment ledger.
• Policies & terms — estimate validity, disclaimers, authorization language, payment / late-payment / storage / abandoned-vehicle / warranty policies and jurisdiction wording. Policy text is frozen onto every posted invoice; editing it later changes new documents only.
• Advanced — technician names (off by default), service advisor, promised/completed dates, declined and deferred work, customer PO, job notes. The internal work order copy has its own switches for prices and internal notes and is always marked not for customer distribution.

Pick Shop defaults or a specific document type at the top of the panel. A document type inherits every setting until you override it there; overridden fields show a pill and can be reverted individually. Saving needs the matching permission — branding, presentation or policies — and a stale form (someone else saved first) is refused until it is reloaded.

Canned jobs can be flagged Present as one package on customer documents so a service such as “Synthetic Oil Service $129.95” prints as one line when the pricing preset allows it; labour, parts and fees stay itemized internally for accounting, inventory and reporting.

Financial policy

Review the active tax profile/version, labor and pricing policy, fees, terms, and enabled business-office settings. Tax-profile acknowledgement in Setup is version-bound; changing the active version can change readiness.

Operations and scheduling

Maintain business hours, booking policy, capacity/bays, workflow requirements, and related operating choices. Appointment availability and configured Voice booking use the shop’s current policy; they do not guess around closed days or capacity.

Employees and Access Control

Use Employees for identity, invitation, role template, and active status. Use Access Control for effective permissions, overrides, scopes, and custom roles. Frontend visibility never grants backend authority.

Features & Modules

Enable only the workflows the shop uses. Turning a module off removes current navigation/actions/help leakage while preserving historical records. Enabling a module does not prove its provider or data source is Ready.

Messaging, Voice, payments, and external data

Connected workflows expose readiness rather than assuming success. Review configuration, verification, provider state, consent, limits, and fallback for:

• transactional messaging and campaigns;
• Voice/AI workflows and human transfer;
• card processing and payment links;
• tire catalog/application/fitment/supplier sources and quote policy;
• any other supported integration visible in the current product.

Do not assume a future ServiceFile integration, data migration, supplier connection, or import path because it appears in planning material. Only current configured integrations are supported.

Developer API

Settings → Developer issues API keys and webhook subscriptions so a website, fleet system, or accounting tool can work with this shop's data under scopes you choose — see Developer API.

Return to readiness

Open Setup & Readiness to see how current configuration projects into Required, Needs setup, Ready, or degraded outcomes. Readiness cannot be dismissed into success.