> ## Documentation Index
> Fetch the complete documentation index at: https://docs.superoffice.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Known challenges with SuperID

> Known challenges with SuperID

We currently see some challenges where users are unable to sign in after migrating the tenant to SuperID.

## Multiple usernames

**Problem:**

A user might have multiple email addresses on their `person` record. Only 1 of these will become the new SuperID username. Sometimes migration picks the wrong email address.

**Solution:**

<Note>
  The admin can fix this by editing the **Username** field in the Admin client.
</Note>

Issues related to multiple associate records pointing to the new/old username apply (see next scenario).

## Users with multiple associate records in the same tenant

**Problem:**

A person might have multiple associate records in the customer database. We observe that often only 1 of these has a valid license.

<Warning>
  If the primary tenant does **not** have a license and you change the username, the user can no longer sign in.
</Warning>

**Solution:**

Must be resolved manually by R\&D services or Operations.

With SuperID, it is not permitted to create multiple users with identical usernames in the Admin client. Renaming a username also held by another user will create a new SuperID user.


## Related topics

- [Add a user](/en/developer-portal/partner/add-user.md)
- [OpenID Connect native apps](/en/api/authentication/online/sign-in-user/native-apps.md)
- [SuperID](/en/online/identity/superid/index.md)
- [Authorization Code flow](/en/api/authentication/online/sign-in-user/auth-code-flow.md)
- [Update SuperOffice username to match IdP username](/en/online/identity/superid/howto/map-idp-usernames.md)
- [SuperID terms and conditions](/en/online/identity/superid/terms-and-conditions.md)