Released: May 21, 2026
Internal users (staff and faculty) can now be assigned identity values beyond email, with two new types: School ID and SSO ID. Internal SSO can now be configured to match on either value instead of email, for institutions whose identity provider sends a non-email identifier. Identities are managed directly from the internal user's Basic Info section, where they can be added, updated, or removed.
šØ Important: Each internal SSO configuration matches on one field: Email (default), School ID, or SSO ID. Adding a School ID or SSO ID to a user's profile doesn't turn on matching by that field. Element451 sets the matching field. To change it, contact Support. See Internal SSO User Matching.
Two New Identity Types for Internal Users: Internal users can now store a School ID and an SSO ID. Previously, internal users had no identity values and could only be matched on email.
āSSO Matching by Identity: Internal SSO can be configured to match on School ID or SSO ID instead of email. Each configuration matches on one field.
āManage Identities from Basic Info: Users with the Administer Internal Users permission can add, update, or delete School ID and SSO ID values directly in the Basic Info section of the internal user profile.
āUniqueness Enforced: Each identity value must be unique across internal users; duplicates are rejected when attempting to save changes.
Institutions whose SSO providers send a non-email identifier no longer have to force email as the matching field for internal user logins. IT teams can ask Element451 to switch Internal SSO matching to the School ID or SSO ID their IdP already issues, removing a common blocker during SSO rollouts.





