Tenant Manual

1. The Tenant Portal

Your organisation has its own operational portal at {your-slug}.track-any-device.com. This portal is where your team manages day-to-day fleet operations. Access it by signing in via the link your administrator provided, or from your My portal under Organizations.

The portal contains:

• Dashboard — summary of active devices, open incidents, and personnel
• Live Map — real-time positions of all active devices
• Devices — full device list with status, battery, and last signal
• Incidents — active and historical alerts
• Beats — patrol zones and restricted areas
• Assignees — field personnel who carry or are associated with devices

2. Assignees

An Assignee is a field operative, vehicle, or asset that can be assigned a tracking device. Assignees are the people and things your fleet monitors.

Creating an assignee

Assignees are managed from the admin panel by your organisation's administrator. Each assignee has a name, type (person, vehicle, asset), and contact information. Once created, a device can be assigned to them.

Device assignments

A device assignment links one device to one assignee for a period of time. When a device is assigned, its signals (location, battery, incidents) are attributed to that assignee. Assignments can be transferred or returned at any time from the admin panel.

3. Beats — Patrol Zones

A Beat is a geographic zone applied to devices. There are two types:

• Inclusion Zone — the device must stay inside. An incident is raised if the device exits the zone.
• Exclusion Zone — the device must stay outside. An incident is raised if the device enters the zone.

Zones can be polygon (free-draw), hexagon, or circle shaped. Beats support a parent–child hierarchy: a beat can have sub-beats, and violations escalate through the chain as the device moves further from its assigned area.

Assigning a device to a beat

From the admin panel: open the device record → Beat Assignments → Assign to beat. Only active beats are selectable. A device can be assigned to one beat at a time.

4. Live Map

The Live Map updates in real time as devices send location signals. Each device marker shows:

• Device name and current status
• Battery percentage
• Last update timestamp
• Assigned beat zone outline (if active)

Click any marker to open the device detail panel. The map supports OpenStreetMap tiles and can be configured to use offline tile caches for areas with limited connectivity.

5. Incidents

Incidents are raised automatically when a device breaches a monitored condition. Your team must review, acknowledge, and resolve incidents to keep the incident queue clean.

Incident lifecycle

1. Open — raised automatically; requires operator action
2. Acknowledged — operator has reviewed it; monitoring continues
3. Escalated — severity promoted; additional notifications triggered
4. Resolved — operator closes with optional resolution notes

Incident levels

For Inclusion Zone violations, incidents escalate by level as the device moves further outside its zone — Level 1 is just outside the assigned beat, Level 2 is outside the parent beat, and so on. Higher levels trigger more urgent notifications.

Managing incidents

From the Incidents view: filter by status, device, or date. Click an incident to see its detail — location, device, assignee, beat, timestamps, and history. Use the action buttons to acknowledge, escalate, or resolve. Resolution notes are stored permanently on the record.

6. Workflows

Workflows automate responses to incidents and time-based triggers without manual intervention.

Trigger types

• Incident opened — fires when a new incident is created
• Incident escalated — fires when an incident level increases
• Time schedule — fires on a cron schedule (e.g. every 15 minutes)

Actions

• Notify — send an in-platform notification to users or assignees
• Escalate incident — automatically promote the incident status
• Send command — send a command to the device (e.g. request location update)
• Webhook — POST incident data to an external URL
• Wait — pause the workflow for a set number of seconds before the next action

7. Reports and History

Historical signal data, incident logs, and assignment records are accessible from the admin panel. Signal history is retained for the configured retention period (default: 90 days in InfluxDB).