Knowledge Base

Documentation for RESEEKiT!

Enrolling a device, using the Live Agent, and everything else you'd need to actually run this.

Getting Started

Setting up your organization

Create an account to get started. RESEEKiT! doesn't currently support single sign-on, so every user signs in directly with an email and password from Log In.

Core Workflow

Device inventory

Every device your organization tracks, company-owned or otherwise, lives in Devices, whether or not the Live Agent is installed on it. Add one from Devices → + Add Device with its make, model, serial number, and who it's assigned to. Inventory tracking works standalone; the Live Agent (below) is an optional layer on top of a device record, not a requirement for it.

Live Agent

Enrolling a device

The Live Agent is a lightweight client that keeps a device connected to RESEEKiT! for real-time commands.

From a device's detail page (or Settings → Enrollment Tokens), generate a token: set a Label, Device Type, how long it's valid for (Expires In), and how many times it can be used (Max Uses).
Install the Live Agent on the target device and provide the token when prompted.
The agent opens a persistent connection back to RESEEKiT!. Once connected, the device shows as Online on its detail page.

Note: an enrollment token only grants the agent an initial connection. It does not itself run any command on the device.

Live Agent

Using the Live Agent

Once a device is enrolled and online, its detail page exposes a small set of real-time commands:

Command	What it does
Locate	Requests the device's current location from the agent.
Lock	Locks the device remotely.
Message	Displays an on-screen message to whoever has the device.
Ping	Confirms the agent connection is alive and responsive.

Not available today: remote wipe and remote freeze are not implemented. Only Locate, Lock, Message, and Ping are real commands. Don't rely on RESEEKiT! for a governed remote-wipe workflow yet.

Core Workflow

Lost device workflow

Marking a device Lost from its detail page puts it into a dedicated recovery flow, surfacing the Locate/Lock/Message commands above front-and-center and logging every action taken while it's in that state to the device's history.

Core Workflow

Offboarding & recovery

When someone leaves and their device needs to be recovered, Offboarding → + New Offboarding tracks the process end-to-end: which devices are owed back, their return status, and a record of how each was recovered or resolved.

Reference

Audit log

Every device command, enrollment, and status change is recorded in Audit Log, a running, organization-wide history you can review independent of any single device's own page.

Support

Still stuck?

Use the chat bubble on this page for a quick question, or see the Support page for other ways to reach us.