Skip to Content

The end-user portal

What your users can do for themselves in their account area, from profile and MFA to launching apps and requesting access.

Alongside the Admin Console, every signed-in user has their own account area. It is where they manage their profile, set up and maintain multi-factor authentication, review their sign-in activity and devices, launch the applications assigned to them, and request access to more. Most of these actions are self-service, which keeps routine requests, such as a lost authenticator or a forgotten password, off your help desk.

This page is an overview for administrators of what users can do on their own. The account area appears automatically for every user; nothing needs to be enabled for the basics. Some actions are gated by your directory and policy settings, as noted below.

Profile and personal data

From their personal-information page users can:

  • Update their basic profile: name, preferred language (limited to the languages you enable), country, and any custom profile attributes you have marked as user-editable.
  • Change their email address or username. When the account is not already at a strong assurance level, the user first confirms a one-time code sent to their current email. A new email address must then be verified before it takes effect.
  • Add or change their mobile number, when the directory manages a mobile attribute and can write it. Because the number is also the SMS second factor, it stays editable even when general profile editing is turned off. Changing the number removes any SMS second factor tied to it and requires the new number to be verified again; users can also remove a number they no longer use.
  • Set notification preferences, such as whether they are emailed about new sign-ins.

Which fields are editable depends on the directory: a synchronized directory can master certain fields upstream, in which case they are read-only here.

Security and sign-in

Users manage their own authentication from the security and MFA pages:

  • Enroll and manage second factors: passkeys, authenticator apps (TOTP), SMS, and email, depending on which factors you have enabled. Users can rename or delete an authenticator and enroll a new one.
  • Add a factor on another device by scanning a one-time QR code, so a phone can be enrolled from the computer they are signed in on.
  • Recovery codes: users receive one-time recovery codes so they can still sign in if they lose their factor. The first time a user enrolls a factor, recovery codes are offered automatically.
  • Change their password, which signs them out on every other device and in the applications, and set a recovery email used for account recovery.
  • Sign in with an email code, where their directory offers email code login: instead of typing a password they choose Email me a sign-in code and enter the six-digit code (or follow the sign-in link) from the message. The link only works in the browser the sign-in was started in.
  • Set an anti-phishing code, a personal phrase shown on genuine sign-in and email screens so users can recognize legitimate prompts.

For a directory that has passwords switched off, the password entries are absent from the portal: there is nothing to change and no password reset, because every sign-in uses an emailed code.

Sensitive changes, such as adding, editing, or removing a factor, require the user to have authenticated strongly and recently; the account area prompts for re-authentication when needed. An employee cannot remove their last remaining factor while multi-factor authentication is mandatory for them; customer and consumer users can, and are walked through enrolling a new one on their next sign-in that needs a factor.

If a user is completely locked out of their factors, an administrator resets their MFA. See Resetting a user's MFA.

Devices, activity, and privacy

  • Sign-in activity: users see their recent sign-ins and failed attempts, with an approximate location on a map (when geolocation is available).
  • Trusted browsers and devices: users can review the browsers they have signed in from and remove any they no longer use.
  • Sign out everywhere: a single action ends all of the user's active sessions across browsers.
  • Connected applications: on the privacy page users see the applications they have granted access to and can revoke that consent.
  • Delete their account: where self-service deletion applies, the user requests deletion, receives a confirmation link by email, and confirms.
  • Marketing communication: when marketing consent is asked for under Settings → Registration, consumer (B2C) users get a toggle on the privacy page to grant or withdraw that consent at any time, including where the sign-up form required it.

Applications

The app launcher shows every application assigned to the user that is set to appear there, so they have one place to open their tools. Each user can view their apps as a tile grid or a list, and sort them by name or by most recently visited.

Users can bookmark the apps they use most. A bookmarked app is marked with a filled star and moves into a Favorites group shown above the rest of the list, in either view. Bookmarking is a personal preference and does not affect who can access an app.

Users can also request access to applications you have made requestable; the request goes through your approval workflow if one applies. A user has at most one open request per application, so approvers are not notified twice.

Organizations

A user who belongs to more than one organization can switch their active organization from the account area. The switch applies to the current session and determines which organization's context and applications they see.

A user who is an administrator of an organization also has a scoped self-service portal for that organization: inviting and removing members, managing invitations, and authorizing applications for members, all limited to their own organization. This is described in Organization portal.

On this page