The Tenant Settings page of the Auth0 Dashboard allows you to configure various settings related to your Auth0 tenant.
The General view contains settings that are typically set for tenants. Use this section to customize general tenant settings that will be used in the Lock widget, emails, and various other pages displayed to your users.
Friendly Name: Name you want to be displayed to your users, usually the name of your company or organization.
Logo URL: URL of your logo; it should be a square. This image will appear to your users on various screens and pages.
Support Email: Email address used to contact your support team.
Support URL: Link to your company/organization support page.
You can identify if your tenant is a production, staging, or development. Under Assign Environment Tag, choose the type of environment and click Save.
Default Audience: API Identifier that should be the default audience when using Authorization flows. If you enter a value, all access tokens issued by Auth0 will specify this API Identifier as an audience. Setting the Default Audience is equivalent to appending this audience to every authorization request made to your tenant for every application. This will cause new behavior that might result in breaking changes for some of your applications. Please contact support if you require assistance.
Default Directory: Name of the default connection to be used for the Resource Owner Password Flow. Its value should be the exact name of an existing connection for one of the following strategies:
In the event of an authorization error, you can either display a generic error page to your users or you can redirect users to your own custom error page. To learn more, see Custom Error Pages.
Default Language: Language your tenant will use by default.
Supported Languages: Languages also supported by your tenant.
The Subscription view allows you to review your current subscription and compare features of your current plan to other Auth0 subscription plans. You may also change your subscription plan. To learn more, see Manage Subscription.
The Payment view allows you to enter or update your billing details.
The Tenant Members view lists tenant members assigned to your tenant. You may also add or remove tenant members and review their assigned roles and if they have multi-factor authentication (MFA) enabled. To learn more, see Manage Dashboard Access.
The Custom Domains view allows you to configure a custom domain, which allows you to maintain a consistent user experience. When a custom domain is configured, users will remain in your domain for login rather than being redirected to your
auth0.com domain. To learn more, see Custom Domains.
The Signing Keys view allows you to securely manage the signing key and certificate used to sign ID tokens, access tokens, SAML assertions, and WS-Fed assertions that are sent to your applications.
Rotation Settings: Settings that allow you to rotate the application signing key and certificate. You may choose whether or not to revoke the signing key upon rotation. To learn more, see Signing Keys.
Rotate Signing Key: Rotates the signing key without revoking it; effectively, moves the current key to the previous key. All tokens signed with the previous key will still be valid until it is revoked.
Rotate & Revoke Signing Key: Rotates the signing key and then revokes it; effectively, moves the current key to the previous key, and then invalidates the previous key. Make sure you have updated your application with the next key in the queue before you rotate and revoke the current key.
List of Valid Keys: List of valid application signing keys for your tenant, which are also available at the Metadata endpoint for your application. Valid keys include:
Next in queue: Key that will be used when the signing key is next rotated.
Currently used: Key that is currently in use.
Previously used: Key that was previously used. Its appearance indicates that the signing key has been rotated, but the previously-used key has not yet been revoked.
List of Revoked Keys: List of the last three revoked keys for your tenant. More data about revoked keys is available via tenant logs.
The Advanced view contains advanced settings that are sometimes set for tenants. On this tab, you can also delete your tenant and cancel all associated subscriptions.
Deleted tenants cannot be restored and the tenant name cannot be used again when creating new tenants. If you want to reset your tenant configuration, see Delete or Reset Tenants.
Login and logout
Allowed Logout URLs: URLs that Auth0 can redirect to after logout when no
client_idis specified on the Logout endpoint invocation. Useful as a global list when Single Sign-on (SSO) is enabled. To learn more, see Logout.
Tenant Login URI: URI that points to a route in your application that starts the OIDC login flow by redirecting to the
/authorizeendpoint; it should take the form of
https://mytenant.org/login. This will only be used in scenarios where Auth0 needs your tenant to start the OIDC login flow. To learn more, see Configure Default Login Routes.
Login session management
These settings configure the login session lifetime, which represents the Auth0 Authorization Server session layer. The Authorization Server session layer drives Single Sign-on (SSO). To learn more, see Single Sign-on.
Timeouts for tokens issued by Auth0 can be configured elsewhere. Token timeouts are often used to drive the Application session layer and appear in token claims, such as in the expiration claim for OpenID Connect (OIDC) ID tokens or the lifetime assertion for SAML.
Inactivity timeout: Timeframe (in minutes) after which a user's session will expire if they haven’t interacted with the Authorization Server. It will be superseded by system limits if over 4,320 minutes (3 days) for non-Enterprise plans or 144,000 minutes (100 days) for Enterprise plans.
Require log in after: Timeframe (in minutes) after which a user will be required to log in again, regardless of their activity. It will be superseded by system limits if over 43,200 minutes (30 days) for non-Enterprise plans or 525,600 minutes (365 days) for Enterprise plans.
Device Flow User Code Format
User Code Character Set: Character set used to generate the user code.
User Code Mask: Mask used to format the user code. The mask defines the length of the user code and formats it into a friendly, readable value, allowing spaces or hyphens for readability.
Global client information
The Global Client ID and Global Client Secret are used to generate tokens for legacy Auth0 APIs. Typically, you will not need these values. If you need to have the global client secret changed, please contact support.
Change Password Flow v2: When enabled, the newest version of the Change Password Flow will be used. The previous version has been deprecated, and we strongly recommend enabling v2. This flag is presented only for backward compatibility, and once enabled, you can no longer disable it. You can customize the user interface for the Change Password widget on the Universal Login > Password Reset tab in the Auth0 Dashboard.
OIDC Dynamic Application Registration: When enabled, third-party developers will be able to dynamically register applications for your APIs. You can also update this flag using the Update Tenant Settings Endpoint of the Auth0 Management API. By default, this feature is disabled. To learn more, see Dynamic Client Registration.
Enable Application Connections: When enabled, all current connections will be enabled for any new application that is created.
Use a generic response in public signup API error message: When enabled, errors generated while using the public signup API will return a generic response. This helps protect against user registration enumeration by preventing bad actors from being able to guess previously-registered email addresses or usernames from reading error response codes, such as
Enable Publishing of Enterprise Connections Information with IdP domains: When enabled, it supports Home Realm Discovery, Auth0 Lock relies on a checked public file that includes enterprise connection information. If you don’t require that functionality, you can disable it.
Enable email verification flow during login for Azure AD and ADFS connections: When enabled, users will be presented with an email verification prompt during their first login when using Azure AD or ADFS connections.
Refresh Token Revocation Deletes Grant: When enabled, it deletes the underlying grant when you revoke a refresh token using the Authentication API
Runtime: NodeJS version environment used to execute custom scripts that allow you to extend parts of Auth0's functionality; these include rules, hooks, and database connections. Choose the
node.jsversion environment you will use to execute your custom scripts. If you are migrating from an older version of
node.jsthat is no longer supported, see the migration guide.
Disable Clickjacking Protection for Classic Universal Login: When enabled, additional HTTP security headers will not be included in the response to prevent embedding of Universal Login prompts in an iframe.
Allow Legacy TLS: When enabled, requests to Auth0 servers with legacy TLS (1.0 and 1.1) will work. Note that legacy protocols are insecure, with well-known weaknesses and vulnerabilities within the industry. For maximum security, upgrade to TLS 1.2 or later. Details vary depending on your application. See Deprecations and Migrations for details.
This section displays feature preview options that vary depending on availability.