Skip to main content

How does uConnect handle duplicate accounts when a student has multiple email addresses (NetID, alias, personal)?

Learn more about how your uConnect platform handles duplicate accounts regarding student data, subscriber lists, and SIS.

Written by Christina Butler
Updated this week

uConnect is designed to avoid creating unnecessary duplicate accounts, even when a single person may use different email addresses over time.

1. What fields does uConnect use to recognize a returning user?

When someone logs in (via SSO/SAML or using local credentials), uConnect checks:

  • Username / unique ID (often a NetID, NUID, or similar), and

  • Email address

uConnect will treat someone as the same person if either:

  • The username/unique ID matches an existing account, or

  • The email address matches an existing account

2. What happens if a student has multiple institutional emails (NetID vs alias)?

Common scenario:

If a student logs in with a new institutional email but either:

  • The username/unique ID is the same as an existing account, or

  • The new email matches an existing account

then uConnect will link that login to the existing account, rather than creating a duplicate.

If both the username/ID and email are different from anything we’ve seen before, uConnect will create a new account.

3. What about personal emails?

If a student uses a personal email that is not already associated with their existing uConnect account, and:

  • The username/ID is also different or not provided, then

  • uConnect will create a separate account for that login.

If you want to ensure personal emails are not creating separate accounts, we recommend:

  • Using a consistent unique identifier (e.g., student ID/NetID/NUID) across all authentication flows that should map to the same person, and/or

  • Avoiding personal-email-based logins for populations that should be tied to institutional identities and required SSO login for students.

4. How does uConnect handle email or username changes over time?

  • If only the email changes (and the username/ID stays the same), uConnect will treat the login as the same account and can update attributes accordingly.

  • If only the username/ID changes (and the email stays the same), we still match on the email, so it is treated as the same account.

  • If both the email and the username/ID change (for example, a student changes their username and starts using a different email that doesn’t match what we have on file), uConnect will treat this as a new user and create a new account.

In that edge case, if you need the records combined, our team can assist with a manual merge.

5. How can we minimize duplicate accounts for our students?

To keep the experience seamless and avoid duplicates:

  • Standardize on a single, stable identifier (like student ID/NUID/NetID) in:

    • Your SSO/SAML configuration

    • Any automated user/subscriber feeds

  • Ensure that identifier is sent consistently for the same person, regardless of which institutional email they use.

  • If you anticipate frequent name or email changes (e.g., after name changes or role changes), design your IdP behavior so that either the ID stays stable or the email remains consistent to preserve matching.

As always if you have further questions, please reach out to our support team!

Did this answer your question?