Tenant Admin Onboarding

Role focus

Tenant Admins configure how a workshop or service-center network uses Motornauts.

What you need

Collect the tenant name, support details, logo, brand colors, branch list, staff list, service catalog, module decisions, and readiness owners. Decide who owns customer registration, payments, notifications, inventory, fleet, and custom domain setup.

Find your work areas in the grouped, labeled sidebar. On a smaller screen, open the header navigation menu; it contains the same permitted destinations. Check the tenant and branch scope before starting work, and use the breadcrumbs to return from a detail page. Account contains appearance controls and Log out. Daily workshop destinations appear before Management and Administration; unavailable role destinations are omitted.

Sign in to the tenant staff workspace. From Today’s work, open Administration → Settings to begin setup. Review Branding, Branches, Staff, Services, Modules, customer-facing settings, document templates, notification readiness, and custom domain readiness.

For operational review, choose a branch and queue in Today’s work, search a plate/reference, and use its task link. Read the manual update time before a handoff. Confirm the stable vehicle/customer/status header before using the task tabs. Safely unavailable secondary tabs are not proof that the underlying business records are empty.

Open Customers and Vehicles once to confirm the 360 workspaces reflect your tenant. Search for an existing customer before adding a vehicle, verify the plate and current owner, and confirm that profile, access, verification, and document controls follow the permissions you assigned.

First steps

Confirm tenant branding and support contact details.
Add or review active branches.
Invite or provision staff with the narrowest useful role.
Configure service packages customers and staff can select.
Review module readiness before telling staff a feature is live.
Assign fallback owners for Cashier and Quality Controller if those roles are disabled.
Configure customer self-registration only when a review owner is ready.
Check PayHere/online-payment, PDF, domain, inventory, fleet, and media readiness before exposure.
Share the correct customer portal or tenant URL with staff.

For customer registration, enable the tenant module first, select an active default branch, review the public terms copy, and then separately choose whether to accept public requests. If a save cannot complete, public intake remains closed. Review applicants in the registration queue; changing settings never grants customer access by itself.

Open the public registration URL in both Stone and Carbon before sharing it. Confirm the tenant name, logo, support contact, public terms, catalogue-backed vehicle fields, and staff-review explanation. Accepting requests describes your tenant’s intake setting. The public form also needs working bot verification. If it says Verification is temporarily unavailable, ask Motornauts support to check the site’s verification setup; switching intake off and on does not repair that setup. Do not ask a customer to bypass verification or send applicant details through an internal support ticket. After setup is corrected, reload the public registration page before trying again.

When inviting or updating staff, choose one role and then select every branch where that role applies. Multiple branches are supported; simultaneous roles for the same tenant staff member are not. Tenant Admin always covers every branch in the tenant, even when no individual branches are selected.

Typical workflow

Tenant Admin work is setup and governance. Most daily service work belongs to Branch Manager, Service Advisor, Technician, Cashier, Quality Controller, Inventory Manager, or fleet users.

When to ask for help

Send branch workload issues to Branch Manager. Send intake and customer communication issues to Service Advisor. Send provider setup or readiness gaps to Motornauts support. Send inventory setup questions to Inventory Manager when that module is active.

Safe use

Do treat disabled and setup-incomplete states as real product states. Do not paste credentials, provider payloads, private links, or raw callbacks into public notes or support messages.

Example

Prepare a tenant for payment requests: check PayHere/online-payment readiness, PDF readiness, Cashier fallback, Service Advisor permissions, and the customer-safe payment state wording. Verify that assigned-branch staff see only their branch choices in Standalone requests, and make the approved customer channel clear because renewing an access link does not deliver it automatically. Follow Set up online payments. Check the intended Test/Live configuration, explicitly enable checkout, and verify an authorized payment result. Review reminders remain separate from runtime setup and payment integrity.