4All Platform Terminology and Data Flow

Understand organization, team, event, source, transcript, language, display, viewer, output, export, and device concepts.

Written By 4ALL.LIVE

Last updated 12 days ago

Give production, support, and engineering teams a shared vocabulary for how audio becomes accessible live content.

Best for: All 4All users, integrators, and support staff.

Before you start

Terminology is universal; feature availability varies by plan, role, and product.

  • Use the current production release and approved organizational policy.
  • Record resource IDs, exact time zone, and accountable owner.
  • Validate in a non-production environment when possible.
  • Identify your own organization/team/event example.
  • Use the current product UI when labels differ.
  • Read Platform Overview first.

Reference

  1. Organization: billing, security, branding, providers, members, and plan boundary.
  2. Team: operational group that owns events and team roles.
  3. Event: scheduled/configured production container with live state, languages, sharing, outputs, and deliverables.
  4. Input/source: microphone, channel, speaker route, local or cloud recognition source that creates text.
  5. STT/transcription manager: turns audio into partial/final captions; model/provider/tuning influence latency and accuracy.
  6. Transcript v3: realtime caption state transported through secure WebSockets with sequence/final/source metadata.
  7. Translation/TTS: transforms source captions into target-language text and optionally spoken audio.
  8. Display/viewer/stage/remote: different consumers and control surfaces for captions, ASL, branding, and operator actions.
  9. XPression Bridge/Encoder/Desktop: companion apps for graphics DataLinq, CEA-embedded streaming, and desktop/local operation.
  10. Export/statistics/usage: post-event deliverables and operational/commercial records; they are related but not interchangeable.

Use this reference to confirm: Teams can describe a problem by layer and resource without ambiguous labels.

Validation checks

  • Runbooks use organization/team/event IDs.
  • Source and output are named separately.
  • Caption language and UI language are not confused.
  • Usage record and transcript export are distinguished.

Compatibility notes

  • Event vs channel confusion: use event ID and language/channel explicitly.
  • Display vs viewer confusion: describe URL/surface and operator ownership.
  • Caption overlay vs embedded CEA: identify rendering vs bitstream insertion.
  • License vs user role: separate commercial entitlement from permission.

Limits and cautions

Important: Names and IDs can appear in logs and exports. Treat identifiers according to your data-classification policy.