Staff customer and vehicle records
Authorized staff use Customers to search by name, phone, or email and open a customer 360 record. The record keeps profile and access controls separate from the customer’s plate-anchored vehicles. The actions shown depend on the staff member’s update, disable, and reactivate capabilities; seeing a customer does not by itself grant every action.
Use Vehicles for a paginated, plate-first view. Search the existing customer directory before creating a vehicle instead of loading or copying the full directory into the page. A vehicle 360 record keeps its identity available when owner or document details are temporarily unavailable. Vehicle editing, verification decisions, document reading, and document upload are separate capabilities. Document links are authorized by the server when opened and are never displayed as storage URLs.
Feedback submission is single-use. The response and token consumption are saved together, so retries or simultaneous submits cannot create a second response or leave a response behind with a reusable token. A retry after a completed submission receives the same safe already-submitted response.
Feedback links use the non-secret feedback request ID in the path. The private link capability is carried in the fragment, removed from the visible URL before loading feedback context, and sent to the API as an authorization credential. Do not copy a cleaned feedback page URL as a replacement for the original link. A temporary network or service failure keeps that capability only in memory in the current tab and offers a retry; an expired, consumed, or unauthorized link fails closed.