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 freeze is not implemented. Governed remote wipe is real, but it's its own separate, MFA-gated workflow, not one of the four quick commands above; see "Governed remote wipe" below.

Live Agent

Governed remote wipe

A device's detail page has its own Governed Wipe card, separate from the quick commands above, for when a device won't be coming back. It's deliberately not a full-disk erase: it signs the user out, clears saved browser logins and cookies, and deletes whatever folders your organization has configured as corporate data under Settings. Requesting one needs a fresh two-factor code at request time, not just an active session, and it sits on a cancelable delay (5 minutes to 24 hours, your choice) before it actually runs, so anyone with wipe access, not only whoever requested it, can stop it if the device turns up.

Android is different: on an Android device, this same button performs a full factory reset instead, personal data included, not just corporate folders. Android's remote-wipe capability has no selective, corporate-only tier the way Windows and macOS do. The wipe screen tells you which kind you're about to trigger before you confirm.

Live Agent

Android and iPhone support

RESEEKiT! is extending the Live Agent to company-owned phones, not just laptops and desktops. Status is different for each platform:

Android: not available yet. When it ships, it will enroll the same way as a laptop or desktop, from Devices or a device's own detail page, with Lock, Locate, Message, and Wipe. Its Locate will use real GPS when the phone grants location access, not just network-level information. Its Wipe works differently from Windows/macOS too: a full factory reset rather than a corporate-data-only wipe, see "Governed remote wipe" above.

iPhone: not supported yet. Apple does not allow any third-party app, RESEEKiT!'s Live Agent included, to lock or wipe an iPhone directly; that capability only exists through Apple's own MDM protocol. Even once supported, iPhone will remain different from every other platform in one specific way: there is no way for RESEEKiT!, or any MDM, to generate an unlock code for a locked iPhone. Apple reserves that capability for Mac only.

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.