5h ago

Offer Registration Restrictions per ticket type

Offer Registration Restrictions per ticket type I would like to restrict SPECIFIC ticket purchases/registrations by email domain. My Particular Use Case: Creating our community hub with Heysummit as an ongoing series. One of our membership plans allows all employees to register for free. restricting a specific hidden ticket type would achieve this perfectly. This would also work to create a hidden ticket type for internal company employees woth private chatrooms. Maybe others have their own use cases for providing email and domain restrictions per ticket type. Would be an incredibly useful feature here in any case. Thanks for considering it.

Completed

4 hours ago

Okay, I'm pleased to say this has now been delivered. As always, do let us know if you have any feedback. Changelog below. https://heysummit.userjot.com/updates/p/email-restrictions-n…

4 hours ago

Thanks Ben This really does make a big difference for us, as you should see next week when we send invites out to use this feature. Thanks again

4 hours ago

Fab - glad it helps :)

4 hours ago

Hey Andrew, just following up on this one. We could potentially add the ability to restrict tickets to individual emails or email domains, but this would only work in a couple of scenarios or at least there are a couple of edge cases you'd need to be aware of. Depending on how you set up the event, if you're not asking for the email before someone registers (i.e., as the very first thing that they do), then we will always show tickets first. This essentially means that they would potentially see tickets that they might later on not be able to access by virtue of the email that they later on add. Would this in itself be an issue for you? Or are you just looking for some extra control so that you can intentionally choose to hide that ticket from the checkout and then you create a secret page that drops in this ticket (which it sounds like you're potentially already doing) but you just want that extra peace of mind knowing that if someone stumbles upon that page and tries to get access to that ticket there is a restriction in place that locks that ticket to a particular domain or set of email addresses. Is it more this that you're trying to achieve so that you've got that extra control should you need it? If I can just have you clarify, this shouldn't be too difficult to roll out.

4 hours ago

That would not be an issue, and yes exactly the scenario I was looking to avoid, people sharing the link with folks who should not have access. So I want to restrict to specific domains and or email addresses. Understand the limitations and potential edge cases, would not be an issue for what we have in mind. Thanks @ben

4 hours ago

OK perfect. Thanks for clarifying. We should be able to work on that later this week. I’ll update you once done :)

4 hours ago

Thank you so much Ben

4 hours ago

A hidden ticket type would be great

4 hours ago

That is available @Henk Werner You can do that by ticking the “hide at checkout” when creating a ticket. That is certainly a workaround we could use, but does require us to manually verify each registration, and then and links are easily shared to folks who should not have access, in our use case the link might be shared with 100 or more people at a company.