> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Samsara API

> Read where your technicians' vehicles are and were, time on client sites, trips and drivers from Samsara in an agent

The common use is onsite time: when a technician's vehicle arrived at a client site and when it left, and who drove it, so an agent can log the time on the ticket.

<Info>
  Automatically enabled when you configure Samsara permissions in your agent workflow.
</Info>

## What it does

* Find a vehicle by name or registration, and read where it is now
* Read a vehicle's GPS trail for any time window. A point inside a Samsara address's geofence names that address, so the agent can find when the vehicle arrived at and left a client site's geofence
* Read which driver had a vehicle at a given time, from Samsara's driver-vehicle assignments
* Read trips, engine and fuel stats, speeding, idling and safety events
* Read and change drivers, addresses (client sites and their geofences), routes, messages to drivers, inspections, work orders and hours of service, as the permission groups allow. Safety Controls below lists what Neo refuses and what always asks

Neo removes webhook signing keys, driver auth tokens, driver sign-in QR links and presigned upload links from every answer. A vehicle's location is personal data about its driver: Neo's Samsara instructions tell the agent to write locations and trips only into internal notes, unless your agent's instructions say otherwise.

## Permission groups

| Group | Covers |
| - | - |
| Vehicles, Locations & Trips | Vehicles, equipment, trailers and assets, their locations, GPS and engine stats, trips, speeding, idling, fuel and gateways |
| Drivers & Assignments | Drivers, driver-vehicle and driver-trailer assignments, remote sign-out |
| Addresses, Routes & Dispatch | Addresses and geofences, places, routes, hubs and plans, live sharing links |
| Messages, Forms & Documents | Messages to drivers, documents, forms, issues, driver app workflows |
| Maintenance & Inspections | Inspections (DVIRs), defects, work orders, parts, preventive maintenance, warranties |
| Hours of Service & Compliance | Hours of service, ELD and compliance settings, IFTA, tachograph, qualification records |
| Safety, Coaching & Training | Safety events and scores, coaching, detections, training |
| Industrial, Sensors & Readings | Industrial assets, sensors, readings, ground intelligence |
| Setup & Administration | The organization, users, tags, attributes, alert contacts and configurations, webhooks, Functions, custom reports, data sharing |

Each group can be Disabled, Read Only or Read / Write.

| Profile | What it does |
| - | - |
| Read Only | Reads every group, changes nothing |
| Helpdesk | Reads every group. Changes to drivers, assignments, sites, routes and messages to drivers ask a technician first |
| IT Admin | Changes on its own, except compliance, safety and setup changes, which ask a technician first |
| Full Automation | Every change with no approval, except those Safety Controls lists |

## Safety Controls

These always ask a technician, whatever the profile:

* Immobilizing a vehicle's engine, locking or unlocking a vehicle, and setting an equipment or industrial output
* Deactivating a gateway, which stops the vehicle's tracking
* Setting a driver's hours-of-service duty status
* Creating or changing a live sharing link, which shows a vehicle's location to anyone with the link
* Every change to Samsara users, webhooks, Functions and their stored files, and data sharing with another organization
* Any change that sends a password, secret or token, such as a driver's app password
* Any change that records an approval decision in Samsara: approving, denying, rejecting or awarding an estimate, a purchase order, a warranty claim or a form submission, or asking for changes to one

Neo never creates or reads driver sign-in tokens or QR codes, and does not call Samsara's dashcam media endpoints. Revoking a driver's QR code is allowed. Neo hides every presigned upload link Samsara returns, so an agent cannot finish an upload that goes through one. A safety event can still carry links to its video, which the agent passes on as links.

## Setup

See [Connecting Samsara to Neo](/integrations/samsara/connecting-to-neo).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.