01 / Start here

Sign in

Enter your email and password. If multi-factor authentication is enabled, expand that section and enter either your current one-time code or a recovery code. If your account belongs to more than one workspace, choose one after signing in.

02 / Recommended setup order

Create dependencies before monitoring begins

1. 1
   Create a subject

   Add the person, vehicle, asset, or team that will be monitored.

2. 2
   Create locations

   Enter latitude, longitude, and the permitted geofence radius in metres.

3. 3
   Create and publish an SOP

   Create the SOP, add its monitoring rules from Manage, then publish the reviewed version from the dashboard.

4. 4
   Open a monitoring case

   Select the subject and a published SOP, then confirm its start time and timezone.

5. 5
   Add target locations

   Open the case workspace and bind each reusable location using the role referenced by its SOP rules.

6. 6
   Issue device enrollment

   Enroll the device from the case workspace and copy the one-time token immediately.

03 / Manage records

Use directories to find work and workspaces to complete it

Filter large directories by status, use the resource-specific reference lookup, and load additional cursor pages when needed. Open a subject or case to keep its related records and actions together.

Subjects

See every linked case, location, and device, or open a new case. Review consent, legal holds and data exports, or request erasure.

Cases

Add, edit, or remove target locations; enroll devices; and run lifecycle actions.

Locations

Edit geofence details or archive a location.

Devices

Review enrollment state or revoke a device.

SOPs

Edit metadata and add a validated rules version.

Integrations

Change access status, issue scoped API credentials, and rotate or revoke the ones already out.

Webhooks

Edit, disable, enable, rotate the secret, or delete.

Team

See who holds access and revoke a membership.

Invitations

Invite someone to a role, chase the pending ones, or revoke an invitation before it is used.

Roles

Create and edit what a role may do. A role cannot grant more than you hold yourself.

Privacy policies

How long data is kept and how it is erased. The workspace default governs everything a SOP policy does not. Draft a version, compare it with the ones before it, and publish: publishing retires the version it replaces, and cases already running keep their terms until you move them from the case workspace.

Legal holds

Place a hold from the subject, case or integration it covers; review and release holds here. A hold blocks erasure and retention deletion until the last matter releases.

Erasures

Approve or reject a requested erasure. Someone other than the requester must decide, and an approved erasure cannot be undone.

Retention

What retention removed from this workspace, and under which rule. From a subject, Retention shows when each month of its pings becomes removable: a hold must be placed before then to keep them.

Destructive and irreversible actions ask for confirmation before the change is applied.

04 / Tokens and secrets

Copy one-time values before closing

Enrollment tokens, invitation tokens, API credentials, and rotated webhook secrets are displayed only once. Use the Copy button and transfer the value through an approved secure channel.

A subject's data export downloads a limited number of times and expires, after which it is destroyed. Treat a downloaded export as carefully as the subject's own records.

Send an invitation token to its recipient with a link ending #invite/<token>, or tell them to choose I have an invitation to accept on the sign-in screen. Rotating a credential leaves the current one working for a grace window, so a caller can move across without a coordinated cutover.

05 / API tools

Use Reference to discover and Request Lab to execute

API Reference lists every documented operation and its authentication requirements. Select an operation to load it into Request Lab, review the path and JSON body, then send it with your current workspace session.

Keep the idempotency option enabled for write requests. It prevents accidental duplicate work when the same request is retried.

06 / Manual smoke test

Confirm the workspace is ready

• Overview reports the API as Operational and dependencies as Ready.
• Each resource page loads without an authorization or workspace error.
• Create a test subject and confirm it appears in the table.
• Open Manage, edit the display name, and confirm the refreshed value.
• Open API Reference, select a GET operation, and run it in Request Lab.
• Sign out and confirm protected resources are no longer accessible.