Sessions
Sessions group recordings from a single device into logical units such as a drive, mission, or field test. Use sessions to organize data by context and visualize a set of recordings together.
How sessions work
Create a session in the app or via the API by specifying a device (or recordings from one device) and an optional key (a user-provided identifier unique within the Project). You can attach session custom properties to store metadata such as location, stack configuration, or mission type.
- From a device: Create a session for a device and optionally add recordings to it later.
- From recordings: Provide a list of recording IDs; the device and Project are inferred (all recordings must belong to the same device).
- On import: When importing recordings, you can set a session key; recordings with that key are grouped into the same session. If no session with that key exists, one is created automatically.
Sessions appear on the Sessions page, in device detail under the Sessions tab, and in recording tables. Opening a session in the visualizer loads all associated recordings for that session.
Session properties
Admins can define session properties (custom metadata fields) for the organization in Settings → Sessions. These properties are available when creating or editing a session and can be used to filter and organize sessions. Only keys that match your organization’s session property definitions are stored.
API
You can list, create, get, update, and delete sessions via the API. See the API reference.