> ## Documentation Index > Fetch the complete documentation index at: https://docs.portalhq.io/llms.txt > Use this file to discover all available pages before exploring further. # End users > Review the users who have signed in through Portal-managed authentication and reset their two-factor enrollment. An **end user** is the record Portal keeps for someone who signs in through Portal-managed authentication. Portal creates one the first time an email address signs in to an environment, and reuses it on every later sign-in, whichever method they use. Each end user maps to exactly one Portal client, which is what owns their wallet. That mapping is why a returning user keeps their wallet instead of getting a new one. End users are keyed on email address within an environment. The same person signing in to your Development and Production environments is two separate end users with two separate wallets, which is expected. A person arriving with two different email addresses is also two end users, so decide how you want that to behave if you offer several sign-in methods. ## Browse end users Step 1: Click **End Users** in the left sidebar, under Authentication. Step 2: Select the environment whose users you want to see. End Users list showing email, end user ID, auth methods, client ID, and created at columns with a search box above The list shows: | Column | Description | | ---------------- | ------------------------------------------------------------------------------------------------------- | | **Email** | The address the user signed in with. Sortable. | | **End User ID** | Portal's identifier for the end user, matching the `endUserId` returned by the validation endpoints. | | **Auth Methods** | Every method this user has signed in with. A user who has used both Google and a magic link shows both. | | **Client ID** | The Portal client created for this user. | | **Created At** | When the end user first signed in. Sortable. | Search by email address or end user ID to find a specific user. ## Inspect an end user Click a row to open the detail view, which is organized into three cards. End user detail view with the End User, Wallet, and TOTP cards * **End User** shows the end user ID, when they were created, their email, and the auth methods they have used. * **Wallet** shows the client ID associated with the user. * **TOTP** shows whether they are enrolled in two-factor authentication, and lets you reset it. This is not shown if TOTP is not enabled. ## Reset two-factor enrollment If a user loses the device holding their authenticator app, reset their enrollment. Step 1: Open the user from **Authentication > End Users**. Step 2: In the **TOTP** card, click **Reset TOTP** and confirm. The card switches from **Enrolled** to **Not enrolled**. On their next sign-in Portal returns a fresh `totpLink`, so your app shows the QR code again and they set up a new authenticator. See [Two-factor authentication](/resources/authentication/two-factor-authentication). Resetting enrollment removes the second factor until the user sets it up again, so the next sign-in is protected by their email or OAuth account alone. Confirm you are talking to the real account owner before resetting. The reset option only appears for users who are currently enrolled. ## Next steps How the TOTP flow works from your app's side. Back to how Portal-managed authentication fits together.