Vehicle detail (overview)

Path: /dashboard/fleet-management/vehicles/:vehicleId (default tab)

Purpose

Inspect one vehicle: summary card, live map, optional geofence list, assigned drivers, registered device, and full specification view.

Prerequisites

• view_vehicle to load the layout.
• Section-specific permissions below.

Header and navigation

• Back returns to All vehicles (clears list search/pagination params in the link).
• Breadcrumb-style text shows All vehicles and the vehicle make + plate.

Tabs (visible in UI)

The product shows:

• Vehicle detail (this page).
• Vehicle history — see Vehicle history.

Other child routes exist in the router but are not linked in the header; they are not documented here as supported workflows.

Left panel sections

Vehicle info card

• Status, telemetry summary, expand/collapse for more fields, and control to open full specification on the right instead of the map.

Geofences

• Rendered only if you have view_vehicle_geofence.
• Lists geofences associated with the vehicle; clicking can highlight them on the map.
• Expand enters a full-height geofence mode; Back restores the normal layout.
• Managing geofences (assign, edit, remove) uses the dialogs in this section; creating assignments typically requires list_geofence and the appropriate create/update/delete vehicle-geofence permissions.

Assigned drivers

• Shown only with view_vehicle_driver_assignment.
• Lists driver assignments for this vehicle; supports expanded layout.
• Adding or changing assignments depends on create_vehicle_driver_assignment, update_vehicle_driver_assignment, delete_vehicle_driver_assignment, and list_user where the picker loads users.

Registered device

• Shows the device linked to the vehicle (if any) with expand/collapse behavior.
• Opens device-centric navigation where implemented (e.g., toward device detail).

Right panel: map vs specification

• Default: Vehicle map with optional geofence highlighting when a geofence is selected.
• When “full specification” is active: Vehicle specification details instead of the map.

Data sources

• Overview content uses Vehicles.detail (vehicle includes vehicleGeofences, device, and related fields).
• Driver assignments may come from driverAssignments on the detail response when present.

Troubleshooting

• Geofence or drivers missing: You lack view_vehicle_geofence or view_vehicle_driver_assignment; sections are omitted entirely.
• Map empty: No usable coordinates on the vehicle telemetry snapshot.
• Failed to load vehicle: Detail API error or invalid id; use back navigation and verify the vehicle still exists.