Vehicle ownership and garage access
Add or update your vehicle
In Garage, choose Add vehicle. Select the make, vehicle type, fuel type, transmission and ownership type; these start empty so you can choose the correct details. Enter the registration, model, year and Odometer reading (km). Expand Additional vehicle details (optional) for a nickname, chassis number or engine number.
A failed save keeps your entries so you can correct the highlighted field and try again. Verification needed means the workshop must check the vehicle details. Vehicles that do not need verification have no extra badge beside their plate.
Choose a vehicle to review its details, documents and history. Expand Edit vehicle details when you want to make a change; closing and reopening it keeps unsaved entries while the page stays open. Identity changes may require verification again. Every history card has View visit details; delivered visits can also offer Give feedback when the workshop’s request is available. In Profile, the sign-in email is shown for reference and cannot be edited there.
Ownership changes
Authorized workshop staff can correct Vehicle type, Fuel, and Transmission in Vehicles → Vehicle details, alongside registration, make, model, year and mileage. Choose Save vehicle to apply the correction. Changing these facts does not transfer ownership; use the separate ownership action below when the owner changes.
Every live vehicle has one active owner: either an individual customer account or a fleet account. Motornauts uses the dated ownership record as the source of truth, so a vehicle is not treated as simultaneously owned by a customer and a fleet.
Adding a vehicle through a customer’s garage creates the initial customer ownership record. When authorized staff later transfer the vehicle to another customer or link it to an active fleet, the previous ownership period closes and the new ownership begins as one operation. The previous customer then loses current garage access to the vehicle. A fleet-owned vehicle is shown as fleet owned in staff views and is not linked to an unrelated or former customer profile.
In the staff Vehicle 360 workspace, choose the receiving customer or fleet by its human-readable
name and confirm the action with TRANSFER; do not paste an identifier from another page. A
customer-to-customer transfer requires vehicle-update access. Any transfer into or out of a fleet
also requires Fleet Vehicle assignment access and Fleet readiness. Motornauts rechecks the active
owner, target, active workshop work, and audit requirements before committing the change.
A transfer changes current ownership; it does not rewrite completed business records. Existing appointments, repair orders, estimates, invoices, payments, feedback, and other workflow records retain the customer context captured when that work was created. The new owner does not automatically inherit a previous owner’s private documents, estimates, invoices, payments, feedback, media, notes, or other private workflow details.
For fleet-owned vehicles, authorized workshop staff may retain a selected customer/contact as an immutable appointment or repair-order snapshot. That snapshot supports workshop communication and record continuity only; it does not make the customer the current vehicle owner and does not grant customer-portal access.
If a vehicle disappears from a customer’s garage after a legitimate transfer, that is expected access revocation rather than data deletion. Contact the workshop if the active owner is incorrect; staff should verify the vehicle and owner before making another transfer.
Public registration requires a successful action-bound Turnstile check and an empty hidden honeypot. Each form carries a one-use idempotency key. Motornauts returns the original receipt for an exact retry, blocks another pending request with the same email, phone, or vehicle registration, and pauses new intake when a tenant reaches 500 pending requests. Bot tokens and raw idempotency values are not stored in customer or audit records.