Who Can Disarm This Car? Setting Lot Access for Sales, Service and Porters

Walk onto your lot, point at any unit and ask one question: who can disarm this car right now? If the honest answer is "anyone who knows the code" or "whoever knows where the switch is," access is the weakest layer you have.

Most theft prevention talk is about outsiders: relay devices, key programmers, jammers and tow trucks. But a lot also has dozens of people with a legitimate reason to move vehicles, and staff come and go. Every one of them is a key, and every key needs managing.

This guide treats access as a security control in its own right: who should be able to do what, how to stop secrets spreading, what to do the day someone leaves, and why the recorded trip matters.

The short version: give each person the access their role needs and nothing more, replace shared codes and hidden switches with personal access, remove access the day someone leaves, and let the recorded trip show what happened after every disarm.

1. Treat Access as a Layer, Not a Formality

Prevention is only as strong as its off switch. When it's armed, a Titan vehicle won't drive away, key or no key. That's the point: thieves now go after the key, so the strongest layer is one that doesn't trust it. But the same logic applies to the people who can disarm. If disarming is easy for anyone who has ever worked on the lot, the layer is weaker than it looks.

Access decisions are security decisions. Who can disarm, who can arm everything at close, who changes schedules and who gets the alerts all shape how well the lot is protected after hours. They deserve the same care as who holds the key box.

2. Map Every Role Before You Grant Anything

Start with jobs, not names. List the roles on your lot and what each one actually needs to do with a vehicle. A typical map looks something like this:

Sales: find a unit and disarm it for a test drive. Porters and lot staff: check lot health, move units and arm them at close. Service: handle the units that pass through the shop and the loaners that go out. Managers: arm or disarm everything on the lot, confirm schedules and receive alerts. Owners and admins: set the rules, the groups and who gets access.

Use the tool that fits the role. Titan splits the work across three apps. The Partner Service Dashboard is for owners, managers and admins, with role-based access for owners, managers and staff. Halo is the team app for lot, yard and sales teams, and Halo accounts are set up by Titan for each partner location. The Titan Secure app belongs to the driver once a vehicle is sold.

Grant the minimum. Titan gives each person the access their role needs. Resist granting everyone everything "to save time." The convenience lasts a week; the exposure lasts until someone notices.

3. Why Shared Codes and Hidden Switches Leak

A secret shared is a secret spread. A kill switch is a secret, and secrets get out. With shared vehicles, every driver has to know where the switch is, and the knowledge travels with every new hire, every departure and every conversation in the break room. A single shared code works the same way: you can't take it back from one person without changing it for everyone.

Personal access fixes both problems. With role-based access, each person gets the access their role needs, and nobody has to know a secret to do their job. Our comparison of Titan and kill switches covers the difference in more detail.

READ: Shared Keys, Open Sites: Why Construction Equipment Theft Needs Prevention

4. Offboard the Same Day

Access ends when the job ends. When someone leaves, removing their Titan access should sit on the same checklist as returning keys, door codes and email, and it should happen the same day, not at the next monthly review. Decide in advance who at your store requests or makes that change, so it never waits on someone being in the office.

Close the old shortcuts too. If a shared code, a spare fob in a desk or a hidden switch location ever circulated, assume it left with the person. Change what can be changed and recount the keys.

Think about phones. Halo includes a biometric app lock, which adds a step between a lost or borrowed phone and your lot. When a phone is replaced or lost, treat it as an access change, not just an IT ticket.

5. The Recorded Trip

Every disarm leads somewhere. In Halo, a porter checks lot health, finds the stock number on the map and disarms it for a test drive. The trip is recorded. Route history and speed alerts for test drives mean a demo that runs long or far is visible, not a rumor.

Records keep honest people honest. When access is personal rather than shared, the list of people who can disarm a unit is short and known, and the trip that follows is on record with route, stops and speed events. That protects the business, and it protects staff who did everything right.

A One-Page Access Map

Before the end of the month, put your access map on one page: every role, what it can do, who holds it today and who removes it when someone leaves. Then compare that page with reality. Anyone with access who isn't on the page is your first fix.

See how roles, Halo and the dashboard fit together, or book a live vehicle demo and see a disarm, a test drive and its recorded trip on a real vehicle.