... | ... | @@ -22,13 +22,13 @@ inLeague distinguishes between the **Volunteer Pool** (users who indicated that |
|
|
|
|
|
## Affinity and AYSO Volunteer Management
|
|
|
|
|
|
### Important: Last Name & DOB
|
|
|
### Important: First Name, Last Name & DOB
|
|
|
|
|
|
The first time an inLeague user selects a volunteer role for themselves or someone in their family, inLeague will prompt the user to confirm their last name and to enter their date of birth.
|
|
|
The first time an inLeague user selects a volunteer role for themselves or someone in their family, inLeague will prompt the user to confirm their first name and last name and to enter their date of birth.
|
|
|
|
|
|
inLeague sends volunteer data to the [AYSO Association Management Platform](https://eayso.sportsaffinity.com/foundation/login.aspx), called Affinity (operated by Stack Sports). Affinity will look for an existing volunteer record from any AYSO region and assign the inLeague volunteer the appropriate AYSO ID, or else generate a new one.
|
|
|
|
|
|
The basis for AYSO ID is the volunteer's last name and date of birth. Once a volunteer has an AYSO ID, their name and date of birth can only be changed by a regional administrator with access to the Affinity platform. These changes are sent to inLeague and the volunteer record will be updated instantly. Nevertheless, the volunteer registration flow was designed to encourage users to input this information correctly up front.
|
|
|
The basis for AYSO ID is the volunteer's name (first + last, but not middle) and date of birth. Once a volunteer has an AYSO ID, their name and date of birth can only be changed by a regional administrator with access to the Affinity platform. These changes are sent to inLeague and the volunteer record will be updated instantly. Nevertheless, the volunteer registration flow was designed to encourage users to input this information correctly up front.
|
|
|
|
|
|
### AYSO Volunteer Registration and Electronic Legal Agreements
|
|
|
|
... | ... | |