Credential approvals
Working the queue: who gets on site, decided in advance rather than at the gate.
Everyone submitted for accreditation — by a supplier, an artist's tour manager, a guestlist request, a volunteer application or your own team — lands in one queue. Approving them is what turns a request into a pass.
The queue is at Accreditation › Cred Approvals.
What is in the queue
Only people waiting on a decision. Each row shows the name, the artist or organisation, the person's role, the pass type requested, the source it came from, and when it was submitted.
You can search by name, email, artist or pass type, and filter by source — touring party, guestlist or crew — or by artist tag.
Approving
Approving clears the person and issues a pass against their record. If a pass type has not been set yet, you set it as part of approving.
Approval is also the point at which the holder is emailed their pass: their QR code, a link to their ticket and an Add to Apple Wallet button. That email is on by default and can be turned off for a single person or for a whole batch. Anyone with no email address on file is skipped and flagged rather than failing silently.
Rejecting
Rejecting asks for a reason. It is optional, but it is the difference between a supplier resubmitting correctly and a supplier emailing you to ask what was wrong.
A rejection is not a dead end. The record stays, the details can be corrected, and it can come back through the queue.
Working in bulk
Select several rows and approve or reject them together. A bulk approval can set one pass type across the whole selection; a bulk rejection uses one shared reason.
Bulk is how a hundred-person supplier list gets cleared in a morning. It is also how a hundred people get the wrong pass type, so read the selection before you confirm.
Why it matters that this happens in advance
Only approved people appear on the collection desk. Someone still pending, or rejected, will not come up when they are searched for.
That is deliberate. The decision about whether someone gets site access is made by the right person, at a desk, with the request in front of them — not by whoever happens to be on the gate at seven in the morning with a queue building behind them.
Who can do this
The approvals queue is its own permission. Someone can be given approvals without being given allocations, pass types or collection. Suppliers never see it at all — they see their own crew and their own allocation, and nothing else.
Where to go next
- Passes and QR scanning — what gets issued once someone is approved
- Collection on site — running the desk