cloudGPS provides role-based access for your corporate fleet. Each sub-user only sees their assigned vehicles and geofences, performs only the allowed actions, and nothing else. The audit log records who changed what and when. Reports can be delegated — without handing out your credentials.
In a typical fleet the monitoring system login circulates in a group chat — dispatchers, accounting, the manager, sometimes drivers. Someone deletes a vehicle, someone leaves for a competitor — and there's no way to tell who. cloudGPS solves this with per-user sub-accounts, restrictions, and an audit log.
Dispatcher, accountant, technician, manager — each with a sensible default permission set. They can be cloned and adjusted to fit your policy: a single role for the whole dispatch team.
A sub-user only sees the vehicles assigned to them. The rest of the fleet does not exist for them. Useful when a fleet is split across branches or contractors.
You can scope the console to a map — for example, only the city or region the user is responsible for. Data outside the geofence isn't shown, even if a vehicle crosses into that area.
Every login, settings change, object deletion, or command sent is recorded with IP, time, and user. Reconstructing who changed what is a couple of clicks away.
Configure automated reports to accounting, the CEO, or the customer — without giving them console access. Template, frequency, and file format stay under your control.
Two-factor authentication for admins, mandatory password rotation every N days, no password reuse. The minimum any serious fleet's security team will expect.
Any fleet of 20+ vehicles with a team of more than three people already needs access separation.
Multiple dispatchers per shift, each managing their own group of vehicles. One shouldn't see another's, but the shift lead needs to see all of them.
They need mileage, fuel, and maintenance data for the books. Full access to the map and driver commands is unnecessary.
A CEO or an external customer (for example, the tenant of your fleet) wants the big picture without intervening in operations.
A sub-user is created in 30 seconds. Permissions and scopes are flexible, but presented behind clear templates for the administrator.
From the built-in list: dispatcher, accountant, technician, manager, read-only. Each role is a set of action permissions (map view, command sending, report access, vehicle editing).
Pick the specific vehicles, groups, or geofences the sub-user can work with. Everything else does not exist for them — not even in search.
Email and a one-time password for the first sign-in. The sub-user sets their own password and — optionally — enables 2FA via an authenticator app.
The sub-user sees only what's allowed in their console. The admin gets a full audit log with filters by user, vehicle, event type, and time.
Most competitors offer at most "admin" and "operator" without object-level restrictions. cloudGPS provides a full role model with geofence-level scopes.
| Feature | cloudGPS | Single shared login | Basic "admin/operator" |
|---|---|---|---|
| Per-employee login | Yes | No | Yes |
| Built-in roles (dispatcher, accountant, technician) | Yes | No | Often only 2 roles |
| Access restrictions to specific vehicles | Yes | Sees everything | Often no |
| Geofence restrictions | Yes | None | None |
| Audit log with filters | Yes | Author unknown | Basic log |
| Delegated reports by email without login | Yes | No | Rare |
| 2FA and password policies | Yes | One password for everyone | Not always |
| API with sub-user scoped token | Yes | No | No |
Everything that comes up around security and team-access organization.
We'll show how to configure roles, access scopes, and the audit log for your fleet.
We respond within 24 business hours.