Application-Linked Unique Access Codes for Subsidised Event Tickets

Background

We run a student subsidy program that helps eligible students access discounted tickets for selected events. As part of this process, students are required to apply for the subsidy so we can assess eligibility, approve requests, and track the distribution of financial assistance.

Current Workflow

Our ideal process would be:

A student submits a subsidy application through Rubric.
We review the application against our eligibility criteria.
If approved, the student automatically receives a unique access code in their approval email.
The student enters this code when accessing the event registration page.
The code unlocks a hidden discounted ticket type that is not visible to the general public.
The student purchases the subsidised ticket.

Why Existing Options Don't Meet Our Needs

I have reviewed the existing feature request regarding password-protected ticket access. While this is a step in the right direction, it does not fully address our use case.

A shared password creates the risk of being distributed between students. Once a password is shared, students who have not applied for or been approved for the subsidy could potentially access the discounted ticket option. This would bypass our assessment process and significantly reduce our ability to track who has requested and received financial assistance.

Similarly, using a private event link creates the same issue. Private links can be forwarded or shared, allowing students to access subsidised tickets without submitting an application through Rubric.

Requested Enhancement

We would like the ability to generate unique, application-linked access codes that can be issued only to approved applicants.

Key requirements:

Students must first submit an application through Rubric.
Approval of the application triggers the distribution of a unique code.
The code unlocks access to a hidden discounted ticket type.
Discounted tickets remain invisible to the public unless a valid code is entered.
Codes can be issued individually to specific students.
Administrators can track which code was issued to which applicant.
Codes can be configured as single-use or limited-use, depending on the program requirements.

Benefits

This feature would:

Ensure subsidised tickets are only accessed by approved applicants.
Prevent unauthorised access through shared links or common passwords.
Maintain accurate records of subsidy applications and approvals.
Improve reporting and auditing of financial assistance programs.
Create a seamless workflow between applications and event registrations within Rubric.

For organisations like ours that provide targeted financial support, this functionality would create a secure and scalable way to manage subsidised event access while maintaining accountability and accurate data collection.