Core 4All Terminology

Definitions for organizations, teams, events, sessions, providers, captions, outputs, displays, and desktop products.

Written By 4ALL.LIVE

Last updated 12 days ago

Give administrators and operators a shared vocabulary for configuring, rehearsing, supporting, and documenting 4All workflows.

Best for: All users, especially new administrators, producers, support staff, and technical partners.

Before you start

No specific plan is required. Some defined capabilities are plan-gated or require add-ons, wallet balance, permissions, or desktop licenses.

  • Keep this glossary available during onboarding and incident calls.
  • Use the names shown in the current UI when writing internal runbooks.

Reference

  1. Account, organization, and team. An account identifies a person. An organization owns billing, members, roles, branding, provider credentials, events, and entitlements. A team groups members and can scope event access. The General team is the broad default context where configured.
  2. Event and live session. An event is the persistent production record and configuration. A live session is the active operational instance that owns microphones, recognition, translation, outputs, usage, and control state. An event can be offline while its saved configuration remains available.
  3. Setup Wizard and Live Setup. Setup Wizard is the guided configuration flow. Live Setup is the operational workspace used to edit sections, preview, share, run preflight, go live, stop, take over, review status, and open related outputs.
  4. Source, partial, final, and segment. The source language is the language being recognized. A partial is low-latency text that may change. A final is settled provider output. A segment is the timed unit stored, rendered, translated, or exported.
  5. Provider, BYOK, and wallet. A provider performs speech recognition, translation, or TTS. BYOK uses organization-managed credentials where supported. Platform-funded usage draws from included entitlements, allowances, wallet balance, or overage rules according to the plan.
  6. Program Display, Closed Captions, and Extended Screen. Program Display is a shared primary presentation surface. Closed Captions is a production-friendly transparent browser output. Extended Screen is a separately paired surface with independent language and presentation controls.
  7. Viewer, lobby, embed, and destination. The lobby introduces the event and can collect a language choice. The viewer provides personal caption controls. An embed places an allowed 4All experience in another page. A destination is a specific URL or production output.
  8. Remote Control, host, controller, and takeover. The host owns local devices and the live session in Live Setup. A controller is an authorized remote operator. Takeover transfers operational ownership when the existing live host is unavailable or when an authorized producer deliberately assumes control.
  9. ASL private stage and Program output. The private stage is for interpreter monitoring and coordination. ASL Program output is the audience-facing stream or display. Talkback and private cues must not be confused with public audio.
  10. XPression Bridge and 4All Encoder. XPression Bridge transports formatted caption data to Ross XPression. 4All Encoder combines input video/audio, optional embedded CEA captions, encoding, and RTMP/SRT/RIST delivery.

Use this reference to confirm: Team members use consistent terms in event plans, UI instructions, incident reports, and vendor conversations.

Validation checks

  • Ask each operator to distinguish an event from a live session.
  • Confirm the team understands partial versus final captions.
  • Confirm the difference between a public viewer link and an authorized Remote Control link.
  • Confirm the difference between XPression Bridge and Encoder.

Compatibility notes

Calling every screen the viewer

Use the exact destination name so operators open the correct surface.

Calling every operator the host

Only the active host owns local devices and session state; remote controllers may operate through that host.

Calling captions subtitles without context

For production and compliance discussions, specify whether the output is live captions, translated text, WebVTT/SRT, graphics text, or embedded CEA services.

Limits and cautions

  • UI terms can evolve; verify labels after significant releases and update local SOPs.
  • Do not use vague terms such as “the link” during a live incident—state the event, destination, environment, and operator role.
  • 🚀 What Is 4All?
  • 🔄 Event States and Lifecycle
  • 🎯 Production Destinations
  • 🛠️ Limits, Error Messages, and Statuses