Skip to main content
Restrict Ticket Access lets you control who can buy tickets to an event while still showing public information (date, time, location). Use it for a pre-sale, alumni gathering, donor event, or private staff function to keep ticketing secure and exclusive. You can choose between two restriction methods:
  • Password Protection: Set one password that attendees must enter before viewing ticket options
  • Email Domain Restriction: Specify up to five domains (for example, company.com or university.edu). Only email addresses matching those domains can complete a purchase
Your event page remains visible to everyone, showing all the standard information. Only the ticket-purchase section asks buyers to verify. Admins can turn restrictions on or off, or switch between password and domain protection, at any time. Changes take effect immediately.
This feature can be combined with individual password-protected tickets for additional layers of security.

Use Cases

Pre-Sales

Offer early-bird access only to newsletter subscribers who know the password.

Alumni/Donor Events

Share password or domain list with alumni or major donors to restrict access.

Private Staff/Student Events

Ensure only on-campus staff (for example, @school.edu emails) can buy tickets.

VIP or Sponsor-Only Access

Limit access to partners by adding their corporate email domains.

Setting Up Restrict Ticket Access

Step 1: Log In to the Manager Portal

  1. Access Your Account:
    • Go to Manager Portal and sign in with your organizer account.
    • From the dashboard, select the event you want to secure.

Step 2: Find the Restriction Settings

  1. Navigate to Event Details:
    • In the left-hand menu of your event, click Event Details.
    • Scroll down until you see the Enable Event Access Restriction section.

Step 3: Enable Restriction

  1. Toggle Protection:
    • Toggle Enable Event Access Restriction to ON.
  2. Choose your restriction type: Password Protection:
    • Select Password Protection
    • Enter your desired password in the field provided
    Email Domain Restriction:
    • Select Email Domain Restriction
    • Enter a domain without @, such as school.edu
    • Click Add another for each additional domain, up to five
  3. Save Settings:
    • Click Save to apply your restrictions.

Step 4: Test Your Restriction

  1. Test the Flow:
    • Open your event’s public page in a private/incognito window.
    • Verify that the ticket-purchase section prompts for a password or requires an allowed email address.
  2. Verify Domain Restrictions:
    • If you use domain restriction, enter an email address with an unauthorized domain in the email prompt and click Submit. Confirm it’s blocked.
    • Then test with an authorized domain to ensure it works.

Step 5: Update or Remove Restrictions

  1. Make Changes:
    • Return to Event Details → Enable Event Access Restriction anytime.
    • To switch from Password to Email Domain (or vice versa), select the other option and save.
    • To disable restrictions altogether, toggle Enable Event Access Restriction OFF and click Save.

Managing Restrictions

Viewing Current Settings

In Event Details, you’ll see whether Password Protection or Email Domain Restriction is active, and the associated password or domains listed.

Editing a Password

  1. Update Password:
    • Click Password Protection.
    • Overwrite the existing password with a new one.
    • Click Save.
All future buyers will need the new password immediately after saving.

Adding/Removing Domains

  1. Manage Domain List:
    • Under Email Domain Restriction, click the “x” next to a domain to remove it.
    • Enter a domain without @, such as school.edu. Click Add another for each additional domain, up to five.
    • Click Save to apply changes.

Switching Restriction Type

  1. Change Protection Method:
    • Toggling from Password to Email Domain (or vice versa) automatically removes the previous setting.
    • Select the new type, configure it, and click Save.

How Buyers Experience Restrictions

Customer Journey

  1. Event Discovery:
    • Visitor lands on the public event page.
    • They see date, time, location, and ticket types—then click Buy Tickets.
  2. Verification Required: Password Protection:
    • A password prompt appears
    • They must enter the correct password to unlock ticket options
    Email Domain Restriction:
    • They enter an email address with an allowed domain in the email prompt and click Submit
    • If it doesn’t match, they cannot proceed
  3. Purchase Flow:
    • After verification, ticket options appear.
    • They select tickets and complete checkout as usual.

Best Practices

Clear Instructions

In your event description or emails to attendees, let people know they’ll need a password or must enter an email address with an approved domain and click Submit.

Use Unique Passwords

Choose a password that’s easy to share with the intended group but hard for outsiders to guess.

Maintain Domain Lists

Periodically review your allowed domains if your audience changes. Remove outdated or irrelevant domains to keep access tight.

Plan for Changes

If you anticipate opening ticketing to a broader audience later, schedule a reminder to disable or update restrictions before that date.

Communication Is Key

Share specific instructions (password or domains) in your marketing emails and social posts so guests know exactly how to access tickets.

Combine with Promo Codes

For extra exclusivity, you can still use promo or discount codes in tandem with restrictions—buyers will need both to unlock certain discounted ticket types.

Troubleshooting

  • Confirm that you saved the correct password or domain entries (no typos, no extra spaces)
  • If using Email Domain Restriction, remind them to enter an email address in the email prompt and click Submit. Addresses at an allowed domain or one of its subdomains (for example, john@school.edu or john@dept.school.edu) are accepted
Go back to Event Details → Enable Event Access Restriction, and click Password Protection to see the current password. To change it, overwrite the password, click Save, and share the new password with attendees.
You can add or remove domains at any time. Changes apply instantly. Notify your audience if you add new approved domains.

Frequently Asked Questions (FAQ)

Currently, you can choose only one restriction type per event. For combined security, consider using a unique password and limiting its distribution to those with the proper email domain.
Up to five domains per event.
Yes. Public-facing details remain visible—only the checkout flow is locked behind the chosen restriction.
Yes. To protect an individual ticket type, use Password protect this ticket in its ticket settings (Password Protected for reserved seating tickets). Event access restriction protects the event’s ticket-purchase flow.
When using Email Domain Restriction, SimpleTix checks the domain (the part after the ”@”) when the buyer submits their email, then carries that email into checkout.

See Also

Learn about other advanced event configuration options.