Module · Video

Video settings

Where: ExpertPress admin app → Modules → Video (Відео). The same screen is also under ExpertPress → Video in the WordPress admin menu (page title "Video (LiveKit)").

What this screen is for

Provider keys for video calls (LiveKit) and intro videos (Bunny Stream), limits for intro video uploads, and optional call transcription. The screen also shows a read-only panel about pending video deletions at Bunny Stream.

How sessions are delivered (meeting link or call on this site), when the call opens and closes, end-of-session warnings and screen sharing are core options under ExpertPress → Settings → Video calls. They are not repeated here.

Who can open it

  • People with expertpress_operate (for example ExpertPress Manager) can open the screen and change the non-secret fields.
  • Keys and secrets (LiveKit API secret, Bunny API key, token key and Read-Only API key, the transcription agent secret) can be entered, changed or cleared only by a WordPress administrator (manage_options). Other users see "Only a site administrator (manage_options) may change …" in place of those fields. These fields are marked Admin only below.

See Roles and access.

Saving and secrets

All blocks on the screen are saved together with Save video settings (Зберегти налаштування відео). Each block (LiveKit, Bunny Stream, transcription) is saved on its own: if one block is refused, the others can still be saved and the message lists what failed. On full success the message is "Video settings saved."

Secrets are encrypted before they are stored and are never shown back in the form. A secret field left empty keeps the current value. A status line shows whether a secret is set (for LiveKit and the agent secret, with its last four characters). A newly generated agent secret is shown once, right after saving, with "copy now; it will not be shown again." If a secret cannot be encrypted, nothing in that block is saved ("… could not be stored securely. Nothing was saved.").

Provider status lines

  • LiveKit: "Provider status: ready." or "Provider status: not ready (URL, API key and secret required). Leave inactive until keys exist."
  • Bunny Stream: "Intro video: ready." or "Intro video: not ready (library, API key, token key and CDN hostname required)."
  • If the Read-Only API key is missing, a warning says Bunny webhooks are refused until it is saved; uploads and playback still work.
  • The Bunny block also shows how many intro video deletions need manual review and how many are held to preserve evidence.

LiveKit

LiveKit carries the audio and video of on-site calls. Needs an external account (LiveKit Cloud or a self-hosted LiveKit server). Without all three values below, on-site calls cannot be enabled and the site keeps using meeting links.

While a one-to-one session that was already admitted to an on-site call is upcoming or in progress (or ended less than 12 hours ago), the LiveKit block cannot be changed: the save keeps the old values with "Settings were not saved." Change LiveKit settings when no such sessions are in progress.

LiveKit server URL

  • Where: Video → LiveKit
  • What it does: The address of your LiveKit server, for example https://your-project.livekit.cloud. The site calls it to create and end rooms; browsers connect to the same host over a secure WebSocket.
  • Default: empty.
  • Values / limits: a URL. An address without a scheme gets https://; wss:// and ws:// are accepted and stored as https:// and http://. An address without a host is cleared.
  • When to change it: when you first set up calls; when you move from LiveKit Cloud to your own server or to another project.
  • Related: Video calls (Delivery mode)

API key

  • Where: Video → LiveKit
  • What it does: The LiveKit API key that the site uses to sign join tokens and server requests.
  • Default: empty.
  • Values / limits: plain text. Shown in the form.
  • When to change it: when you set up LiveKit; when you rotate keys in LiveKit (change the key and the secret together).
  • Related: API secret

API secret

  • Where: Video → LiveKit
  • What it does: The secret paired with the API key. Join tokens are short-lived and signed with it.
  • Default: empty.
  • Values / limits: Admin only. Never shown back; an empty field keeps the current secret. The Clear API secret (Видалити секретний ключ API) checkbox removes it, which makes LiveKit "not ready".
  • When to change it: when you rotate keys in LiveKit; clear it to switch on-site calls off for good on this site.
  • Related: API key

Bunny Stream (intro video)

Bunny Stream stores and plays specialist intro videos. Needs an external account. The feature is ready when the library ID, API key, token authentication key and CDN hostname are set. Upload status reaches the site in two ways: the site checks Bunny every 15 minutes, and Bunny can also notify the site at once through a signed webhook.

Changing the library or keys while videos exist. Once a library has been in use, changing Library ID, API key or Token authentication key is refused while any intro video from that library still exists in the registry or deletion jobs for it remain: "First delete videos from the previous library." If the registry or queue cannot be read, the save is refused too ("Could not verify …").

Webhook setup

When the site can build its webhook address, the block shows three steps under "Bunny webhook setup:":

  1. Paste the shown address (it ends in /wp-json/expertpress-video/v1/bunny-webhook) into the webhook field of your Bunny Stream library. No secret goes in the address.
  2. Copy the library's Read-Only API key from Bunny Stream → Library → API and save it in Read-Only API key (webhook signatures).
  3. Nothing else is needed: Bunny signs every webhook request, and the site checks that signature with the Read-Only API key.

Library ID

  • Where: Video → Bunny Stream (intro video)
  • What it does: The Bunny Stream video library where intro videos are created.
  • Default: empty.
  • Values / limits: plain text. Locked against changes while videos from the current library exist (see above).
  • When to change it: at first setup; when moving to a new library after all old videos have been deleted.
  • Related: API key, Token authentication key

CDN hostname

  • Where: Video → Bunny Stream (intro video)
  • What it does: The library's CDN host, for example vz-xxxx.b-cdn.net. Required for the feature to count as ready.
  • Default: empty.
  • Values / limits: a host name; a leading http:// or https:// and a trailing slash are removed, letters are lowercased.
  • When to change it: at first setup, copied from the library settings in Bunny.

Pull zone (optional)

  • Where: Video → Bunny Stream (intro video)
  • What it does: Stores the name of the library's pull zone for reference. In the current version it is not used for uploads or playback.
  • Default: empty.
  • Values / limits: plain text, optional.
  • When to change it: only if you want to keep the pull zone name next to the other Bunny settings.

API key

  • Where: Video → Bunny Stream (intro video)
  • What it does: The library API key. The site uses it to create a video before each upload, read its status, list the library during the daily check and delete videos.
  • Default: empty.
  • Values / limits: Admin only. Never shown back ("API key: set." / "API key: not set."); an empty field keeps the current key. Clear API key (Очистити API-ключ) removes it. Locked against changes while videos from the current library exist.
  • When to change it: at first setup; when the key is rotated in Bunny and no videos remain in the old library.

Token authentication key

  • Where: Video → Bunny Stream (intro video)
  • What it does: Signs playback links. Every intro video is played through a link that expires (by default after one hour), so a copied link stops working.
  • Default: empty.
  • Values / limits: Admin only. Never shown back; an empty field keeps the current key. Clear token key (Очистити ключ токена) removes it. Locked against changes while videos from the current library exist. Turn on token authentication for the library in Bunny so unsigned links are refused.
  • When to change it: at first setup.

Read-Only API key (webhook signatures)

  • Where: Video → Bunny Stream (intro video)
  • What it does: Checks the signature of every webhook from Bunny Stream. Without it, webhooks are refused ("Read-Only API key: not set. Signed webhooks will be refused.") and the site relies on its 15-minute status checks.
  • Default: empty.
  • Values / limits: Admin only. Never shown back after the save message. Clear Read-Only API key (Очистити Read-Only API key) removes it. ExpertPress cannot generate this key; copy it from Bunny.
  • When to change it: at first setup; after rotating the key in Bunny, replace it here.

Intro video

Limits for specialist intro video uploads. See Intro videos for the full flow.

Max duration (seconds)

  • Where: Video → Intro video
  • What it does: The longest intro video allowed. A longer video is rejected automatically once Bunny has processed it, before it reaches the moderation queue.
  • Default: 60 seconds.
  • Values / limits: 15–600 seconds; values outside are moved to the nearest limit.
  • When to change it: raise it to 90–120 seconds if specialists need more time to introduce themselves; keep it short so profile visitors watch to the end.
  • Related: the moderation queue marks videos shorter than 10 seconds (duration_short) and videos close to the maximum (duration_long).

Uploads per day

  • Where: Video → Intro video
  • What it does: How many uploads one specialist can start per day. Further attempts get "Daily upload limit reached."
  • Default: 3.
  • Values / limits: 1–20.
  • When to change it: raise it during onboarding when specialists are trying several takes; lower it if storage use at Bunny grows too fast.

Rejected video retention (days)

  • Where: Video → Intro video
  • What it does: Intended as the number of days a rejected video is kept. In the current version the value is saved but not applied: rejected videos are kept in the Bunny library as a record of the moderation decision and are not deleted on a timer.
  • Default: 30 days.
  • Values / limits: 1–365 days.
  • When to change it: no effect at present.

Call transcription

Optional automatic transcription of on-site calls into text, to help resolve complaints and fraud. Video is never recorded. The screen reminds you: "Enable only together with a site rules clause covering call transcription."

Transcription needs a separately deployed transcription worker registered with your LiveKit server under the agent name below. Needs external infrastructure. When a call starts, the site asks LiveKit to send that worker into the room. The worker joins as a hidden participant (it is not shown as a person and does not take a seat), and posts text segments back to /wp-json/expertpress-video/v1/transcript-segments, signed with the agent secret. The site accepts text only for calls the worker was sent to, only for real participants of that call, and only while the call is open.

Every participant sees a notice in the call lobby: "This conversation is automatically transcribed to help protect against fraud; video is not recorded." A theme or site plugin can change this text with the expertpress_video_transcription_notice filter.

The module has no screen for reading transcripts. They are available through the WordPress personal data export and to add-ons.

Call transcription

  • Where: Video → Call transcription (Розшифровка дзвінків)
  • What it does: Turns transcription on or off. The choice is fixed for each call when the first person joins: switching on applies to new calls, switching off also removes the worker from calls already running (in the background).
  • Default: off.
  • Values / limits: on / off. Cannot be switched on without an agent secret: "Call transcription needs the agent secret. Generate it, then switch transcription on."
  • When to change it: turn it on after the worker is running and your site rules mention transcription; turn it off if the worker is down so participants are not told their call is transcribed.
  • Related: Retention (days); Data retention

Agent name

  • Where: Video → Call transcription
  • What it does: The name under which the transcription worker is registered with LiveKit. The site asks LiveKit to send an agent with this name. A running call keeps the name it started with.
  • Default: expertpress-transcriber.
  • Values / limits: letters, digits, dot, underscore and hyphen; up to 128 characters. Other characters are removed; an empty value goes back to the default.
  • When to change it: when your worker is deployed under a different name, or you run separate workers for several sites on one LiveKit project.

Retention (days)

  • Where: Video → Call transcription
  • What it does: How long transcript text is kept. A daily cleanup deletes older segments. Segments stay longer while the call is still open, while a complaint exists for the booking (or for a seat in the group meeting), or when someone reported a connection problem or the specialist muted or removed a participant during that call.
  • Default: 14 days.
  • Values / limits: 1–365 days.
  • When to change it: lengthen it (30–60 days) if complaints are often filed late; shorten it to keep less personal data.

Transcription languages

  • Where: Video → Call transcription
  • What it does: Languages the speech recognition is tuned to. Sent to the worker with each call; a running call keeps the languages it started with.
  • Default: the site language if it is English, Ukrainian or Russian; otherwise English.
  • Values / limits: any of English, Ukrainian, Russian. None selected means the site language. Text in other languages is refused.
  • When to change it: select every language your specialists hold sessions in.

Generate / rotate agent secret

  • Where: Video → Call transcription
  • What it does: Creates a new random secret (48 characters) that the worker uses to sign the text it sends. After saving, the new secret is shown once as "New transcription agent secret — copy now; it will not be shown again." Put it into the worker's configuration. The old secret stops working at once.
  • Default: no secret ("Agent secret: not set. Generate one before enabling transcription.").
  • Values / limits: Admin only. Checkbox; applied on save.
  • When to change it: at first setup; when the worker's configuration may have leaked.

Clear agent secret

  • Where: Video → Call transcription
  • What it does: Removes the agent secret. Text from the worker is then refused.
  • Default: off.
  • Values / limits: Admin only. Checkbox. Cannot be combined with transcription switched on.
  • When to change it: when retiring the worker.

Data retention rows

The module adds two rows to ExpertPress → Settings → Data retention. The common rules for periods, units and the daily cleanup are described there.

Transcript dispatch history

  • Where: ExpertPress → Settings → Data retention → Editable retention periods (Історія запуску транскрипції)
  • What it does: Deletes the log of transcription worker launches for calls, measured from creation. Only rooms that are finally closed and outside any joining or retry window are removed. The transcription launch history of completed calls is lost.
  • Default: 0 (keep indefinitely).
  • Values / limits: 1–36500 days or 1–1200 months.
  • When to change it: set 90–180 days once transcription has been running for a while and you do not need old launch records.
  • Related: Retention (days) (the transcript text itself has its own period)

Deleted intro video history

  • Where: ExpertPress → Settings → Data retention → Editable retention periods (Історія видалених відео-знайомств)
  • What it does: Deletes records of intro videos that were deleted before reaching moderation (measured from deletion), and records of deletions that Bunny Stream confirmed (measured from confirmation). Moderation decisions, replaced videos, held or unfinished deletions are kept.
  • Default: 0 (keep indefinitely).
  • Values / limits: 1–36500 days or 1–1200 months.
  • When to change it: set a period (for example 12 months) to keep the registry small on a site with many uploads.

Provider deletion queue (read-only panel)

Where: at the bottom of the Video screen, Provider deletion queue (Черга видалення у провайдера).

Shows the state of the local queue of video deletions at Bunny Stream. Opening the screen does not contact Bunny. Columns: State, Jobs, Oldest job age. Rows:

  • Deleting, lease expired — a deletion attempt started but did not finish in time; it is retried.
  • Held for evidence — deletion stopped because the video is a moderation record.
  • Needs review — the site could not prove the video is safe to delete automatically; check it in your Bunny library.
  • Pending — waiting for the next run (every 15 minutes, and daily).

Below the table: Last error reason (a short code, or "transport error (details hidden)") and Last complete Bunny library snapshot (the time of the last full daily comparison of the library with the site's registry, or "not taken yet"). Values that cannot be read show "unavailable". There are no actions on this panel.


Intro videos moderation queue

Where: ExpertPress admin app → Work → Intro videos (Відео-знайомства), next to Moderation. Needs expertpress_moderate (for example ExpertPress Moderator) or administrator.

Lists up to 100 intro videos that Bunny has processed and that wait for a decision, with "No intro videos awaiting moderation." when empty. Intro video decisions are separate from profile text moderation. Each item shows:

  • the specialist's name, duration and resolution;
  • warnings, if any: duration_short (under 10 seconds) or duration_long (close to the maximum duration);
  • a player (signed link, valid for a limited time).

Actions:

  • Publish (Опублікувати) — the video appears on the specialist's public profile, replacing the previous one, and the specialist receives the Intro video approved email. Refused if the account was closed meanwhile.
  • Reject (Відхилити) with a required Reason (Причина, up to 500 characters) — the specialist receives the Intro video rejected email with the reason and can upload another video.

If the action fails (for example, someone else decided first), the page says "The action was not completed."