How to set up your account in Ticket Validation

Think of account-level setup as the skeleton everything else hangs on:

• Ticket sources label where tickets were sold or issued (partner, platform, internal).
• Ticket types describe access level (GA, VIP, …) and are always tied to one source.
• Locations are venues with a time zone. Event start and end times depend on this.
• Users can be admins, viewers, validators, or sellers, depending on what they need to do.

Events then combine a location, selected types, imported tickets, and validator assignments. If sources or types are wrong, every downstream step inherits that confusion.

In the sidebar, open Ticket sources. Create one row per distinct origin you need to report on or filter by.

Examples of sources:

• Resident Advisor
• Eventbrite
• Ticketmaster
• Partners
• Internal / organization tickets

A source is the origin of the ticket, not the type.

• Source = where the ticket comes from
• Type = what kind of ticket it is

Before you continue: Names should match how your team talks about sales channels so imports and dashboards stay readable.

Open Ticket types in the sidebar. Types define what access a ticket grants at the door.

Examples:

• Regular / General Admission
• VIP
• Backstage
• On Stage

When creating a ticket type, you must assign it to a source. This means:

• Each ticket type belongs to a specific source
• One source can have multiple ticket types

Example:

• Source: Resident Advisor. Types: Regular, VIP
• Source: Guestlist. Types: Regular, VIP, Backstage, Artist

At event level you will pick which types apply; imports and validation rules use this source and type pairing.

Open Users. Every person who needs access is created here.

Admins sign in to the web portal to manage sources, types, locations, events, imports, POS setup, and users.

Viewers sign in to the web portal with read-only access to event data, statistics, tickets, and POS reporting. You can allow all events or restrict the viewer to selected events.

Validators scan tickets at entry in the mobile validation app. Sellers use the same mobile app for POS ticket sales when POS is enabled.

• Create at least one admin besides the account owner if more than one person runs operations.
• Create viewers for partners, promoters, or stakeholders who need live visibility without edit access.
• Create validators and sellers early so devices can be logged in and tested before show day.
• When editing a user, password can be left blank to keep the current one.

Open Locations. Each location is a venue record with address fields and a time zone selector.

Examples:

• Club
• Festival site
• Outdoor venue

Reuse the same location for recurring nights at one venue; create separate locations when the address or time zone differs.

1. Create ticket sources, then ticket types linked to those sources.
2. Add locations with the correct time zone for each venue.
3. Create users: admins for setup, viewers for read-only event visibility, validators for scanning, and sellers for POS.
4. Proceed to Set up an event. Pick the location, attach types, import tickets, and assign validators.

• Cannot create a ticket type: ensure at least one source exists and select it when saving the type.
• Event times look wrong: open the location and confirm the time zone; edit the location rather than guessing offsets on the event.
• Validator cannot log in: confirm the user is type Validator, credentials are correct, and the mobile app is the validation app (not the web URL).
• Admin cannot see menus: account-level objects are under Ticket sources, Ticket types, Locations, and Users in the sidebar. Use an Admin user, not a Viewer, Validator, or Seller account, for setup work in the browser.