Configuring which detections are enabled

Turning capabilities on and off per fleet, and choosing sensible defaults.

Written for
Administrators
Reading time
1 min
Last reviewed
July 28, 2026

The capability set is configurable rather than fixed. Which detections are enabled, and what happens when one fires, is a decision made per fleet.

Where to start

  • Enable a small set of road-facing detections first. They are the least contentious with drivers and the easiest to validate.
  • Review a few weeks of events before adding cabin-facing detections, so you know what your own false-positive rate looks like.
  • Add driver-facing capabilities only once your policy and driver communication are actually in place.
  • Leave identity and biometric features off unless you have a specific, documented reason and the consent to match.

Related

Still stuck?

Technical documentation

API references, data model, webhook payloads and integration guides — the detail behind the workflows described here. Available to signed-in Naveera customers.

Open documentation

Ask your team

Support requests are raised from inside Naveera Console, where your organization and your role are already known — which means the answer can be about your configuration rather than the general case.

Settings → Support, or ask your organization’s administrator