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

# Universal Portals

> Learn about Auth0 Universal Portals, hosted self-service Portals where end users manage their accounts and organization administrators manage their organizations.

> [!WARNING]
>
> **The Auth0 Universal Portals feature is in .**

Auth0 Universal Portals are hosted, self-service Portals. End users manage their own accounts, and organization administrators manage their own organizations, without you building, hosting, or maintaining the interface.

You can create each Portal from pre-built [components](https://auth0.com/docs/get-started/universal-components/universal-components-overview.md), and Auth0 hosts the Portal at a URL on your domain.

When a user opens a Portal from your application, the Portal calls the [My Account API](https://auth0.com/docs/manage-users/my-account-api.md) for personal settings, the [My Organization API](https://auth0.com/docs/manage-users/my-organization-api.md) for organization management, or both.

The visual editor with the Components panel open. The Form component is dragged from the panel and dropped onto the page, where it appears in a new block.

## Use cases

Universal Portals supports the following use cases:

### Consumer Portals

Give end users a page to manage their own account: update their profile, enroll [multi-factor authentication (MFA)](https://auth0.com/docs/secure/multi-factor-authentication.md) factors and passkeys, and review their security settings. A consumer Portal replaces the **My Account** page that you would otherwise build and host yourself, and uses the [My Account API](https://auth0.com/docs/manage-users/my-account-api.md).

![Consumer Portal example](https://mintlify.s3.us-west-1.amazonaws.com/auth0/docs/images/customize/portals/universal-portal-b2c-example.png)

### Business Portals

Give Organization administrators a page to manage their own Organization: edit Organization details and verify domains. A business Portal replaces the **My Organization** page that you would otherwise build and host yourself, and uses the [My Organization API](https://auth0.com/docs/manage-users/my-organization-api.md). To open a business Portal for a specific Organization, read [Access Portals](https://auth0.com/docs/customize/portals/access-portals.md#open-a-portal-in-an-organization-context).

![Business Portal example](https://mintlify.s3.us-west-1.amazonaws.com/auth0/docs/images/customize/portals/universal-portal-b2b-example.png)

### Combined Portals

A Portal can also provide a mix of both kinds of components. For example, one page can show MFA management next to Organization details. Add the components your users need, and give the portal application access to each resource server that they call.

## Key features

* Visual builder: arrange portal pages with pre-built components.
  * Identity components: use [Universal Components](https://auth0.com/docs/get-started/universal-components/universal-components-overview.md) for profile management, MFA and passkey enrollment, Organization details, and verified domains.
  * [Auth0 Forms](https://auth0.com/docs/customize/forms.md): collect information from end users, such as profile updates, policy acceptance, and communication preferences.
  * Layout components: add headings, rich text, sections, separators, and images.
* One application per Portal: every Portal is backed by an Auth0 [Regular Web Application](https://auth0.com/docs/get-started/auth0-overview/create-applications/regular-web-apps.md). To learn more, read [Configure an Application for Universal Portals](https://auth0.com/docs/customize/portals/configure-portal-application.md).
* Branding inheritance: Portals use your tenant's logo, colors, and fonts. In an [Organization](https://auth0.com/docs/manage-users/organizations.md) context, Portals use that Organization's branding.
* Hosted by Auth0: there is nothing to deploy, scale, or maintain.
* Secure token handling: the portal server keeps access tokens and refresh tokens, and the browser holds only a secure session cookie.
* Automatic MFA step-up: when Auth0 requires MFA for an operation, based on your tenant's policies and Actions, the Portal presents the challenge and retries the operation after the user completes it.

To see every component that Portals support, read [Portal Components Library Reference](https://auth0.com/docs/customize/portals/portal-components.md).

## How it works

A user who is signed in to your application opens the portal URL. The portal server signs the user in with single sign-on (Single Sign-On (SSO): Service that, after a user logs into one application, automatically logs them into other applications as well. Single Logout works similarly in reverse.) without a login prompt. Auth0 issues an access token (Access Token: Credential that can be used by an application to access an API. It informs the API that the bearer of the token has been authorized to access the API and perform specific actions specified by the scope that has been granted.) and a refresh token (Refresh Token: Special kind of token that can be used to obtain a renewed Access Token. It is useful for renewing expiring Access Tokens without forcing the user to log in again.), and the portal server stores them. When a component needs data, the portal server exchanges the refresh token for an access token for that API and makes the call on the user's behalf.

```mermaid theme={null}
flowchart LR
    user("User") --> app["Your application"]
    app -- "Opens the portal" --> portal["Portal server"]
    portal -- "Sign-in and tokens" --> auth0["Auth0"]
    portal -- "Calls with access tokens" --> rs["Resource servers"]
```

A portal session lasts up to 1 day and ends after 1 hour of inactivity.

To learn more, read [Universal Portals Architecture](https://auth0.com/docs/customize/portals/architecture.md).

## Supported resources and limitations

Portals support the following:

| Capability | Supported |
| - | - |
| Resource servers | Universal Components call the [My Account API](https://auth0.com/docs/manage-users/my-account-api.md) and the [My Organization API](https://auth0.com/docs/manage-users/my-organization-api.md). Auth0 Forms can call any API through Flows. |
| Components | Universal Components for MFA, [passkeys](https://auth0.com/docs/authenticate/database-connections/passkeys), Organization details, and verified domains; Auth0 Forms; headings, rich text, sections, separators, and images |
| Applications | Web applications and native applications |
| Organizations | Portals can open in the context of an organization |
| Domains | Custom domain or Auth0 domain |

Portals have the following limitations:

* Portals support a subset of Universal Components. To see which, read [Portal Components Library Reference](https://auth0.com/docs/customize/portals/portal-components.md).
* Custom code requires a custom domain.

## Universal Portals and Universal Components

Use Universal Portals to send users to a page that Auth0 hosts.

Use [Universal Components](https://auth0.com/docs/get-started/universal-components/universal-components-overview.md) to embed user account and Organization management into your application.

| | **Universal Components (embedded)** | **Universal Portals (hosted)** |
| - | - | - |
| Your responsibility | The application that contains the components | Page content and configuration |
| Authentication and tokens | You wire the components to Auth0 with the Auth0 SDKs | The Portal handles the authentication flows and stores the tokens securely in the backend |
| [Step-up authentication](https://auth0.com/docs/secure/multi-factor-authentication/step-up-authentication.md#add-step-up-authentication) | You wire the MFA step-up flow with the Auth0 SDKs, which gives you full control of the experience | The Portal handles the MFA step-up flow out of the box |
| End-user flow | Stays within your application | Opens a separate portal URL |
| When to choose | You want full control of the experience inside your application, with no redirect | You want to ship faster, and let Auth0 handle the maintenance and the security best practices of the full hosted experience |

## Next steps

> **[Universal Portals Quickstart](https://auth0.com/docs/customize/portals/quickstart.md)**
>
> Create your first Portal in minutes.

> **[Universal Portals Architecture](https://auth0.com/docs/customize/portals/architecture.md)**
>
> Learn how Portals sign users in, call APIs on their behalf, and manage sessions.

> **[Portal Components Library Reference](https://auth0.com/docs/customize/portals/portal-components.md)**
>
> Review available components, their resource servers, and scopes.