> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tekma.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up recording on a verified website

> Verify a website origin, install the Tekma recorder handoff, and let eligible guests record with consent on that site.

Connected site recording lets a guest use a recording link while they are on a website that your workspace owns. A workspace owner must complete both ownership verification and recorder installation verification. Ownership by itself does not enable the connected flow; a hosted browser flow remains available when either check is incomplete.

## Verify ownership

1. Open **Settings → Recording domains** as a workspace owner.
2. Enter the public **Website origin**, such as `https://support.example.com`, then choose **Add domain**. Use HTTPS without a path. Register each subdomain separately; Tekma supports up to 20 origins.
3. Open **Ownership setup** and publish the plain-text challenge at the exact `/.well-known/tekma/<domain-id>.txt` URL shown by Tekma. Return HTTP 200 without a redirect and include only the displayed challenge text.
4. Choose **Verify ownership** and wait for **Ownership verified**.

If verification fails, check the exact scheme and hostname, the path, redirects, caching and whether the deployed server returns the challenge as plain text. A staging hostname is a separate origin and must be added separately.

## Install and verify the recorder

After ownership is verified, open **Recorder installation** for that domain and choose **Copy generated snippet**. Add the snippet to the owned website using the origin and identifiers Tekma supplied; do not substitute identifiers from another domain. The generated code loads the Tekma recorder SDK and calls `TekmaRecorder.install(...)` for the verified workspace/domain.

Return to the domain settings, choose **Check installation**, and allow the site popup or opener check when the browser asks. Tekma marks the domain **Installation checked** only after the recorder is detectable from the verified origin. Deploy the snippet before checking; a check on a different host, in a blocked iframe, or before the new asset is live cannot prove installation.

Both **Ownership verified** and **Installation checked** are required before a recording request can offer connected site recording.

## Use it in a recording request

When a recording link's required **Website to record** matches an active, fully verified domain in the same workspace, the guest can choose **Record on the website**. The original recording-link tab must stay open while the site popup connects.

The guest accepts **I agree to record this tab and page diagnostics**, optionally enables **Include microphone**, and can hide an element before choosing **Start recording**. Chrome or Edge then asks them to choose the current tab. The guest can **Pause**, **Resume** and **Stop**, review the local result and choose **Send recording**. They can discard it or choose **Record again** before sending. Connected capture protects the Tekma control strip and requires a supported protected browser tab; unsupported sources or a closed opener fall back to the hosted flow or show a recovery error.

The guest's consent and browser source selection determine what is captured. The owner receives the submitted capture in the configured workspace and folder; installing the recorder does not grant the guest workspace access.

Presets for title, folder, reference and metadata are resolved by Tekma. A guest cannot use query parameters to grant access or move a submission outside the configured workspace. If the opener was closed or navigated, reconnect or use the hosted flow.