Hide tickets from the public (comp, volunteer and invite-only tickets) | Feature requests

Hide tickets from the public (comp, volunteer and invite-only tickets)

complete

Michel (Product @Zeffy)

Organizers want to create a ticket on their form without showing it to everyone. Today the only workaround is to build the ticket at the last minute, or to delete it and recreate it later.
This is different from scheduling a ticket's sales window, which is now available. Scheduling controls when a ticket can be bought, and the ticket stays visible on the form with its status. This request is about ticket types that should not appear publicly at all.
The situations that come up most often:
Comp and free tickets. Organizations give free tickets to guests, sponsors or board members, and would rather the public not see that a $0 ticket exists.
Volunteer tickets. The same need for volunteers, usually with the wish to keep them as their own ticket type in the guest list instead of adding each person by hand.
Reserved tickets. Holding a few tickets for hosts, speakers or specific patrons who may not buy right away, including on an event that is otherwise sold out.
Group or discounted rates for a specific audience. A reduced rate for a partner organization or a particular group, which should not be offered to everyone.
Access-code tickets. Revealing a hidden ticket only to people who enter a code you gave them, rather than a discount code that applies to the whole order.
What organizers describe wanting:
A way to mark a ticket as hidden and to unhide it later, without deleting and recreating it.
Optionally, a code that reveals a hidden ticket to the people who have it.
Hidden tickets still showing normally in the guest list and in reports, so attendance stays easy to follow.
If this matters to your organization, please upvote and tell us which of these cases is yours. It helps us scope the right first version.

September 21, 2026

Michel (Product @Zeffy)

Great news, this is now live! 🎉 You can now hide a ticket from your public form, which is perfect for comp, volunteer or guest tickets. The public won't see it, but you can still add it yourself from your dashboard. This works for event and custom form campaigns.

WhoDunnit

Michel (Product @Zeffy) Thank you - this is very helpful!

Any idea on whether the feature you mentioned above - "Optionally, a code that reveals a hidden ticket to the people who have it." - will be implemented, as well? And if so, if there will be any limits on how many times a user / member / e-mail address / etc. can redeem these tickets?

Michel (Product @Zeffy)

Thanks, glad it helps! The access code isn't part of this first version: today a hidden ticket can only be added by your team from the dashboard.

The idea is noted, but we don't have enough requests on it yet to build it now, and we want to avoid making the product more complex. We keep listening to what organizers ask for, so it may come later, and your question on redemption limits per person will help if we do.

Sara

Michel (Product @Zeffy) thank you for following through on this, this is a huge and essential feature for us! 👏�

Michel (Product @Zeffy)

updated the status to

complete

Heidi

We have an in-person fundraiser involving a sale (not an auction). We are taking "or best offers" in person, and I want to list all of the items in Zeffy so that I can take tap payments, but not have these available for the public to see. I also want to be able to set "pay what you can" so that I can adjust the price paid for the item as I sell it at the party, but I don't want people online to be able to find this form and purchase costly items for whatever amount they want.

Anna

Also needed for free press passes.

Korora

Yes! We need the ability to put tickets on hold so that they may be disbursed at a later date; and the ability to assign a complimentary ticket level that won't show publicly- which we use to assign to volunteers, etc. This is important because we need accurate audience metrics (including comps) for grant applications especially.

Willow Wood JH

This is big need for our organization -- especially for a waitlist that we are now having to implement!

CanU

We are having the same issue for discounted tickets and would find hidden ticket options very useful. The only workaround that I can think of is to create a new ticket type in Zeffy for 1 ticket at a time and invoice each discounted ticket holder separately. I can't use the discount code on the general admission ticket because there is a tax receipt tied to a portion of that ticket and the tax receipt is not available for the discounted ticket.

Jacky

We're running into this issue for our Gala. We're having to create coupon codes for volunteers, partners, sponsors, etc. which also allows them to use them multiple times - thankfully they aren't. Pretty much all the scenarios described in this feature request we could use.

For the access-code tickets, just a suggestion that we could enter/import them into Zeffy, including which campaign, ticket type and number of tickets to assign, and let Zeffy generate the code to an email and send it right out to them.

Michel (Product @Zeffy)

Thank you so much for taking the time to share so many concrete examples. Seeing this many detailed comments in just a few days shows there's real interest in this feature, and it makes us want to dig in and see what we can do.

Here's how I understand the core need:

A hide/show toggle on any ticket type, so you can set it up early and reveal it later without deleting and recreating it.
Hidden tickets never appear on your public form.
You can still add them yourself as manual entries: comps, volunteers, staff, performers, vendors, holds, or paper tickets sold elsewhere.
They count toward your event capacity and show up normally in your guest list, check-in and reports.
This works independently from scheduled sales windows.

Does this match what you need?

I fully recognize this only covers part of the needs shared here. It looks like a first part we should be able to build fairly easily, so I wanted to make sure I understood it well.

Some other cases seem more complex to us:

A discounted rate offered to a specific group, such as a partner venue reselling to its members.
Discounted tickets that cast or crew book themselves, with a limit per person.
A free ticket included in a season membership, with a limit per member.
A ticket that only appears with an access code or a private link.

I'll email the people who shared these cases individually to understand them better.

Thanks again for all this feedback and detail. Input like this is what helps us prioritize the features that bring the most value.

Michel (Product @Zeffy) Yes! That describes the core needs of my organization. The other use cases you outlined are not as important to us.

Sara

Michel (Product @Zeffy) the core needs you outlined are exactly what our organization is looking for, especially for our largest event (Shady Pines Festival), where hiding staff/volunteer/performer ticket types, but still having those numbers contribute to guest list/attendance tracking, is essential! Thank you for listening!

Michel (Product @Zeffy)

Perfect thanks a lot, will work on a solution with the team.

WFAE

This is a critical feature for our organization and, specifically, is a deciding factor in whether we can use Zeffy for our annual gala.
Our gala requires us to manage a significant number of reserved and complimentary tickets for sponsors, board members, special guests, speakers and other invited attendees. These tickets need to count toward our total event capacity and remain fully integrated into the guest list, check-in and reporting, but they absolutely should not be visible as $0 or otherwise unavailable ticket options on the public registration page.
For an event of this size and complexity, manually adding guests or creating and deleting ticket types is not a sustainable workaround. We need to be able to establish our full ticket inventory from the beginning, including tickets being held for specific groups, while controlling which ticket types the public can actually see and access.
Ideally, we would have both the ability to keep certain ticket types completely hidden and the option to reveal others through an access code or private link. This would allow us to manage sponsor allocations, complimentary tickets, reserved seats and other special groups without maintaining separate processes outside of Zeffy.
I want to emphasize how important this is: the lack of this functionality has caused us to consider other ticketing platforms specifically for our annual gala, despite our preference to continue using Zeffy. For smaller events, we can sometimes work around the limitation. For our gala, however, robust management of hidden, reserved and complimentary inventory is essentially a requirement.
We LOVE Zeffy, we just need it to fit the scenarios we're facing.

→