Require approval before registration
Updated September 23, 2026
Hold free-page sign-ups for your review, then approve or decline them before anyone is registered for the event.
What it’s for
Require approval captures registrations on Venue first. Visitors submit the form as usual, see a pending confirmation, and wait until you decide. Only an approval registers them for the event.
Use it when the guest list must stay curated: invite-only webinars, partner events, or any free page where an automatic enroll is too open. Paid registration keeps its own path and never goes through this review.
Open your page in the builder, on step 4 · Settings. The “Require approval” block sits below the access rules (free pages only).
Turn on “Require approval”. New sign-ups stay pending: nobody is registered for the event until you decide.
You cannot turn the setting off while anyone is still waiting on a decision. Open the Registrants tab. Views of the same list sit side by side, each with its own count: Approved (everyone who is registered), Waiting while approval is on, and Declined beside it. Waiting is the one to watch, so you can see from the tab whether anyone needs you. Waiting list and Failed join them when the page keeps a waiting list, or when the event platform refused someone.
Every waiting row leads with its decision: Approve or Decline. Tick rows to decide a batch at once. Declined keeps your past decisions and says why each request ended there. Move back to Waiting puts one in front of you again, and approving it from there runs the usual checks as if it had just arrived.
Declining tells the visitor nothing and blocks nobody: the same person can register again and comes back to Waiting.
Good to know
- Approve one runs the same registration path as a normal free sign-up, including capacity and sessions, and enrolls the visitor on the page’s event platform when the event comes from a connector. Bulk approve runs in the background and shows progress on the Registrants tab.
- An approval the event platform refuses moves to the Failed view, tagged “Approved”, and is retried automatically. Fix the cause, then use “Retry all” there, which also restarts the rows that ran out of attempts; “Discard” gives up on one. See “Recover registrations the event platform refused”.
- Changing the linked event moves waiting and failed requests to Declined, marked with that reason: those submissions were captured for the previous event. Move one back to Waiting to decide it against the new event.
- Unavailable while registrant retention is “Don’t store on Venue”: Venue needs a place to keep the pending form answers.
Related articles
- Control access and privacyPassword-protect the page, set its visibility, redirect after registration, and cap sign-ups.
- Create and revoke API keysIssue workspace keys to call the Venue API from your own code. Revoke them when you no longer need them.
- Set how long registrant data is keptChoose a retention window for the personal data collected through your pages, or keep none on Venue at all.
Still need help?
Ask AI for a docs-grounded answer, or talk to our team.
Was this article helpful?