Agent Tracking

Track the mobile devices your team carries, without tracking your team. Agent tracking policies control when an Agent device has its own location recorded: during its work schedule, inside its work sites, and never anywhere else. Outside those times and places, the device's location is not stored at all. It is not hidden on the map. It is never recorded.

Policies do not affect tags. An off-schedule agent still relays every tag near it, so your assets stay tracked while the person carrying the device is not.

Availability

Agent Tracking appears under Tracking in the sidebar when your workspace has a linked network, on plans that include it. Your plan's features are listed on the Plan page under Settings.

How a policy works

A policy names the only times and places its agents are tracked:

A work schedule allows tracking during set hours, in the schedule's own timezone.
A tracking zone allows tracking inside a work site.
With both set, tracking is allowed during the schedule or inside a zone.
With neither set, the policy's agents are tracked at all times.

Everything outside the policy is off: the device reports its position, and the platform drops it before it reaches any store. Each policy states its own meaning in plain language on the Agent Tracking page, together with what it is doing right now.

Target agents by keyword

Each policy targets agents whose asset name or tags contain its keyword. Name your agents consistently ("Warehouse Phone 7") or tag them, and the policy applies itself: a matching agent picks the policy up when it is added, renamed, or retagged. When several keywords match, the longest wins. The Default policy covers every agent that no keyword policy matches.

Policies also select by device class:

Personal phones are the default class. Every agent is personal until something says otherwise.
Managed handhelds are company-owned devices. Zebra handhelds classify themselves automatically from their hardware model.
Fixed infrastructure is never affected by policies.

Work schedules

A schedule sets the hours tracking is allowed, per weekday, in local time: for example weekdays 08:00-18:00. Overnight shifts work as written, so 22:00-06:00 covers the evening and spills into the next morning. Split shifts are comma-separated ranges.

Tracking zones

A tracking zone is a work site where tracking is allowed. Create one by picking a zone from your Zones page: the tracking zone takes its name and boundary, and follows the zone when you edit it. If you delete the source zone, the tracking zone keeps its last boundary and keeps enforcing, so a deleted map zone can never silently turn full tracking back on.

Only with nearby tags

A policy can also record an agent's location only when the device has seen a tag recently. This keeps idle devices out of your data entirely. It only ever narrows a policy: a nearby tag outside the work schedule does not turn tracking on.