Skip to main content

Video room templates: consistent rooms, one click

A room template saves a video room’s setup once so every host spins up the same room without re-entering settings. Save the configuration a weekly standup, a client consultation, or a webinar should always open with — the participant cap, the time limit, whether recording starts, the waiting room, and the rest of the host-facing defaults — and the next room is one click instead of a dozen fields. Templates are per tenant. One saved template works for everyone on your workspace, so a sales demo room in Berlin runs on the same configuration as the one in Austin.

Who can manage templates

Template actions need video:write, which is available to the owner, admin, and developer roles — the same roles that can create rooms. Listing the template library only needs video:read, so API keys scoped for read access can read templates back, but every create, update, delete, and instantiate call requires the write scope.

Where templates live

In the dashboard, open Voice → Video → Templates (/voice/video/templates). The page lists every saved template as a card with its name, description, and a badge summary of the settings it locks in — for example “Up to 20 participants”, “Ends after 30 min”, “Recording on”. A workspace can keep up to 100 saved templates. When you reach the library cap, New template is disabled — delete a template to make room.

Template lifecycle

  1. Create. Click New template, give it a name and an optional description, and pick the room defaults it should apply. Every setting is optional — leave a field unset and rooms created from the template fall back to the normal room default.
  2. Edit. Click the pencil on a template’s card to rename it or change its configuration. The update replaces the stored configuration in full, and fields the form doesn’t render (for example, a codec preset set over the API) are preserved on save.
  3. Duplicate. To branch off an existing template, open it for edit, adjust the one or two settings you want to vary, and save the result as a new name. The library shows both side by side.
  4. Delete. Click the trash icon and confirm. Deleting a template removes the saved configuration only — rooms already created from it are not affected and keep running with the settings they took at creation.

What a template locks in

Each setting is a default the new room starts with. Nothing here seals the room permanently — a host with the right role can still change a live room’s lock or cap afterward.
  • Max participants — 2 to 300. Leave unset to inherit your plan’s participant ceiling.
  • Max duration — 5 minutes to 24 hours. The room ends when it hits the limit.
  • Recording — start recording automatically, with a choice of composite (one mixed file), per-participant tracks, or both. In a two-party-consent jurisdiction the same consent gate as a manually-created room applies.
  • Waiting room — arm the lobby on every room from this template, with an optional auto-admit that promotes the next person in line when a seat frees.
  • Virtual background and noise suppression — set to off, allowed, or required instead of leaving them to the room default.
  • Audio-only — open as an audio room with no video publishing.
  • Live captions — require live captions on every room from the template.
  • End-to-end encryption — open with E2EE enabled.
  • Media region — pin the room to Europe or the United States, or leave it automatic.

Create a room from a template

On the template card, click Create room, then name the room and optionally schedule it. The new room inherits everything the template saved — its participant cap, duration, recording defaults, waiting room, and the rest — and lands you in it as host, so the per-template defaults apply from the first click. Over the API, the same flow is two calls:
The template routes mirror the room-create path exactly — the same participant-cap gate, recording auto-start, waiting-room lobby, consent gate, and audit trail as POST /video/rooms-scheduled.

Roles and permissions, in practice

  • A template belongs to the tenant, not to the person who saved it. Any owner, admin, or developer in the workspace can view, edit, duplicate, and delete the shared library — there is no per-template ownership to transfer.
  • Viewer and billing roles cannot open the Templates page at all; the dashboard gate matches the API’s video:write requirement.
  • An API key with video:read may list templates (GET /video/room-templates); mutating and instantiating require video:write plus an owner, admin, or developer role on the key’s account.

Three templates worth saving first

  1. 30-minute synchronous webinar — 300 participants, 30-minute max duration, recording on (composite), waiting room on with auto-admit, live captions required. Presenters start on time and nobody sits in an unrecorded session by accident.
  2. 1:1 video consultation — 2 participants, 45 minutes, waiting room on, recording off, end-to-end encryption on. Every intake call opens identical, private, and capped.
  3. Team standup, 20 max — 20 participants, 30-minute hard stop, audio-only, live captions required. A standing daily room that never runs long and never fills up.