Skip to content

Running live events in Agora

The Live Events section helps a content manager prepare the public page for an upcoming broadcast, collect viewer requests, confirm participation, and grant access through personal invitation links.

Technically, running a live event means creating a separate new stream for a specific broadcast. This stream exists in the context of the event: its source, processing, and delivery are prepared in advance, the broadcast is run, and after it ends the recording is used or the broadcast scenario is closed.

This is what makes a live event different from a 24/7 TV stream. A permanent TV stream works as a continuous broadcast channel: it exists independently of any single event, may run around the clock, and is usually not tied to participant registration. A live event, by contrast, combines a one-off or time-limited broadcast with the viewer workflow around it: announcement, scheduled time, public page, participant registration, and invitation list.

When to Use Live Events

Live events fit scenarios where viewing needs an organizational layer:

  • webinars and online conferences;
  • internal corporate events;
  • broadcasts with pre-registration;
  • events where access must be issued individually, after manual approval or from a prepared participant list.

The same mechanism can be used both for closed internal corporate events and for public broadcasts. In both cases, Agora is designed around access pre-moderation: a viewer reaches the broadcast only after their request is approved or a personal invite is issued, so unrelated participants do not get access automatically.

If you only need to ingest and distribute a video stream without a public page or requests, configure a regular stream.

Main Workflow

Working with a live event usually follows several steps:

  1. The content manager creates an event card and fills in the title, description, date, time, and time zone.
  2. After the details are checked, the card is published to the Agora portal.
  3. If needed, the public landing page is enabled so viewers can submit participation requests.
  4. Requests are added to the event invite list.
  5. The content manager moderates requests: approves, rejects, revokes, or resends invitation emails.
  6. The viewer follows the email link, completes registration, and receives access to the event.

What the Content Manager Sees

In the admin UI, the workflow is centered in Content -> Live Events. The list shows created events, their slugs, start dates, time zones, public page publication status, and last update time.

The event card has two main tabs:

  • Edit event — the main event fields, page publication, and public landing page toggle;
  • Invite moderation — creating invitations, filtering requests, and actions on invites.

What the Viewer Sees

On the portal, the viewer can access:

  • the catalog of published events;
  • the public page of a specific event;
  • the request form, if the event landing page is enabled;
  • the invitation-link page from the email;
  • a personal list of requests and invitations after signing in.

The viewer can start as an anonymous visitor: open the public page, leave an email and name, receive an email, and complete registration through the link. After registration is completed, the portal session is linked to the client, and subsequent requests are made as the registered viewer.

Section Pages

Detailed steps are described on separate pages: