Understand Plans, Entitlements, and Feature Gates

Determine why a capability is available, disabled, hidden, or blocked.

Written By 4ALL.LIVE

Last updated 12 days ago

Determine why a capability is available, disabled, hidden, or blocked.

Best for: Organization owners, billing administrators, finance approvers, event producers, and authorized support staff.

Before you start

Commercial actions and protected billing data require the correct organization role. Current plan, enterprise assignment, add-ons, seats, wallet, usage, payment state, and desktop license inventory determine effective availability.

  • Confirm exact organization and authority.
  • Record current subscription, entitlement, wallet, usage, or device state.
  • Obtain required commercial approval before purchase, cancellation, payment, or license transfer.

What to know

  1. Open Billing/Plans. Confirm organization, active plan, interval, and renewal state.
  2. Review quantitative limits. Events, languages, members/seats, concurrency, usage, retention.
  3. Review feature gates. QR logo, Remote Control, Extended Screen, Closed Captions, TTS, ASL, advanced statistics, custom branding, exports, BYOK, priority support, multi-speaker, API, webhooks.
  4. Review add-ons. Check separate purchases/assignments.
  5. Review authorization. Entitlement does not grant role/team permission.
  6. Review event state. Feature may require an event toggle/configuration.
  7. Check usage/wallet. Funding can block an entitled provider feature.
  8. Record the decision. Plan + entitlement + permission + event + usage.

What this unlocks: The approved commercial or license state is reflected in 4All and verified against the intended workflow.

Check your understanding

  • Resolved plan/limits recorded.
  • Control state explained by evidence.
  • Test user receives only intended access.

Common misconceptions

Expected feature hidden

Check plan, enterprise assignment, add-on, organization.

Visible but disabled

Check role, event state/toggle, config, usage.

Plan changed but stale

Refresh/reconcile entitlement state.

Good to know

  • Verify current state before promising features.
  • Plan name alone is insufficient.
  • Commercial changes require authority.

Documentation status: Draft for billing, legal, security, and operational review. Validate current prices, entitlements, and UI before publishing.