**Warning:** Per the [OAuth 2.0 Specification](https://tools.ietf.org/html/rfc6749#section-3.1.2), Auth0 removes everything after the hash and does *not* honor any fragments. | | `scope` | Specifies the [scopes](/docs/get-started/apis/scopes) for which you want to request authorization, which dictate which claims (or user attributes) you want returned. These must be separated by a space. To get an ID Token in the response, you need to specify a scope of at least `openid`. If you want to return the user's full profile, you can request `openid profile`. You can request any of the [standard OpenID Connect (OIDC) scopes](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims) about users, such as `email`, or [custom claims](/docs/secure/tokens/json-web-tokens/json-web-token-claims#custom-claims) conforming to a [namespaced format](/docs/secure/tokens/json-web-tokens/create-custom-claims). Include `offline_access` to get a [Refresh Token](/docs/glossary?term=Refresh+Token) (make sure that the **Allow Offline Access** field is enabled in the [Application Settings](https://manage.auth0.com/#/applications)). | | `state` | (recommended) An opaque arbitrary alphanumeric string your app adds to the initial request that Auth0 includes when redirecting back to your application. To see how to use this value to prevent cross-site request forgery (CSRF) attacks, see [Mitigate CSRF Attacks With State Parameters](/docs/secure/attack-protection/state-parameters). | | `connection` | (optional) Forces the user to sign in with a specific connection. For example, you can pass a value of `github` to send the user directly to GitHub to log in with their GitHub account. When not specified, the user sees the Auth0 Lock screen with all configured connections. You can see a list of your configured connections on the **Connections** tab of your application. | | `organization` | (optional) ID of the organization to use when authenticating a user. When not provided, if your application is configured to **Display Organization Prompt**, the user will be able to enter the organization name when authenticating. | | `invitation` | (optional) Ticket ID of the organization invitation. When [inviting a member to an Organization](/docs/manage-users/organizations/configure-organizations/invite-members), your application should handle invitation acceptance by forwarding the `invitation` and `organization` key-value pairs when the user accepts the invitation. | As an example, your HTML snippet for your authorization URL when adding login to your app might look like:
**Warning:** Per the [OAuth 2.0 Specification](https://tools.ietf.org/html/rfc6749#section-3.1.2), Auth0 removes everything after the hash and does *not* honor any fragments. | | `scope` | The [scopes](/docs/get-started/apis/scopes) for which you want to request authorization. These must be separated by a space. You can request any of the [standard OpenID Connect (OIDC) scopes](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims) about users, such as `profile` and `email`, [custom claims](/docs/secure/tokens/json-web-tokens/json-web-token-claims#custom-claims) conforming to a [namespaced format](/docs/secure/tokens/json-web-tokens/create-custom-claims), or any scopes supported by the target API (e.g., `read:contacts`). Include `offline_access` to get a [Refresh Token](/docs/glossary?term=Refresh+Token) (make sure that the **Allow Offline Access** field is enabled in the [Application Settings](https://manage.auth0.com/#/apis)). | | `audience` | The unique identifier of the API your mobile app wants to access. Use the **Identifier** value on the [Settings](https://manage.auth0.com/#/apis) tab for the API you created as part of the prerequisites for this tutorial. | | `state` | (recommended) An opaque arbitrary alphanumeric string your app adds to the initial request that Auth0 includes when redirecting back to your application. To see how to use this value to prevent cross-site request forgery (CSRF) attacks, see [Mitigate CSRF Attacks With State Parameters](/docs/secure/attack-protection/state-parameters). | | `organization` | (optional) ID of the organization to use when authenticating a user. When not provided, if your application is configured to **Display Organization Prompt**, the user will be able to enter the organization name when authenticating. | | `invitation` | (optional) Ticket ID of the organization invitation. When [inviting a member to an Organization](/docs/manage-users/organizations/configure-organizations/invite-members), your application should handle invitation acceptance by forwarding the `invitation` and `organization` key-value pairs when the user accepts the invitation. | As an example, your HTML snippet for your authorization URL when calling an API might look like:
**Warning:** Per the [OAuth 2.0 Specification](https://tools.ietf.org/html/rfc6749#section-3.1.2), Auth0 removes everything after the hash and does *not* honor any fragments. | | `scope` | Specifies the [scopes](/docs/get-started/apis/scopes) for which you want to request authorization, which dictate which claims (or user attributes) you want returned. These must be separated by a space. To get an ID Token in the response, you need to specify a scope of at least `openid`. If you want to return the user's full profile, you can request `openid profile`. You can request any of the [standard OpenID Connect (OIDC) scopes](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims) about users, such as `email`, or [custom claims](/docs/secure/tokens/json-web-tokens/json-web-token-claims#custom-claims) conforming to a [namespaced format](/docs/secure/tokens/json-web-tokens/create-custom-claims). Include `offline_access` to get a [Refresh Token](/docs/glossary?term=Refresh+Token) (make sure that the **Allow Offline Access** field is enabled in the [Application Settings](https://manage.auth0.com/#/applications)). | | `state` | (recommended) An opaque arbitrary alphanumeric string your app adds to the initial request that Auth0 includes when redirecting back to your application. To see how to use this value to prevent cross-site request forgery (CSRF) attacks, see [Mitigate CSRF Attacks With State Parameters](/docs/secure/attack-protection/state-parameters). | | `connection` | (optional) Forces the user to sign in with a specific connection. For example, you can pass a value of `github` to send the user directly to GitHub to log in with their GitHub account. When not specified, the user sees the Auth0 Lock screen with all configured connections. You can see a list of your configured connections on the **Connections** tab of your application. | | `organization` | (optional) ID of the organization to use when authenticating a user. When not provided, if your application is configured to **Display Organization Prompt**, the user will be able to enter the organization name when authenticating. | | `invitation` | (optional) Ticket ID of the organization invitation. When [inviting a member to an Organization](/docs/manage-users/organizations/configure-organizations/invite-members), your application should handle invitation acceptance by forwarding the `invitation` and `organization` key-value pairs when the user accepts the invitation. | | `login_hint` | (optional) Populates the username/email field for the login or signup page when redirecting to Auth0. Supported by the Universal Login experience. | As an example, your HTML snippet for your authorization URL when adding login to your app might look like:
**Warning:** Per the [OAuth 2.0 Specification](https://tools.ietf.org/html/rfc6749#section-3.1.2), Auth0 removes everything after the hash and does *not* honor any fragments. | | `scope` | Specifies the [scopes](/docs/get-started/apis/scopes) for which you want to request authorization, which dictate which claims (or user attributes) you want returned. These must be separated by a space. You can request any of the [standard OpenID Connect (OIDC) scopes](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims) about users, such as `profile` or `email`, [custom claims](/docs/secure/tokens/json-web-tokens/json-web-token-claims#custom-claims) conforming to a [namespaced format](/docs/secure/tokens/json-web-tokens/create-custom-claims), or any scopes supported by the target API (e.g., `read:contacts`). Include `offline_access` to get a [Refresh Token](/docs/glossary?term=Refresh+Token) (make sure that the **Allow Offline Access** field is enabled in the [Application Settings](https://manage.auth0.com/#/applications)). | | `audience` | The unique identifier of the API your web app wants to access. Use the **Identifier** value on the [Settings](https://manage.auth0.com/#/apis) tab for the API you created as part of the prerequisites for this tutorial. | | `state` | (recommended) An opaque arbitrary alphanumeric string your app adds to the initial request that Auth0 includes when redirecting back to your application. To see how to use this value to prevent cross-site request forgery (CSRF) attacks, see [Mitigate CSRF Attacks With State Parameters](/docs/secure/attack-protection/state-parameters). | | `organization` | (optional) ID of the organization to use when authenticating a user. When not provided, if your application is configured to **Display Organization Prompt**, the user will be able to enter the organization name when authenticating. | | `invitation` | (optional) Ticket ID of the organization invitation. When [inviting a member to an Organization](/docs/manage-users/organizations/configure-organizations/invite-members), your application should handle invitation acceptance by forwarding the `invitation` and `organization` key-value pairs when the user accepts the invitation. | As an example, your HTML snippet for your authorization URL when adding login to your app might look like:
The scope can optionally include `offline_access` to request a refresh token. However, for one-time authorization of a transaction with the CIBA Flow, a refresh token is not needed and does not have any meaning in this context. | | `user_id` | User ID for the authorizing user that is passed within the `login_hint` structure. If `iss_sub` format is used, then the user ID is passed within the `sub` claim.
The user ID may have a different format depending on the external provider. | | `requested_expiry` | The maximum duration, in seconds, for which the CIBA session should be valid. The CIBA flow's requested expiry is between 1 and 259200 seconds (72 hours), and it defaults to 300 seconds. Include the `requested_expiry` parameter to set a custom expiry for the CIBA flow.
The `requested_expiry` parameter helps determine which notification channel CIBA uses:
- If you set your `requested_expiry` to a value of 300 or lower in seconds, CIBA uses the mobile push notification channel if enabled. If you have not configured MFA for your tenant, the CIBA request fails.
- If you set your `requested_expiry` to a value between 301 to 259200 seconds (72 hours), CIBA uses the email notification channel if enabled.
The scope can optionally include `offline_access` to request a refresh token. However, for one-time authorization of a transaction with the CIBA Flow, a refresh token is not needed and does not have any meaning in this context. | | `user_id` | User ID for the authorizing user that is passed within the `login_hint` structure. If `iss_sub` format is used, then the user ID is passed within the `sub` claim.
The user ID may have a different format depending on the external provider. | | `requested_expiry` | The maximum duration, in seconds, for which the CIBA session should be valid. The CIBA flow's requested expiry is between 1 and 259200 seconds (72 hours), and it defaults to 300 seconds. Include the `requested_expiry` parameter to set a custom expiry for the CIBA flow.
The `requested_expiry` parameter helps determine which notification channel CIBA uses:
- If you set your `requested_expiry` to a value of 300 or lower in seconds, CIBA uses the mobile push notification channel if enabled. If you have not configured MFA for your tenant, the CIBA request fails.
- If you set your `requested_expiry` to a value between 301 to 259200 seconds (72 hours), CIBA uses the email notification channel if enabled.
**Example**: `login_hint={"format": "iss_sub", "iss": "https://{YOUR_DOMAIN}.auth0.com/", "sub":"{USER_ID"}` | | `client_id` | Client application identifier. | | `client_secret` | Client authentication method used for user authentication with CIBA, such as Client Secret, Private Key JWT, or mTLS Authentication. If you're using Private Key JWT or mTLS, you don't need to include the client secret. | | `scope` | Must include `openid`.
The scope can optionally include `offline_access` to request a refresh token. However, for one-time authorization of a transaction with the CIBA Flow, a refresh token is not needed and does not have any meaning in this context. | | `user_id` | User ID for the authorizing user that is passed within the `login_hint` structure. If `iss_sub` format is used, then the user ID is passed within the `sub` claim.
**Example**: `login_hint={"format": "iss_sub", "iss": "https://{YOUR_DOMAIN}.auth0.com/", "sub":"{USER_ID}"}`
The user ID may have a different format depending on the external provider. | | `requested_expiry` | The CIBA flow's requested expiry is between 1 and 259200 (72 hours) seconds, and it defaults to 300 seconds. Include the `requested_expiry` parameter to set a custom expiry for the CIBA flow.
The `requested_expiry` parameter helps determine which notification channel CIBA uses:
- If you set your `requested_expiry` to a value of 300 or lower in seconds, CIBA uses the mobile push notification channel if enabled. If you have not configured MFA for your tenant, the CIBA request fails.
- If you set your `requested_expiry` to a value between 301 to 259200 seconds, CIBA uses the email notification channel if enabled.
**Warning:** Per the [OAuth 2.0 Specification](https://tools.ietf.org/html/rfc6749#section-3.1.2), Auth0 removes everything after the hash and does *not* honor any fragments. | | `scope` | Specifies the [scopes](/docs/get-started/apis/scopes) for which you want to request authorization, which dictate which claims (or user attributes) you want returned. These must be separated by a space. You can request any of the [standard OpenID Connect (OIDC) scopes](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims) about users, such as `profile` or `email`, [custom claims](/docs/secure/tokens/json-web-tokens/json-web-token-claims#custom-claims) conforming to a [namespaced format](/docs/secure/tokens/json-web-tokens/create-custom-claims), or any scopes supported by the target API (e.g., `read:contacts`). Include `offline_access` to get a [Refresh Token](/docs/glossary?term=Refresh+Token) (make sure that the **Allow Offline Access** field is enabled in the [Application Settings](https://manage.auth0.com/#/applications)). | | `audience` | The unique identifier of the API your application wants to access. Use the **Identifier** value on the [Settings](https://manage.auth0.com/#/apis) tab for the API you created as part of the prerequisites for this tutorial. | | `state` | (recommended) An opaque arbitrary alphanumeric string your app adds to the initial request that Auth0 includes when redirecting back to your application. To see how to use this value to prevent cross-site request forgery (CSRF) attacks, see [Mitigate CSRF Attacks With State Parameters](/docs/secure/attack-protection/state-parameters). | | `nonce` | A cryptographically random string that your app adds to the initial request and Auth0 includes inside the ID Token, [used to prevent token replay attacks](/docs/get-started/authentication-and-authorization-flow/implicit-flow-with-form-post/mitigate-replay-attacks-when-using-the-implicit-flow). | | `organization` | (optional) ID of the organization to use when authenticating a user. When not provided, if your application is configured to **Display Organization Prompt**, the user will be able to enter the organization name when authenticating. | | `invitation` | (optional) Ticket ID of the organization invitation. When [inviting a member to an Organization](/docs/manage-users/organizations/configure-organizations/invite-members), your application should handle invitation acceptance by forwarding the `invitation` and `organization` key-value pairs when the user accepts the invitation. | As an example, your HTML snippet for your authorization URL when adding login to your app might look like:
**Warning:** Per the [OAuth 2.0 Specification](https://tools.ietf.org/html/rfc6749#section-3.1.2), Auth0 removes everything after the hash and does *not* honor any fragments. | | `scope` | Specifies the [scopes](/docs/get-started/apis/scopes) for which you want to request authorization, which dictate which claims (or user attributes) you want returned. These must be separated by a space. You can request any of the [standard OpenID Connect (OIDC) scopes](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims) about users, such as `profile` and `email`, [custom claims](/docs/secure/tokens/json-web-tokens/json-web-token-claims#custom-claims) conforming to a [namespaced format](/docs/secure/tokens/json-web-tokens/create-custom-claims), or any scopes supported by the target API (for example, `read:contacts`). | | `state` | (recommended) An opaque arbitrary alphanumeric string that your app adds to the initial request and Auth0 includes when redirecting back to your application. To see how to use this value to prevent cross-site request forgery (CSRF) attacks, see [Mitigate CSRF Attacks With State Parameters](/docs/secure/attack-protection/state-parameters). | | `nonce` | (required for `response_type` containing `id_token token`, otherwise recommended) A cryptographically random string that your app adds to the initial request and Auth0 includes inside the ID Token, [used to prevent token replay attacks](/docs/get-started/authentication-and-authorization-flow/implicit-flow-with-form-post/mitigate-replay-attacks-when-using-the-implicit-flow). | | `connection` | (optional) Forces the user to sign in with a specific connection. For example, you can pass a value of `github` to send the user directly to GitHub to log in with their GitHub account. When not specified, the user sees the Auth0 Lock screen with all configured connections. You can see a list of your configured connections on the **Connections** tab of your application. | | `organization` | (optional) ID of the organization to use when authenticating a user. When not provided, if your application is configured to **Display Organization Prompt**, the user will be able to enter the organization name when authenticating. | | `invitation` | (optional) Ticket ID of the organization invitation. When [inviting a member to an Organization](/docs/manage-users/organizations/configure-organizations/invite-members), your application should handle invitation acceptance by forwarding the `invitation` and `organization` key-value pairs when the user accepts the invitation. | As an example, your HTML snippet for your authorization URL when adding login to your app might look like:
The following namespaces are reserved and cannot be used:
- `http://auth0.com`
- `https://auth0.com`
- `http://okta.com`
- `https://okta.com`
- `urn:ietf`
- `urn:auth0`
- `urn:okta`
Other alternatives are also available as explained in [Auth0 Authentication API reference docs](https://auth0.com/docs/api/authentication#authentication-methods).
Note Custom Token Exchange can be used by public Applications. Make sure to read [Attack Protection](#attack-protection) in that case. | | `audience` | The API identifier defined in Auth0. The default tenant audience will be used when not present, as configured in [Tenant Settings](/docs/get-started/tenant-settings). | | `scope` | (Optional) The OAuth2 scope parameter. | | `organization` | (Optional) The organization identifier you want the request to be associated with. Alternatively, you can specify an organization name if [Use Organization Names in Authentication API](/docs/manage-users/organizations/configure-organizations/use-org-name-authentication-api) is allowed for your tenant. To learn more about how the request is processed, read about the [api.authentication.setOrganization() API method](/docs/customize/actions/explore-triggers/signup-and-login-triggers/custom-token-exchange-trigger/custom-token-exchange-api-object#api-authentication-setorganization-organization). | | `actor_token` | (Optional) A token identifying the actor or the principal performing delegation on behalf of the subject user. Must be provided together with `actor_token_type`. | | `actor_token_type` | (Optional) The type of the actor token. Must be provided together with `actor_token`. For Auth0 ID tokens, use `urn:ietf:params:oauth:token-type:id_token` for automatic server-side validation. For other values, follow the same namespace restrictions as `subject_token_type`. |
Profile
{{ profile?.nickname }}
{{ profile | json }}
"Find applications with 'api' in their name."
"What applications do I have in my Auth0 tenant?" | | `auth0_get_application ` | Get details about a specific Auth0 application. | "Show me details for the application called 'Customer Portal'."
"Get information about my application with client ID ."
"What are the callback URLs for my 'Mobile App'?" | | `auth0_create_application ` | Create a new Auth0 application. | "Create a new single-page application called 'Analytics Dashboard'."
"Set up a new native mobile app called 'iOS Client'."
"Create a machine-to-machine application for our background service." | | `auth0_update_application` | Update an existing Auth0 application. | "Update the callback URLs for my 'Web App' to include `https://staging.example.com/callback`."
"Change the logout URL for the 'Customer Portal'."
"Add development environment metadata to my 'Admin Dashboard' application." | | `auth0_create_application_grant` | Create a client grant authorizing an application to access an API with specified scopes. | "Authorize my 'Background Service' app to access the 'Inventory API'."
"Grant my machine-to-machine app access to the user management API."
"Set up client credentials access for my backend service to the payments API." | ## Resource server (API) management | Tool | Description | Natural language examples | | - | - | - | | `auth0_list_resource_servers` | List all resource servers (APIs) in the Auth0 tenant. | "Show me all the APIs in my Auth0 tenant."
"List my resource servers."
"What APIs have I configured in Auth0?" | | `auth0_get_resource_server` | Get details about a specific Auth0 resource server. | "Show me details for the 'User API'."
"What scopes are defined for my 'Payment API'?"
"Get information about the resource server with identifier `https://api.example.com`." | | `auth0_create_resource_server` | Create a new Auth0 resource server (API). | "Create a new API called 'Inventory API' with read and write scopes."
"Set up a resource server for our customer data API."
"Create an API with the identifier `https://orders.example.com`." | | `auth0_update_resource_server` | Update an existing Auth0 resource server. | "Add an 'admin' scope to the 'User API'."
"Update the token lifetime for my 'Payment API' to 1 hour."
"Change the signing algorithm for my API to RS256." | ## Actions management | Tool | Description | Natural language examples | | - | - | - | | `auth0_list_actions` | List all Actions in the Auth0 tenant. | "Show me all my Auth0 Actions."
"What Actions do I have configured?"
"List the Actions in my tenant." | | `auth0_get_action` | Get details about a specific Auth0 Action. | "Show me the code for my 'Enrich User Profile' Action."
"Get details about my login flow Action."
"What does my 'Add Custom Claims' Action do?" | | `auth0_create_action` | Create a new Auth0 Action. | "Create an Action that adds user roles to tokens."
"Set up an Action to log failed login attempts."
"Create a post-login Action that checks user location." | | `auth0_update_action` | Update an existing Auth0 Action. | "Update my 'Add Custom Claims' Action to include department information."
"Modify the IP filtering logic in my security Action."
"Fix the bug in my user enrichment Action." | | `auth0_deploy_action` | Deploy an Auth0 Action. | "Deploy my 'Add Custom Claims' Action to production."
"Make my new security Action live."
"Deploy the updated user enrichment Action." | ## Logs management | Tool | Description | Natural language examples | | - | - | - | | `auth0_list_logs` | List logs from the Auth0 tenant | "Show me recent login attempts."
"Find failed logins from the past 24 hours."
"Get authentication logs from yesterday."
"Show me successful logins for user [john@example.com](mailto:john@example.com)." | | `auth0_get_log` | Get a specific log entry by ID. | "Show me details for log entry ."
"Get more information about this failed login attempt."
"What caused this authentication error?" | ## Forms management | Tool | Description | Natural language examples | | - | - | - | | `auth0_list_forms` | List all Forms in the Auth0 tenant. | "Show me all my Auth0 Forms."
"What login Forms do I have configured?"
"List the custom Forms in my tenant." | | `auth0_get_form` | Get details about a specific Auth0 Form. | "Show me the details of my 'Corporate Login' Form."
"What does my password reset Form look like?"
"Get the configuration for my signup Form." | | `auth0_create_form` | Create a new Auth0 Form. | "Create a new login Form with our company branding."
"Set up a custom signup Form that collects department information."
"Create a password reset Form with our logo." | | `auth0_update_form` | Update an existing Auth0 Form. | "Update the colors on our login Form to match our new brand guidelines."
"Add a privacy policy link to our signup Form."
"Change the logo on our password reset Form." | ## Combining Operations You can also ask [Claude](https://claude.ai/) to perform multiple related operations in sequence: #### Set up a new API with client access ```bash wrap lines theme={null} Create a new API called "Inventory API" with read and write scopes, then update my "Admin Dashboard" application to have access to it. ``` #### Create and deploy a security Action ```bash wrap lines theme={null} Create an Action that requires MFA for users logging in from outside our corporate network, then deploy it to the login flow. ``` #### Analyze security events ```bash wrap lines theme={null} Show me all failed login attempts from the past week, and identify any patterns or suspicious activity. ``` #### Updating branding across forms ```bash wrap lines theme={null} Update all our Auth0 forms to use our new logo at
**Applications**: For each of your apps for which you want to authenticate users with Auth0, register an application.
**APIs**: For each of your APIs that you want to secure with Auth0, register an API. Create new APIs and manage existing ones.
**SSO Integrations**: View and enable external services for SSO. Create new SSO integrations and configure, review, and manage integration settings. | | **Authentication** | Manage the identity providers through which you allow users to authenticate to your apps.
**Database**: Securely store and manage identifier/password credentials either in an Auth0 datastore or in your own database. Connect to existing databases using template-based JavaScript scripts that run on Auth0's server during every authentication. Gradually migrate an existing database of legacy credentials to Auth0 as users authenticate (no password reset required).
**Social**: Configure social identity providers (such as Facebook, X, and Github) through which your users can log in.
**Enterprise**: Configure enterprise identity providers (such as Active Directory, SAML, and Office 365) through which your users can log in using their enterprise credentials.
**Passwordless**: Allow your users to sign up and log in using one-time passcodes (delivered by email or SMS) or one-click links, instead of passwords. | | **Organizations** | Manage the organizations you do business with, and customize the experience their users have when accessing your applications. | | **User Management** | Manage your users' identities and permissions.
**Users**: View and create user profiles, perform password resets, block and delete users, and more.
**Roles**: Create and manage roles for your apps. Roles contain collections of permissions and can be assigned to users. | | **Branding** | **Universal Login**: Create and customize a login page to which you can direct users to authenticate.
**Custom Domains**: Create a custom domain to maintain a consistent experience for your users.
**Email Templates**: Use templates to create welcome, password reset, and account verification email-based workflows.
**Email Provider**: Designate and configure your custom email provider information. | | **Security** | Configure extra layers of security by enabling shields that protect your users against different types of attacks and user access anomalies.
**Attack Protection**: Manage settings for bot, IP throttling, brute-force, and breached password attacks.
**Multi-factor Auth**: Require additional factors during the login process to prevent unauthorized access.
**Monitoring**: Monitor threat intelligence events with one of our data visualization and alerting integrations. | | **Actions** | Configure flows such as login, machine-to-machine, user registration, and password resets. Create and manage customized actions used in flows. | | **Auth Pipeline** | **Rules**: Configure custom JavaScript snippets that are executed in Auth0 as part of each user authentication transaction. You can call external APIs, filter which users can log in to your application, use an AllowList, configure geolocated access, and so on.
**Hooks**: Customize the behavior of Auth0 when you use Database Connections by configuring Node.js code that is executed against extensibility points (which are comparable to webhooks that come with a server). | | **Monitoring** | **Logs**: View log data of actions taken in the dashboard by administrators and user logins.
**Streams**: Create and manage log event streaming to external data analysis services. | | **Marketplace** | Explore integrations that help your business do more with Auth0. | | **Extensions** | Extend the Auth0 platform with official and third-party add-ons. | | **Settings** | Configure your tenants, manage your Auth0 subscription and payment options, control your tenant administrators and other user roles. Manage other tenant settings related to your custom domains, signing keys, and other advanced settings. | | **Get Support** | Go to our [Support Center](https://support.auth0.com). If your plan does not have access to support services, see the [Auth0 Community](https://community.auth0.com/). | ## Manage account settings On the top left, you can see your tenant's name and icon, and a little arrow. This arrow displays a dropdown menu that you can use to configure different aspects of your account: * [**Settings**](/docs/get-started/tenant-settings): Configure several aspects of your tenant. * [**Invite a member**](/docs/get-started/manage-dashboard-access): Add an additional user as an administrator or other role to your tenant configuration. * [**Quota Utilization**](https://support.auth0.com/reports/quota): See quota utilization information about your subscription and tenants. * [**Create tenant**](/docs/get-started/auth0-overview/create-tenants): Use this to create a new tenant. * **Switch tenant**: If you have [multiple tenants](/docs/get-started/auth0-overview/create-tenants/create-multiple-tenants), use this option to switch between them. If you create an application for one tenant, you will not see it listed for another tenant. On the top right, you see several clickable options: * **Search**: Look for apps, marketplace entries, users, and other content related to your tenant. * **Discuss your needs:** Contact an Auth0 expert to help you reach your goals with Auth0. * **Docs:** A link to the documentation site you’re reading right now. * **Notifications bell:** Informs you of new communication from Auth0 or your tenant settings. * **Profile:** A link to your local tenant profile, as well as options to [change your theme](/docs/get-started/dashboard-profile/light-and-dark-themes) and log out. ## Learn more * [Create Tenants](/docs/get-started/auth0-overview/create-tenants) * [Tenant Settings](/docs/get-started/tenant-settings) * [Application Settings](/docs/get-started/applications/application-settings) * [Create Users](/docs/manage-users/user-accounts/create-users) * [API Settings](/docs/get-started/apis/api-settings) * [Logs](/docs/deploy-monitor/logs) # About the Activity Page Source: https://auth0.com/docs/get-started/auth0-overview/dashboard/activity Learn about the metrics on the Activity page for your Auth0 tenant, including information on active users, failed logins, and more. The Activity page provides a summary of key data about your Auth0 tenant, including information on active users, failed logins, and more. ## Things to know * Viewing a tenant's Activity page requires an account with an administrator role (such as Administrator or Owner). * The **Support Access** role has read-only access to view metrics on the tenant's Activity page but cannot modify settings. * To ensure data is consistent, the current date cannot be selected in the date picker and data may take up to 24 hours to display. ## Metrics Here’s what you will see on your tenant's Activity page. ### Totals At the top of the page, you'll see your tenant's total number of users, applications, APIs, and connections.
Agents: AI Agents configuration
Users: User management
Organizations: Organization management
Settings: Tenant configuration and account management | | Integration | Applications: Register and manage your applications
APIs: Register and manage your APIs
Authentication: Configure authentication (Database, Passwordless)
Connections: Manage social connections
Enterprise SSO: Manage enterprise connections and self-service profiles
Authorization: Create and manage roles | | Customization | Branding: Visual editor for Universal Login theming
Pages: Universal Login and Forms page customization
Portals: Visual editor for portal pages
Domains: Manage custom domains | | Messaging | Emails: Email templates and configuration
Phone: Phone messaging settings | | Automation & Extensibility | Actions: Create and manage Auth0 Actions
Events: Stream authentication events to external services
Extensions: Official and third-party add-ons
Rules: Legacy rules (for existing configurations)
Hooks: Legacy hooks (for existing configurations) | | Security & Monitoring | Attack Protection: Bot, IP throttling, Brute-force, and Breached Password Protection
Access Control: Access Control lists
Security Dashboard: Security overview and threat metrics
Logs: View activity logs
Analytics: Usage analytics and reporting | ## Browser support The new navigation requires modern browsers with `localStorage` support for sidebar state persistence. If you encounter any issues, you can always switch back to the classic navigation using the profile menu toggle. ## Learn more * [Auth0 Dashboard Overview](/docs/get-started/auth0-overview/dashboard) * [Dashboard Activity](/docs/get-started/auth0-overview/dashboard/activity) * [Search and Filter by Fields in Auth0 Dashboard](/docs/get-started/auth0-overview/dashboard/search-and-filter-auth0-dashboard) * [Tenant Settings](/docs/get-started/tenant-settings) # Register APIs Source: https://auth0.com/docs/get-started/auth0-overview/set-up-apis Learn how to register APIs in the Auth0 Dashboard.
{{ user.name }}
{{ user.email }}
Sign in to your account to get started.
{user.name}
{user.email}
Loading...
} {error &&Error: {error.message}
} {!isLoading && !isAuthenticated && (Welcome
Sign in to get started
Loading...
,
});
return {result}
Loading profile...
{{ user.name }}
{{ user.email }}
Loading...
Oops!
{{ error.message }}
Welcome
Get started by signing in to your account
{{ JSON.stringify(response, null, 2) }}
```
Loading profile...
}
@if ((auth.isAuthenticated$ | async) && (auth.user$ | async); as user) {
@if (user.picture) {
![]()
}
}
`
})
export class ProfileComponent {
protected auth = inject(AuthService);
}
```
{{ user.name }}
{{ user.email }}
@if (auth.isLoading$ | async) {
}
@if (auth.error$ | async; as error) {
}
@if (!(auth.isLoading$ | async) && !(auth.error$ | async)) {
`,
styles: []
})
export class App {
protected auth = inject(AuthService);
}
```
Loading...
Oops!
Welcome to Sample0
@if (auth.isAuthenticated$ | async) {Your Profile
Get started by signing in to your account
Cap'n Web + Auth0
Secure WebSocket RPC with Authentication
🔌 RPC Operations
${this.user.name || 'User'}
Email: ${this.user.email || 'Not provided'}
User ID: ${this.user.sub}
`; document.getElementById('profile-info').innerHTML = profileHtml; } } showLoggedOutState() { document.getElementById('login-btn').classList.remove('hidden'); document.getElementById('logout-btn').classList.add('hidden'); document.getElementById('profile-section').classList.add('hidden'); document.getElementById('rpc-section').classList.add('hidden'); } showStatus(message, type = 'info') { const statusDiv = document.getElementById('status'); statusDiv.innerHTML = `${message}
`;
// Auto-hide success and info messages after 5 seconds
if (type === 'success' || type === 'info') {
setTimeout(() => {
statusDiv.innerHTML = '';
}, 5000);
}
}
showRPCResult(title, data) {
const resultsDiv = document.getElementById('rpc-results');
const resultHtml = `
${title}
${JSON.stringify(data, null, 2)}
Cap'n Web + Auth0 Profile Demo
Initializing...
🔐 Welcome!
This demo shows Auth0 authentication with Cap'n Web RPC for real-time profile management.
👤 Profile Management
Email: Loading...