Recording and allowed devices
Configure recording in the usability test Configure tab under Recording and tracking.
Recording options
Section titled “Recording options”| Option | Description |
|---|---|
| Screen recording | Captures participant screen during tasks (browser permission required) |
| Participant recording | Camera/microphone capture (permission required) |
Default study settings for new usability tests often enable screen recording at the API level when creating tests.
How recordings are stored
Section titled “How recordings are stored”- Browser uploads chunks to public recording endpoints during the session.
- On finalize, chunks merge into a file in R2 storage.
- Recording metadata links to the response row.
- Playback is available in the Responses tab in results.
Transcription
Section titled “Transcription”When study settings and owner AI/STT keys allow:
- Participant recordings may auto-queue transcription (AssemblyAI or OpenAI per deployment)
- Audio/video question answers can also be transcribed
- View transcripts in the Responses tab
Retry or check transcription status from the results UI when available.
Question timestamps
Section titled “Question timestamps”The runtime can POST question timestamps — mapping recording timeline to question IDs for synchronized playback in results.
Allowed devices
Section titled “Allowed devices”Restrict which device classes can start the test:
- Desktop
- Tablet
- Mobile
Participants on blocked devices see a message before the study starts. Match this to the prototypes you test (e.g. mobile-only Figma frames).
Privacy and consent
Section titled “Privacy and consent”- Add a legal/consent page before recording starts.
- Disclose what is recorded and how long data is retained.
- Comply with GDPR and local laws for video/audio collection.