← User guide

Settings

Fleet settings

Configure how your fleet behaves - vehicle groups, driver IDs, input/output templates, driver scoring, driving-event alerts, vehicle checks and cameras.

The Fleet area of Settings is where you configure how your telematics works: how vehicles are organised, how drivers are identified, how driving is scored and alerted, what your walkaround checks look like, and how wired inputs and cameras are set up. You do most of this once, then adjust it as your fleet changes.

Permissions. These screens live under Settings > Fleet. Most need a permission in the FMS (Fleet Management) group, named on each section below. Administrator and Manager include them by default. You reach them at Settings, then the Fleet group in the left menu.


Vehicle groups

Who can do this: anyone with Vehicles View to see groups; Vehicles Manage to change them.

Groups organise your vehicles into a tree (for example by depot, region or customer) and drive three things: who can see which vehicles (visibility scoping), how reports are broken down, and who alert rules apply to. They live under Settings > Fleet > Vehicle Groups.

Because groups are the backbone of visibility scope, they have their own page: see Vehicle groups for how to create and nest groups, move a group to a different parent, and move vehicles between groups.


Driver IDs (tags and iButtons)

Who can do this: Devices Manage.

Driver IDs let a tracker automatically know who is driving, so journeys and scores are attributed to the right person without anyone logging in. You register each physical tag against a driver.

  • Type - BLE Tag (a Bluetooth key fob) or iButton (a small metal contact key a driver touches to a reader in the vehicle).
  • ID Value - the tag’s identifier (for example a Bluetooth address, or the iButton’s number).
  • Driver - the person the tag belongs to.
  • Label - an optional friendly name, such as “John’s fob”.
  • RSSI Threshold (BLE only) - the minimum signal strength that counts as “in the vehicle”. The default is -80 dBm. This controls how close the tag must be to count as in the vehicle; the default suits most setups, only change it if the system picks up a driver who is near the van but not inside.

When a device sees a tag it does not recognise, it appears in an Unrecognised Driver IDs panel at the top. From there you can Assign it to a driver or Dismiss it.


Input/output (I/O) templates

Who can do this: Io Templates.

This only applies to devices with wired inputs and outputs (ignition, panic button, immobiliser, sensors). Skip this section if you only have plug-in trackers. See Types of tracking device to tell if your tracker has wired inputs.

An I/O template is a reusable wiring setup you can apply to many vehicles at once, so you do not configure each one by hand. In a template you define what each input wire does - a DIN (a wired input on the device; DIN1 is commonly used for ignition, though the exact wiring depends on how the device was installed), the labels and severities, and up to 10 automation rules (“when this input changes, do that”).

Applying a template is always deliberate. When you save a template that is already used by vehicles, AutoM8 asks whether to save only (leave those vehicles as they are) or save and push the change to them. Editing a template never silently reconfigures vehicles.


Driver scoring

Who can do this: Driver Scores Configure.

This screen controls how driving is scored across your fleet. It is worth setting once to match your policy, then leaving alone. See Driver scoring and coaching for how the scores are used.

  • Event thresholds - the g-force, idling and speeding limits that decide when braking, acceleration, cornering, idling or speeding is logged, with separate medium, high and critical lines. Lower thresholds log more events.
  • Scoring weights - the share each of the five factors takes in the overall score. Weights must add up to 1.00; Reset to Defaults puts them back.
  • League table - choose whether names are hidden (Anonymise) and set the green and amber cut-offs for the rating colours.
  • Gamification - badges, streaks and kudos can each be switched on or off.
  • Coaching - the escalation timings (in hours), the event count that opens a coaching case, how long an unactioned case waits before it elapses, and who the default coaching manager is.

Tip: start with the defaults. Only change thresholds if you find the scores are catching too much or too little for your kind of driving.


Driving-event alerts

Who can do this: Driver Scores Configure.

Separate from scoring, these rules decide which driving events raise a live alert and who hears about it. You add one rule per event you care about.

Setting Options Notes
Event type Speeding, harsh braking/acceleration/cornering, excessive idle, seatbelt off, ignition on/off, device tampering, and more The event that triggers the alert.
Applies to Whole fleet, a vehicle group, or a single vehicle Scope the rule as widely or narrowly as you like.
Show live-map alert On / off Whether it pops up on the live map.
Notify Assigned driver, Fleet managers Who gets the notification.
Channels In-app, Push, Email How they get it.

Use narrow rules (a group or a single vehicle) for anything you only want to watch closely, and fleet-wide rules for the events that always matter.


Vehicle checks and walkaround behaviour Manage plan required

Who can do this: Administrator or Manager.

Two screens control the daily walkaround. See Daily walkaround checks for how drivers use them.

Check Templates is where you build the check itself - sections and items, each item with a default severity (Minor, Major or Dangerous), whether a photo is required, whether it is mandatory, and where on the vehicle it applies. A template has a type (Daily Walkaround, Weekly Check, Pre-Journey or Custom), a frequency, and the vehicle types it applies to.

Walkaround Settings controls what happens when a defect is found:

  • Dangerous defect behaviour - Hard block takes the vehicle off the road immediately (the driver cannot start a journey), or Soft warning alerts a manager but leaves the vehicle usable until someone grounds it by hand.
  • SLA thresholds - the maximum time to fix a Dangerous, Major or Minor defect before it breaches (in hours).

Cameras

Who can do this: Vehicles View. Camera hardware must be fitted.

Under Settings > Cameras you see each camera system and open one to configure it. On a camera’s Settings tab you set, per channel: the name, the resolution (1080p, 720p, 480p or 360p), and whether audio, AI and the channel itself are enabled. The device’s own settings (recording, network, alarms) are also here for supported models. The first (built-in) channel is always on. See Cameras and video.

If your cameras are on a fixed-term contract, the paid channel selection is locked for the term - contact your account team to change it.