Client: York Technical College
Ticket: 41339
Business Problem: YTC has particular scholarships that are limited to specific types of students. Although they understand the use of qualifications, they would prefer an access barrier to certain scholarship applications that allows only particular applicants to apply. The specific example given was a scholarship available to transfer students from a 4 year institution; they would like only those students to apply. In the past, they have given these students a "code" which allowed them to find and apply to this job (I presume through another system, not AW). As a workaround around, they will be using this code process in AW and qualifying applicants against it. However, they would rather have unqualified applicants just not apply.
Suggestion Solution: Allow opportunities to be hidden to the public, yet accessible to applicants with a specific link. This link could be distributed to applicants within AW via email or by administrators distributing it outside of AW. The client named this a "Invite Only".
Employee Name | Micco Fay |
Client Name "shard name" | yorktech |
User | System Admin |
Functional Unit | Portfolio |
This has been solved with flexible applications.
Conditional Applications could be used, but since these are not the same student sub-populations targeted in each scholarship, it would require multiple conditional applications that would be used for a scholarship or two each.
Since I wrote this request, I have discovered a possible workaround. It is possible to get a direct link to an opportunity accessible by applicants while setting the opportunity itself to "Not Visible" so it cannot be found in a search or even recommended to an applicant. The direct link still allows applicant to access it, and apply, even though marked as "Not Visible". In order to get this direct link, it requires some modifying of the URL of the internal administrator view of the opportunity. However, it would be far more intuitive a solution if we could just display this direct link in the opportunity as a read-only field users could copy. It would also be a convenient usability tool for administrators as they could click the link to quickly open up the opportunity from the applicant perspective to ensure things look the way they expect to the applicant. I've seen very similar features to this in other SAAS products.
If the goal is to limit the applicants to those that are qualified, and they still need to answer questions (so it cant be automatch), then a conditional application would achieve that. Is there a reason why they are unable to use conditional applications for this?