Setup areas
Start from Settings and choose the outcome group that matches the work. Organization contains identity, locations, services, and staff access; Customer experience contains registration and domain entry points; Communications contains messaging controls; Documents and billing contains templates and online payments; Advanced operations contains safety-gated modules. Counts are shown only from a complete authorized response, while individual module failures stay local to their cards.
- Branding: tenant name, support details, logo assets, colors, and document presentation.
- Branches and staff: branch records, invitations, role changes, and disabling staff.
- Services: service packages, pricing, and catalog records.
- Modules: feature toggles, dependencies, readiness states, disabled states, and provider setup.
- Customer-facing setup: registration settings, custom domains, PDF templates, email templates, PayHere/online-payment, and inspection video readiness.
- Registration review: inspect the protected all-branch applicant queue separately from module setup, confirm the plate, identity, vehicle, consent, and Pending state, then use the guarded approve or reject decision only when the review permission is granted.
- Compliance coordination: tenant-controlled privacy requests, fulfillment evidence, safe export
coordination, retention plans, retention safety checks, tenant approval evidence, and
correction/restriction/erasure decision notes without secrets or private provider details.
Tenant Admins should preserve manual/unsupported blockers; only target/action pairs with an
approved backend handler can complete, and final mutation plus audit evidence is atomic.
Destructive or restricted actions may require Motornauts support review before completion. Formal
refusals should be recorded as refusal fulfillments with reason and appeal placeholders.
Use only the returned coordination statuses and the implemented
request/eventsexport categories. If a response or access check is unavailable, no partial evidence is shown; refresh without copying opaque URL values or backend diagnostics into support notes.
In Brand and support, review the Stone and Carbon customer-signal previews before saving. Enter colors as six-digit hex values; Motornauts derives separate contrast-safe mode pairs and may adjust or replace an unsafe seed. Supporting color is an identity input, not a second unrestricted theme. Upload only PNG, JPEG, or WebP logos, use the 2:1 crop, and wait for verification before treating the asset as current. If logo tools fail while the brand form remains visible, retry only that section; do not infer that existing assets were removed.
In Custom domains, enter a bare customer-facing hostname and publish the exact TXT host/value
shown by Motornauts. Check DNS only after the record is available. A verified record still does not
route traffic until you type its canonical hostname and ACTIVATE; disabling requires the hostname
and DISABLE. Tenant-slug routing remains available. Do not share provider responses, internal
readiness evidence, backend messages, request IDs, or opaque identifiers when asking for help.
In Email templates and delivery, choose the message from the service or identity catalog. Review whether it is required, enabled, using a safe default, saved as a draft, or published before editing. Keep content structured: use only the displayed variables and system link choices, then review the desktop, mobile, and plain-text preview. Preview sends no email. Save a draft before publishing the version used for future sends. Required identity messages stay enabled, and a missing delivery producer is not fixed by changing template text. Do not paste credentials, one-time values, private links, provider diagnostics, backend messages, or request IDs into a template or support note.
In Document templates, choose Invoice, Estimate, Inspection report, or Service history from the catalog rather than editing the address. Review the synthetic sample, print labels, supported block order, columns, safe variables, and available tenant mark. Save a draft first; publishing creates an immutable official version for future server-rendered documents. It does not generate or download a live customer PDF. Manage logo uploads in Brand and support, and never copy signed logo links, processing evidence, private artifacts, backend messages, or request IDs into support notes.
In Online payments, use the intended Test or Live card. Follow the setup guide for credential checks and explicit checkout activation. Credentials remain write-only; changing them turns checkout off for the new setup.
In Inspection videos, save the upload preference, maximum size and allowed file types. No self-approval or evidence notes are required for these settings. Uploads remain unavailable because video safety processing is not implemented in the current application. Saving a preference does not supply that processing or make a file customer-visible. Use photos or documents meanwhile. Refresh before retrying a stale settings form; existing review history remains unchanged.
In Branches, keep the timezone, opening periods, booking interval, capacity, address and contacts accurate. Add a separate period for each part of a split day; use Closes at midnight when needed. Days without periods are closed. Missing or unsupported hours pause online booking, while walk-ins remain available. Other edits preserve unsupported saved settings until you choose to replace them. In Services, confirm the price, currency, duration, vehicle types, every checklist item and branch availability. Prices with too many decimal places are rejected. Failed saves keep your draft and highlight fields needing correction. If another person has changed the record, compare your draft with the latest version before reloading and reapplying it. See Tenant Administration.
In People and access, review the verified staff and invitation counts before changing access.
Choose one role for each tenant membership, select only the locations the person needs, and mark a
selected branch as primary. Staff profile names and phone numbers are tenant-local; email remains
managed by the sign-in identity service. Type REVOKE before revoking an invitation and DISABLE
before disabling an active member. Do not copy invitation links, identity-provider identifiers,
failure classifications, opaque route values, or backend diagnostics into operational notes.
Tenant Admins should treat feature toggles as operational controls. Enabling a module is not enough if provider setup, tenant setup, or readiness is incomplete.