Skip to main content
You connect Samsara once at the MSP level, with an API token.

​
1. Create an API token in Samsara

1

Open API Tokens

Sign in to the Samsara dashboard as an admin, open Settings (the gear icon), and scroll to API Tokens. Click Add an API Token and name it “Neo”.
2

Choose tag access

Give the token access to every tag your technicians’ vehicles carry, or to all tags. Neo cannot see a vehicle outside the token’s tags.
3

Choose the scopes

For onsite time and vehicle tracking, give the token at least Read Vehicles and Read Vehicle Statistics (Vehicles), Read Trips (Trips), Read Drivers (Drivers), Read Assignments (Assignments), Read Addresses (Addresses) and Read Org Information (Setup & Administration). Add a write scope only for what you want agents to change, such as Write Addresses to add client sites. Neo also checks the permission groups you set per agent, so a scope alone never lets an agent change something.
4

Copy the token

Samsara shows the token once. Copy it.

​
2. Add the token in Neo

1

Open Integrations

Open Integrations → Samsara in the Neo Dashboard. The card is under Other.
2

Save the token

Pick your Region: United States if you sign in at cloud.samsara.com, Europe and UK if you sign in at cloud.eu.samsara.com, Canada if you sign in at cloud.ca.samsara.com. Paste the API Token and click Save. Neo checks the token with Samsara before it saves, so a wrong token or region is rejected straight away.

​
3. Turn Samsara on per agent

Open the agent from Agents, go to the Integrations section, and configure the Samsara block. Pick a profile, then change any group. For onsite time, Vehicles, Locations & Trips, Drivers & Assignments and Addresses, Routes & Dispatch at Read Only are enough; the time itself is written through your PSA tools.

​
Changes that always ask a technician

Whatever the profile: immobilizing, locking or unlocking a vehicle, setting an equipment or industrial output, deactivating a gateway, setting a driver’s duty status, creating or changing a live sharing link, every change to Samsara users, webhooks, Functions and their stored files, and data sharing, any change that sends a password, secret or token, and any change that records an approval decision in Samsara, such as approving an estimate, a purchase order or a form submission. See Samsara API for what each profile does.