Skip to main content
A recording link invites someone to submit a capture to your workspace. It is different from a share link, which lets someone view an existing capture.

​
Create and send a request

Open Recording links in Tekma and create a link for the reproduction you need. Set the available limits and expiry, then copy the link to the person reporting the issue. Explain the task alongside the link. For example: “Please record the steps from opening checkout to seeing the delivery error. Use a test address and stop once the message appears.”

​
What the recipient does

The recipient opens the link, reviews the recording request and consent information, and follows the page’s recording instructions. They grant the browser permissions needed for the selected capture source, reproduce the issue, and submit the recording. The page has Prepare, Record, and Review & send stages:
  1. Select Include microphone or Include shared audio if needed. Shared audio depends on the browser’s picker.
  2. Review and accept I agree to record and share my selected screen.
  3. Select Choose screen and record, then choose the intended tab or screen in the browser picker. A three-second countdown follows approval.
  4. Reproduce the problem, pause if needed, then stop.
  5. Preview the result and send it. You can download the recording or choose Record again before sending.
The recording stays on the sender’s device until they send it. If an upload fails, preserve the local recording and retry rather than immediately starting over. They do not need to become a workspace member to use the recording-link submission flow. Browser permission prompts still apply.

​
Find the submitted capture

Submitted recordings arrive in the destination workspace. Open the resulting capture, review the footage, and follow up using your normal reporting workflow. Creating a request link does not itself create a completed recording.

​
Manage the request

Revoke a request when it is no longer needed. Expired, revoked, or exhausted links cannot accept another submission. If the person cannot submit, check the request’s status and workspace policy before sending a replacement. For automation, the CLI also supports an authorized recording-link token. Keep that token private to the intended workflow.