# How do you manage backstage access passes for an event? | Ticket Fairy Guides

1. [Ticket Fairy](https://www.ticketfairy.com/)
2. [Guides](https://www.ticketfairy.com/guides)
3. How do you manage backstage access passes for an event?

Questions organisers ask

# How do you manage backstage access passes for an event?

Crew, artists, production and guests get a named pass rather than a ticket, with a limit on how often it works and the same scanner on the door.

For:  Anyone handing out crew, artist or guest access for an event

Takes:  5 minutes

Backstage access can be a ticket type you only give to crew, an add-on sold on top of a normal ticket, or a pass. A pass is the one built for people who come and go: it is issued to a named person, works as many times as you say, and can carry across a run of events. Crew on shift all day, production, security and press usually want that; a guest coming backstage once after the show can be simpler as an add-on on their ticket.

Passes live on the **Multi-Entry Passes** screen. You define a type for each kind of access you hand out, issue passes of that type to people by name, and the holder gets theirs by email. On the night the same scanner app your door team already uses reads a pass as a pass and checks it against its own limit.

## How Ticket Fairy handles it

- ### A pass type for each kind of access

  Create one per role -- crew, artist, production, press -- with a name, a description and the number of times a pass of that type may be used at one event. That number is what stops a crew pass becoming a way in for a queue of friends.
- ### Passes issued by name, in bulk

  Issue one at a time by first name, last name and email, or upload the whole crew list as a CSV. Each pass belongs to the person named on it, which is what makes it answerable afterwards.
- ### One door team, one app

  A pass is recognised at the gate by the same scanner that reads your tickets, and by the code itself rather than by anything your staff have to select. Your door team learns one thing, not two.
- ### Access beside your ticket sales

  Issue a pass from the event, the venue or the brand it's for. It carries the holder's name and email, and every scan is kept against it. You read access and ticket sales in one place instead of a spreadsheet beside the ticketing.

## How to set it up

- [Open Multi-Entry Passes](#step-1)
- [Create a type for each kind of access](#step-2)
- [Say how often each one works](#step-3)
- [Issue the passes](#step-4)
- [Send them out](#step-5)
- [Tell your door team what to expect](#step-6)

## What you need before you start

- You're an owner or an admin on the event or the brand.
- **Multi-Entry Passes** is in your menu. It appears once passes are turned on for your brand or your event -- ask us if you cannot see it.

1. ## Open Multi-Entry Passes

   Find it in the menu on the event you are working on. A brand can also hold passes that work across its events, on the same screen under the brand rather than the event.
2. ## Create a type for each kind of access

   Select **Manage types**, then **Create Pass Type**. Give it the name your team says out loud -- Crew, Artist, Production -- and set **Type** to **Member** for people working the event or **Season** for access that runs across a series.
3. ## Say how often each one works

   Set **Maximum number of uses per event** on the type, and set it on every type you create.

   Crew who come and go all day need a number that covers the whole day -- count the trips to the van and add some. Left empty, a pass of that type works once per event and the second scan is refused, which is the opposite of what an all-day pass is for.
4. ## Issue the passes

   Select **Create New Pass**, pick the type, and add people under **Enter Recipient** by first name, last name and email. For a crew list, switch to **Upload Recipients** and add a CSV of first name, last name and email address with no header row.
5. ## Send them out

   Each pass emails to the person it belongs to. **Send All** does the whole list at once, and **Notes** on a pass is where to record who approved it.
6. ## Tell your door team what to expect

   A pass scans in the same app as a ticket, and the app tells the two apart by the code. Your staff scan whatever is presented and read the answer on the screen.

   A pass is checked against the event, the brand or the venue it was issued for, and against its own limit. It is not restricted to one entrance, so a crew gate is a matter of who you hand a pass to rather than of what that gate will accept.

## Questions you might have

What is the difference between a pass and a guest-list ticket?:  A guest-list ticket is a ticket somebody did not pay for: one person, one entry. A pass is issued to a named person, can be used as many times as its type allows, and can be made to work across a run of events rather than one.

Can one pass work across every event we run?:  Yes. A pass is issued at brand, venue or event level, and one held at brand level works at the events under that brand -- which is what a season crew pass needs. A venue-level pass works at the events at that venue.

How do I stop a backstage pass being passed around?:  Set the uses per event on the type to the number you expect that role to use, so a pass meant for one entry can't be walked back out and used again. Every pass carries the name of the person it was issued to, so your door team has something to check it against.

Can I upload a crew list rather than adding people one at a time?:  Yes. **Upload Recipients** takes a CSV of first name, last name and email address with no header row, and issues a pass to each row.

Do my door team need a second app for passes?:  No. The same scanner reads a pass and a ticket and recognises which is which by the code itself, so your staff scan whatever is put in front of them.

## Where to go from here

- [What else you can do with Ticket Fairy](https://www.ticketfairy.com/event-ticketing/features)
- [How does event accreditation fit with your ticketing and CRM?](https://www.ticketfairy.com/guides/accreditation-with-ticketing-and-crm)
- [See which buyers come back to your events](https://www.ticketfairy.com/guides/browse-your-customer-list)
- [How do you stop a high-demand on-sale from falling over?](https://www.ticketfairy.com/guides/hold-up-a-high-demand-on-sale)
- [How do you manage many events on one ticketing platform?](https://www.ticketfairy.com/guides/run-many-events-on-one-platform)
- [How do you compare ticketing platforms on fees, payouts and customer data?](https://www.ticketfairy.com/guides/compare-ticketing-platforms-fees-payouts-and-data)
- [How do you build custom reports on ticket sales and buyer behaviour?](https://www.ticketfairy.com/guides/build-custom-reports-on-ticket-sales)
- [What marketing tools should a ticketing platform give you?](https://www.ticketfairy.com/guides/marketing-tools-a-ticketing-platform-should-have)
- [How do you manage tickets for a multi-day event?](https://www.ticketfairy.com/guides/manage-tickets-for-a-multi-day-event)
- [Every Ticket Fairy guide](https://www.ticketfairy.com/guides)

## Do this on your own event

Create your account, build your event, and follow these steps in your own dashboard. No sales call first.

  [Create a free account](https://manage.ticketfairy.com/welcome) [Book a demo](https://www.ticketfairy.com/event-ticketing/book-a-demo)

---

This page is on Ticket Fairy, a ticketing, marketing and operations platform for live events and the venues that host them: festivals, club nights, concerts, conferences and tours, and night clubs, beach clubs and concert venues. It grows revenue with fan rewards that turn an audience into a sales channel, and runs the money side with payments and payouts, Vault business banking, and working capital advanced against ticket sales. [How Ticket Fairy ticketing works](https://www.ticketfairy.com/event-ticketing) · [Ticket Fairy for AI assistants](https://www.ticketfairy.com/llms.txt)