Event Identity, Team, Schedule, and Limits

Choose durable event metadata and understand how teams, slugs, dates, and plan limits affect operation.

Written By 4ALL.LIVE

Last updated About 1 month ago

Choose durable event metadata and understand how teams, slugs, dates, and plan limits affect operation.

Best for: Organization administrators, event producers, live operators, and authorized support staff.

Before you start

Event access and actions depend on organization role, team scope, plan entitlements, limits, and current event state.

  • Use an individual verified account in the correct organization and team.
  • Confirm the event owner, live operator, output owner, and incident authority.
  • Review the current configuration before changing an existing or live event.

Step by step

  1. Choose a durable name. Include event/program identity and environment where useful; avoid confidential data.
  2. Use an approved image. Optimize for lobby/mobile and preview all crops.
  3. Set location and description. Write attendee-facing context and support instructions without internal details.
  4. Set dates/time zone. Use the authoritative production schedule and include overnight/time-zone edge cases.
  5. Assign organization/team. Verify access using a non-admin member.
  6. Choose a slug. Use a short stable URL-safe value before generating QR codes or embeds.
  7. Check limits. Review maximum events, language caps, features, member seats, usage/wallet, and desktop licenses.
  8. Freeze public metadata. After distribution, change slugs/schedule only through an approved communication plan.

What success looks like: The event reaches the intended saved or live state, and every required operator can verify the result without receiving unnecessary access.

Check your setup

  • Metadata matches the event brief and public lobby.
  • Time-zone rendering is correct for production and attendees.
  • Entitlements cover the configured workflow.

Troubleshooting

Slug unavailable

Choose a unique value and regenerate links only after saving.

Schedule appears wrong

Check stored time zone versus browser locale and daylight-saving transition.

Feature/limit warning

Reduce scope or resolve plan/add-on/wallet state before rehearsal.

Security and operational notes

  • A slug change can invalidate printed QR assets and embeds.
  • Do not put passwords, backstage details, or private contacts in public fields.
  • Use clear production/test naming.