Setting up an event
Password-protect your event
Put your event page behind one or more shared passwords, test the gate and replace access without locking out the people you still want to admit.
- For
- Sharing a private event through one or more trusted groups
- Takes
- 7 minutes
- Open Event Settings and turn password protection on
- Add a separate password for each group that needs one
- Save Event Settings
- Send the event link and password in separate messages
- Test the gate in a private browser window
- Replace a shared password without closing the event
- Review completed sales by password
- Turn protection off before removing the final password
What you need before you start
- You can edit Event Settings for the event.
- You have the event link and a private browser window ready for the final test.
-
Open Event Settings and turn password protection on
Open the event, select Event Settings, then turn on Password required to view event. Enter your first password under New Password and select Create.
Use a password you can say, paste and type without guessing. A separate password for each guest group makes later replacement and sales reporting clearer.
Event Settings, Password required to view event. -
Add a separate password for each group that needs one
Enter another value under New Password and select Create for each group. The Existing Passwords table shows every password that can open the event.
Separate passwords let you close one route without disturbing the others. They also separate completed sales in Sales by Password.
-
Save Event Settings
Select Save Event Settings after the switch is on and at least one password appears under Existing Passwords. Wait for the saved confirmation before you leave the page.
-
Send the event link and password in separate messages
Send the normal event link first, then send the password through the private channel you use for that group. Name the event beside the password so nobody has to guess where it works.
Anyone who knows a working password can open the page. Use personal invitations when you need a separate link and limits for each person.
-
Test the gate in a private browser window
Open the event link without a signed-in session. Confirm that the event asks for a password, rejects a value you did not create and opens after you enter a current password. Add a ticket to the basket before you finish.
Test an embedded checkout too when you use one. The embedded checkout asks for the event password before it exposes protected ticket details.
-
Replace a shared password without closing the event
Create the replacement first, send it to the people who still need access, and test it. Then select Delete beside the old password and Refresh to confirm that only the current values remain.
Someone who returns with a deleted password has to enter a current one before continuing. The other passwords keep working.
-
Review completed sales by password
Open the event performance area and choose Sales by Password. Compare the ticket type, password, number of sales, revenue and gross revenue in each row.
Use a separate password for each guest group when you want this report to show which route produced the sale. The password proves which shared value was entered; it does not identify the person who shared it.
Performance, Sales by Password. -
Turn protection off before removing the final password
Turn off Password required to view event, select Save Event Settings, and test the public page. Remove passwords you no longer need only after the event opens without one.
Or have it done for you
Fai, the assistant inside your dashboard, can add or remove event passwords and turn password protection on or off. She shows you the event and asks you to approve each change before she makes it. You can also complete the whole workflow in the dashboard.
In your dashboard, with Fai
Find my event by name, add these event passwords: <PASSWORDS>, and turn on Password required to view event only after at least one password is saved. Show me the event and every password that will remain, then ask me to approve each change
Questions you might have
- Can my event have more than one password?
- Yes. Add each one under New Password. Every value listed under Existing Passwords can open the event until you delete it.
- Can I see which password sold tickets?
- Yes. Open the event performance area and choose Sales by Password. Completed sales are grouped by the password used for the order, which is why separate values are useful for separate guest groups.
- Does a password identify the person buying?
- No. The password proves that someone knows the shared value. Use personal invitations when you need one link and purchase limits per recipient.
- What happens if someone shares the password?
- The other person can use it while it remains active. Create a replacement for the intended group, send that replacement, test it and delete the shared value.
- Does the password also protect my embedded checkout?
- Yes. The embedded checkout asks for a valid event password before it returns protected event and ticket details.
- What is the difference between an event password and a ticket access code?
- An event password protects the whole event page. A ticket access code leaves the page visible and reveals the hidden ticket types attached to its promotion.
Where to go from here
Do this on your own event
Create your account, build your event and follow the steps in your own dashboard. You do not need to book a sales call.