Form Field Setting: Required for Guardian and Required for Admin

Learn how the existing "Required" and "Required Admin" field settings have been updated for clarity and to operate separately.

Prior to the Enroll 2.5 update, the "Required" form field setting was forcing the field to be required for both guardians and admins.  With the 2.5 release, the two required settings are now distinct from each other and can be set separately as seen below.

Fields that were using the "Required" setting will now be set as both: Required for Guardian and Required for Admin to match the current behavior of your field setting.

• Please review your field settings within each step and adjust the Required settings as desired.
• If using Recommendations in your form(s), all recommendation fields were set to “Required” by default so both Required for Guardian and Required for Admin will be assigned
• If using Events in your form(s), all event fields were set to “Required” by default so both Required for Guardian and Required for Admin will be assigned
• If an admin-only step currently has fields set to “Required”, they will now be set to both Required for Guardian and Required for Admin. The admin-only step logic will override the guardian requirement on the field so the field will behave as it did prior to the change.