Vehicle Tracking

Operator
Operator OP

Operator console · Vehicle Tracking

Device registry & provisioning

Fusova-side: register each physical tag against a tenant and its middleware device id, sell GPS as a paid add-on, and flip the per-tenant live-tracking kill-switch that gates a tenant's ability to start "track my technician" jobs. Every register, add-on, and provision here is recorded to the append-only audit log under your operator identity.

Register a device

Bind a physical tag to a tenant + its middleware device id. provider_device_id is the device's id inside the tracking middleware — leave blank until the unit is enrolled there.

Provision GPS for a tenant

Per-tenant gps.live_tracking_enabled kill-switch. ON lets that tenant's owner start tracking jobs; OFF blocks new jobs (the owner sees a friendly "not turned on yet" message). This is the gate the owner's Start-a-job depends on.

Assign GPS add-on

Sell GPS tracking as a paid add-on on top of the client's existing plan. This adds the recurring charge in Stripe and unlocks the service; the tier sets a hard vehicle limit. After assigning, turn ON live tracking so the owner can start jobs. (Billing goes live only once the add-on prices are configured in Stripe.)

Security invariant: the browser never holds a Traccar/Flespi token. Only the Fusova worker & ingress (service-role) talk to the middleware; the customer link resolves a 256-bit share token server-side and returns exactly one vehicle.

Registry

LabelTenantProviderDevice idDriverStatus
Loading devices…

Sessions

TenantCustomerModeStatusDevice id StartedExpires
Loading sessions…