Skip to content

Request and Invite Moderation

Event requests are stored as invites. An invite links the event, the viewer's email, request source, current status, and the state of the personal invitation link.

Moderation is performed in the event card on the Invite moderation tab.

Creating a Manual Invite

A content manager can create an invitation manually without waiting for a request from the public landing page.

When creating an invite, specify:

  • email;
  • name;
  • phone;
  • internal comment;
  • initial status;
  • whether to send the email immediately.

If the approved status is selected, the email can be sent immediately on creation. If the waiting_approval status is selected, sending the email on creation is unavailable: the invite must be approved first.

Invite Sources

The invite list shows the source:

  • manual — the invitation was created manually by a content manager;
  • landing — the request came from the public landing page;
  • group_rule — the invitation was created by a rule or external automation.

The source helps separate self-submitted requests from pre-arranged participant lists.

Request Statuses

The main invite statuses are:

  • waiting_approval — the request is awaiting a moderator decision;
  • approved — the request is approved and access can be granted;
  • invite_sent — the invitation email has been sent;
  • rejected — the request was rejected;
  • revoked — access or the link was revoked.

The invitation token state is shown separately:

  • active — the link is valid;
  • used — the link has already been used;
  • expired — the link has expired;
  • revoked — the link was revoked.

Filtering the List

On the moderation tab, you can:

  • search requests by email, name, or phone;
  • filter by status;
  • filter by source;
  • refresh the list manually.

This is useful when an event has many requests and the moderator needs to quickly find a specific participant or process only requests from the landing page.

Actions on Invites

Each row provides the main actions:

  • Approve — approve the request;
  • Reject — reject the request;
  • Resend — resend the invitation email;
  • Revoke — revoke the invitation or link.

Bulk actions are also available:

  • Approve all waiting — approve all requests in the waiting_approval state for the current event;
  • Revoke all for event — revoke the current event's invites.

Before using bulk actions, apply the needed filters and check the list, because the operation affects many participants at once.

If an invite is already linked to a client, the email in the list becomes a link to the client card. This means Agora knows the registered viewer and can show their consents, profile, and related sessions.

If there is no client_id yet, the invite remains only an email-based request. The link to a client appears after registration is completed or after matching the invite to an existing client.

Moderator Workflow Recommendations

For careful request processing, use a simple order:

  1. Filter requests by the waiting_approval status.
  2. Check the email, name, phone, and internal comment.
  3. Approve requests that can receive access.
  4. Reject requests that should not receive access.
  5. For approved participants, use Resend if the link needs to be sent again.
  6. If access should no longer be valid, use Revoke.

Rejection records the decision on the request. Revocation is used when access has already been issued but must be stopped, or when the link must be made invalid.