Resources
An Admitted user who confirmed their university enrollment. Undergrads confirm via deposit payment.
Bravura process
Data Structure
- This is an active affiliation role. Users within the validity window have active birthright entitlements (e.g. LDAP, AD, Google).
- Entry into Confirmed is one way from Admitted.
- Users remain in Confirmed until the start of their first term, at which time they become a Student.
- A lapsing Student transitions to Limited Student, not back to Confirmed.
- The Confirmed role may overlap a Student role. This occurs in two situations:
- Students are given access seven days prior to the term. In Bravura, this will appear as the Student start date preceding the Confirmed end date by seven days.
- A former undergrad applying to graduate school may also contain Confirmed. Their undergraduate Student role will still display until starting Graduate school.
- Services reserved for registered Students will not be permitted as Confirmed.
- Confirmed users have an Active Directory OU=Confirmed and are in the Confirmed AD group.
- Users in this role are in the Managed/Student Google OU. This is the same OU as Students and, unlike Admitted, allows full Google suite access.
Activation
- An Admitted user becomes Confirmed after completing the necessary procedures to verify their expectation to attend App State.
- Although the Confirmed status allows class registration, the Banner Self Service entitlement is not managed by Bravura or the AD group appointment. Banner self-service access to registration is based on an internal Banner query (e.g. SARADAP, SARAPPD, SGBSTDN).
Leaver:
Unless they change their intended term, Confirmed users failing registration will be relegated to the Inactive Student role affiliation. If they indicate they have no plan to register, they will flagged with a withdrawal code and eventually cease reported to Bravura.