Accessibility Hub overview
How an access request moves from application to pass.
The Accessibility Hub brings every access request into one place: applications, supporting evidence, decisions, companion passes and the requirements your ops teams need to deliver. It's available in Festival workspaces.
How it works
Apply. The applicant fills in your public form (no login), ticks the provisions they need and uploads evidence.
Review. Your access team checks the evidence and approves or declines each requirement.
Decide. The application is approved, partially approved or denied, and the applicant is emailed.
Issue passes. Approval creates an accreditation pass for the applicant, and one for their PA once named.
Deliver. Approved requirements appear on the Requirements board for the teams on site.
The tabs
Dashboard shows demand and anything waiting on you.
Applications lists every application, searchable by name, reference or email.
Approvals shows only applications still waiting for a decision.
Requirements is the delivery list, grouped by team.
Companions covers PAs, their passes and ticket emails.
Forms is where you build and publish application forms.
Provisions is the list of things people can request.
Who can see what
Access to the hub comes from the Accessibility module permission. Supporting evidence is health data, so it sits behind a separate Accessibility → Evidence permission. Reviewers without it can still make decisions, but the Evidence tab stays locked.
Evidence is deleted 90 days after the festival ends, and every time a file is opened it's logged.
What the applicant sees
After submitting, applicants get an acknowledgement email with their reference (for example ACC-0012) and a private status link. From there they can check progress, read your decision message and upload any documents they didn't have at the time.