Sometimes you want to limit attendees to certain guests. We have several ways to either restrict access to your event page or you can manually approve each guest. Depending on how critical it is that you control who attends the event, you could use one of these options (from more least effective to more effective and involved).
Obscure Event Pages
One simple way to help that only people who have a link to your page can find your event page is to hide or unpublish the event pages that list all your events. Then, create a obscure url (
- Change your home page to a static page (e.g. use a page or post that does not show your event list).
- Remove any menu items from the navigation that reference the Event List page (e.g. /events/)
- Use an obscure url for the event. I recommending using a custom page or post and embed the ticket selector shortcode on the page to give people ticket options on that static page. People will be unlikely to find your event page without your link.
Then you can distribute the link to the static page or post that you created. But again, links can be passed around via email or social media or sms (text), so it is possible that people will access that page if they get a hold of that link.
Password-Protected Event pages
You could also password-protect your page so that it requires a password that you set.
When publish your event, go to the:
- Save New Event or Update Event option
- Change the visibility from Public to Password Protected
- Set your required password
- Distribute your password to your wanted attendees.
From then on, anyone will be required to provide the password to see that page. This will help exclude people without the password from seeing the event details.
Again, passwords can also be circulated so it's still possible unwanted guests can register.
Manually Approving Registrations
The Advanced Event Editor upgrade feature is required for this option.
Passwords can be circulated and so can links. The only way that you can ensure that people who register for the event is to manually approve them individually. You can set the default registration status to Not Approved, then people can register, but not pay, until you approve them to pay. Once you approve someone (set their registration status to Pending Payment), you can notify them that they are approved to buy their tickets. That's the most secure way to handle it.
When you edit your event, set the Default Registration Status to Not Approved.
Then, when people register for your events, you'll be notified that someone needs to be approved before they can make a payment. You will review the attendee record, and and if you want to allow them to pay, you can set their registration record to Pending Payment and notify them via email that they can make a payment to complete their registration.
If you have more questions about this, please contact us