Clientana terms, without the guesswork.
Use the product definition first. Engineering details are included only when they explain a visible behavior or ownership boundary.
Product and workspace
Record
The browser studio for asynchronous screen, camera, microphone, and supported system-audio capture.
Meet
The live meeting product for guest links, waiting-room admission, audio/video, screen sharing, captions, translation, chat, recording, and transcripts.
Workspace / tenant
The ownership boundary for members, plans, recordings, meetings, folders, domains, settings, and billing. The code and database often use the word tenant; the product uses workspace.
Active workspace
The workspace currently selected for authenticated API reads and writes.
Owner, admin, member
Workspace roles. Owners control the highest-impact tenant actions. Admins manage most workspace configuration. Members collaborate within the permissions allowed by policy.
Entitlement
A capability calculated from authentication and plan state, such as cloud recording, folders, share links, custom domains, viewer insights, or AI summaries.
Recording and media
Recording asset
The durable workspace row representing a screen recording, saved meeting, or upload. It owns metadata and points to media in object storage.
Local-first
The guest/free behavior where capture remains on the device and must be downloaded before the tab or meeting closes.
Direct upload
A resilient multipart flow where the browser uploads large file parts directly to R2 using short-lived signed URLs.
Derivative
A generated media file such as MP4, optimized WebM, HLS, thumbnail, waveform, duration metadata, clip, version, or export.
HLS
HTTP Live Streaming: segmented playback that adapts delivery and works well behind a caching gateway.
Version
An alternate state or media output for the same logical recording, allowing non-destructive editing and publishing workflows.
Meetings and speech
Room link
The public URL guests use to join or request admission.
Host link/token
The private authority that lets the host admit/deny guests and control owner-only room actions. It should not be published.
Waiting room
The state where a guest has requested access but the host has not yet admitted them.
WebRTC
The browser media technology used to send live audio, video, and screen tracks.
SFU
Selective Forwarding Unit. A media server such as LiveKit that receives participant tracks and forwards them efficiently, replacing a full peer-to-peer mesh at larger scale.
TURN
A relay service used when direct WebRTC connectivity fails because of network/NAT restrictions.
STT
Speech-to-text: converting spoken audio into timed caption text.
Caption capture interval
The period during which the meeting owner has captions enabled for durable transcript storage. Captions outside that interval are not automatically part of the saved transcript.
Translated captions
Caption text rendered in the participant’s selected language, separate from original speech recognition.
Sharing and delivery
Share ID
The public identifier used in a recording share URL. Rotating a share creates a new public capability.
Share-access cookie
An HTTP-only cookie set after a correct recording-share password so protected fields and playback can be returned.
Custom-domain purpose
record, meet, or all, controlling which public product surfaces a verified customer hostname may serve.
Playback gateway
An edge layer that verifies signed playback authorization before serving or caching R2 media.
Security and operations
RLS
Postgres Row-Level Security: database policies that decide which rows a role can read or change.
CSRF
Cross-Site Request Forgery protection. Clientana requires a session-linked token for authenticated state-changing browser requests.
Service role
A privileged Supabase server credential that can bypass normal browser access. It must never be exposed to client code.
Worker lease
A time-limited claim on a background job. If a worker disappears, stale-lease recovery can make the job retryable.
Release gate
An automated check that verifies a risky dependency or workflow—such as recording upload, SFU egress, R2 CORS, domains, STT/translation, or health—before release.
Exact-ref deployment
A deployment built from a specific pushed GitHub branch or commit rather than uncommitted local files.