Skip to main content

Overview

The User interface represents the authenticated user’s profile information derived from the ID token claims. It follows the OpenID Connect (OIDC) standard claims specification.

Type Definition

Properties

string
required
The unique identifier for the user (subject). This is the primary key that uniquely identifies the user across your Auth0 tenant.
string
The user’s full name in displayable form.
string
A casual name for the user, which may or may not be the same as their given name.
string
The user’s given name (first name).
string
The user’s family name (last name).
string
URL of the user’s profile picture. This is typically a URL pointing to an image.
string
The user’s email address.
boolean
Boolean indicating whether the user’s email address has been verified.
string
The unique identifier of the Auth0 organization the user belongs to. This field is only populated when the user authenticates through an organization.
any
Additional custom claims from the ID token can be accessed as properties. These can include custom user metadata, app metadata, or custom claims added via Auth0 Rules or Actions.

Usage Examples

Access User in Server Components (App Router)

Use User Hook in Client Components

Access Custom Claims

Filter User Claims with beforeSessionSaved

Control which claims are stored in the session:

Type-Safe User with Custom Claims

Create a typed interface for your custom claims:

Organization Login

When users log in through an Auth0 organization, the org_id field is automatically populated:
To require organization login:

OIDC Standard Claims

The User interface is based on the OpenID Connect Core 1.0 specification. Additional standard claims that may be present include:
  • updated_at - Time the user’s information was last updated
  • locale - User’s locale (e.g., “en-US”)
  • zoneinfo - User’s time zone (e.g., “America/New_York”)
  • phone_number - User’s phone number
  • phone_number_verified - Whether phone number is verified

See Also