Single sign-on (SSO)
Single sign-on (SSO) allows your staff to log into Parent Events using their school credentials through your identity provider (IdP), such as Azure AD, Google Workspace, or a custom identity provider that supports SAML 2.0.
Once set up, staff can either:
- log in using the "Sign in with SSO" option on the login page and entering their email address.
- use a dedicated URL for your school that sends them directly to your identity provider.
After they sign into your identity provider, they'll be sent back to Parent Events. Depending on your preferred configuration, staff who don't already have a Parent Events account will be created one.
Before we begin
- Single sign-on provisioning is a technical process that will involve your IT staff. It's a good idea for them to read this page as well.
- Parent Events can provision a new staff account if the email address doesn't already exist.
- The first name, last name, classroom, and email address fields for the staff member are extracted from the SAML attributes received by your identity provider.
- The fields of these values can be customised if required.
- We strongly recommend that you only enabled once you've confirmed your identity provider configuration only allows access to certain groups, such as a dedicated group or OU for access to Parent Events. You don't want to find students signing in and acting as staff.
- A primary domain name will need to be chosen to match your staff's email addresses with your school and identity provider. Using multiple domains with SSO is not supported.
- Single sign-on can be enforced so that staff will always sign in with your identity provider, rather than through Parent Events.
- This option can be enabled once the integration process has been completed and confirmed working.
Setting up single sign-on
We strongly recommend having your IT professional provide this information.
In the Single Sign-on section within the Settings page, fill out the form containing the required fields needed for us to start the provisioning process.
We'll then be in touch once we've validated the information provided and have started the integration process, and you'll be able to specify anything custom such as the names of attribute fields for user provisioning.
You'll be able to test the single sign-on process is working correctly before enabling options to enforce its usage amongst your staff.
Need a hand?
If you're unsure that you'll be able to set up single sign-on for your school, please feel free to reach out to our support team and we'll do our best to help.
We cannot guarantee that all identity providers will be supported or we'll be able to provide specific integration instructions depending on your user management processes.