Auth0 changed its API changelog

===================================================================
--- before
+++ after
@@ -3,8 +3,26 @@
 Information on the latest updates and additions to the Auth0 platform.
 
 Filter by version
 
+August 17, 2026
+Version 202627
+
+added
+
+CUSTOM RATE LIMITS AVAILABLE IN EARLY ACCESS
+
+Copied to clipboard
+
+Custom Rate Limits allow Auth0 Customers to limit the amount of RPS their first-party, third-party, or CIMD apps can consume, so as to mitigate the risk that any one Client can exhaust the customer’s Tenant Rate Limit Entitlement on their tenant’s Authentication API Rate Limit Policy.
+
+Key Early Access Features:
+
+ * API-based self service configuration of Custom Rate Limit Policies to limit the number of Authentication API - OAuth requests that can be consumed by individual clients or group of clients (all third-party apps, or CIMD apps) can consume
+ * Configure Rate Limit Policy enforcement to more safely rollout policies. Enforcement can be configured to block requests, or trigger non-blocking notifications.
+
+Visit the Docs here: https://auth0.com/docs/troubleshoot/customer-support/operational-policies/rate-limit-policy/custom-rate-limit-policies
+
 August 13, 2026
 
 updated
 
@@ -240,23 +258,30 @@
 
 Please contact the Sales team if you would like to evaluate Enterprise Connect Beta.
 
 July 29, 2026
+Version 202631
 
 added
 
-DASHBOARD SEARCH FOR ORGANIZATION MEMBERS NOW IN BETA!
+ORGANIZATION-TO-APPLICATION ENTITLEMENT - EARLY ACCESS
 
 Copied to clipboard
 
-Dashboard Search for Organization members is now available in Public Beta! Find your organization members faster without scrolling through paginated lists.
+Organization-to-App Entitlement lets you control which applications the members of an organization can access - natively, without custom code.
 
-Users can now search Organization Members in real time by name, email, ID and filter by blocked status.
+If you sell multiple products and different customers have purchased different combinations, you can now enforce those boundaries directly in Auth0. When a member of an org tries to log in to an app they're not entitled to, Auth0 denies access automatically. No Actions. No metadata checks. No custom logic to maintain.
 
-Rolling out progressively to Public Cloud tenants starting this week, with broader availability in the coming weeks.
+Opt-in, per org. Entitlement enforcement is disabled by default - existing orgs and login flows are unaffected until you explicitly enable it. You can roll out to one org at a time, making it safe to adopt incrementally.
 
-For detailed documentation on search capabilities, visit our Product documentation.
+Safe to configure before you go live. You can set up all your entitlements first, then enable enforcement when you're ready. There's no risk of locking members out during configuration.
 
+org-to-app [//images.ctfassets.net/kbkgmx9upatd/rUfIbrGmUfR5DgFtEtZXB/2bae811541e02ba9905a790e4d1648cf/dbf50f9c-b7c6-474a-98e4-34c90d325c83.png]
+
+To learn more, review Grant Per-Application Access to an Organization.
+
+By using Organization-to-Application Entitlement, you agree to the applicable Free Trial terms in Okta’s Master Subscription Agreement and Okta’s Privacy Policy during use of the Early Access feature. The Free Trial terms can be found within the Master Subscription Agreement at https://www.okta.com/agreements.
+
 July 29, 2026
 
 added
 
@@ -297,30 +322,23 @@
 
 By using Organization-to-Application Entitlement, you agree to the applicable Free Trial terms in Okta’s Master Subscription Agreement and Okta’s Privacy Policy during use of the Early Access feature. The Free Trial terms can be found within the Master Subscription Agreement at https://www.okta.com/agreements.
 
 July 29, 2026
-Version 202631
 
 added
 
-ORGANIZATION-TO-APPLICATION ENTITLEMENT - EARLY ACCESS
+DASHBOARD SEARCH FOR ORGANIZATION MEMBERS NOW IN BETA!
 
 Copied to clipboard
 
-Organization-to-App Entitlement lets you control which applications the members of an organization can access - natively, without custom code.
+Dashboard Search for Organization members is now available in Public Beta! Find your organization members faster without scrolling through paginated lists.
 
-If you sell multiple products and different customers have purchased different combinations, you can now enforce those boundaries directly in Auth0. When a member of an org tries to log in to an app they're not entitled to, Auth0 denies access automatically. No Actions. No metadata checks. No custom logic to maintain.
+Users can now search Organization Members in real time by name, email, ID and filter by blocked status.
 
-Opt-in, per org. Entitlement enforcement is disabled by default - existing orgs and login flows are unaffected until you explicitly enable it. You can roll out to one org at a time, making it safe to adopt incrementally.
+Rolling out progressively to Public Cloud tenants starting this week, with broader availability in the coming weeks.
 
-Safe to configure before you go live. You can set up all your entitlements first, then enable enforcement when you're ready. There's no risk of locking members out during configuration.
+For detailed documentation on search capabilities, visit our Product documentation.
 
-org-to-app [//images.ctfassets.net/kbkgmx9upatd/rUfIbrGmUfR5DgFtEtZXB/2bae811541e02ba9905a790e4d1648cf/dbf50f9c-b7c6-474a-98e4-34c90d325c83.png]
-
-To learn more, review Grant Per-Application Access to an Organization.
-
-By using Organization-to-Application Entitlement, you agree to the applicable Free Trial terms in Okta’s Master Subscription Agreement and Okta’s Privacy Policy during use of the Early Access feature. The Free Trial terms can be found within the Master Subscription Agreement at https://www.okta.com/agreements.
-
 July 27, 2026
 Version 202630
 
 added
@@ -761,8 +779,32 @@
 
 For complete setup instructions and more, refer to our documentation..
 
 May 27, 2026
+Version 202618
+
+added
+
+ACTIONS - ACCESS TOKEN SCOPE CUSTOMIZATION - EA
+
+Copied to clipboard
+
+We are excited to announce that we are adding new Credentials Exchange Actions Access Token Scope Interfaces and they are now available in Early Access.
+
+These new interfaces allow you to customize the scopes to be considered when the access token is issued by writing Credentials Exchange Actions, considering the restrictions based on API and Client Grants definitions.
+
+Early Access functionality includes:
+
+ * Add/Remove: New interfaces to add or remove target scopes from Credentials Exchange Actions.
+ * Set/Clear: Additional interfaces to clear or set target scopes from Credentials Exchange Actions without having to loop through the list of scopes.
+ * Read: The list of target scopes becomes available immediately after being transformed.
+ * Limits: Increased limits to handle up-to 1000 scopes for both Credentials Exchange Actions.
+ * Bonus: The limits were also increased for Post Login Actions.
+ * Docs:
+   * Event Object: https://auth0.com/docs/customize/actions/explore-triggers/machine-to-machine-trigger/credentials-exchange-event-object#param-target-scopes
+   * API Object: https://auth0.com/docs/customize/actions/explore-triggers/machine-to-machine-trigger/credentials-exchange-api-object#api-transaction
+
+May 27, 2026
 Version 202622
 
 added
 
@@ -787,32 +829,8 @@
 To learn more, visit the Custom Token Exchange documentation.
 
 set-Actor-Actions [https://cdn.auth0.com/blog/set-actor-actions-method.png]
 
-May 27, 2026
-Version 202618
-
-added
-
-ACTIONS - ACCESS TOKEN SCOPE CUSTOMIZATION - EA
-
-Copied to clipboard
-
-We are excited to announce that we are adding new Credentials Exchange Actions Access Token Scope Interfaces and they are now available in Early Access.
-
-These new interfaces allow you to customize the scopes to be considered when the access token is issued by writing Credentials Exchange Actions, considering the restrictions based on API and Client Grants definitions.
-
-Early Access functionality includes:
-
- * Add/Remove: New interfaces to add or remove target scopes from Credentials Exchange Actions.
- * Set/Clear: Additional interfaces to clear or set target scopes from Credentials Exchange Actions without having to loop through the list of scopes.
- * Read: The list of target scopes becomes available immediately after being transformed.
- * Limits: Increased limits to handle up-to 1000 scopes for both Credentials Exchange Actions.
- * Bonus: The limits were also increased for Post Login Actions.
- * Docs:
-   * Event Object: https://auth0.com/docs/customize/actions/explore-triggers/machine-to-machine-trigger/credentials-exchange-event-object#param-target-scopes
-   * API Object: https://auth0.com/docs/customize/actions/explore-triggers/machine-to-machine-trigger/credentials-exchange-api-object#api-transaction
-
 May 26, 2026
 Version 202621
 
 added
@@ -1141,45 +1159,45 @@
 Version 202618
 
 added
 
-SELF-SERVICE DOMAIN VERIFICATION NOW IN GENERAL AVAILABILTY!
+SELF-SERVICE PROVISIONING NOW IN GENERAL AVAILABILITY!
 
 Copied to clipboard
 
-We're excited to announce that Self-Service Domain Verification is now in General Availability! Allow your customers' IT admins to verify their own email domains for HRD directly within the SSO setup assistant — no back-and-forth with your team required.
+We’re thrilled to announce that the Self-Service Provisioning experience is now in General Availability! Empower your customers' IT teams to handle user onboarding and offboarding themselves, which means less manual work and fewer support tickets for your team.
 
-Key Advantages at a Glance:
+Key Advantages at a Glance
 
- * Proven ownership: IT admins verify domains via DNS TXT record.
- * Flexible requirements: Configure domain verification as off, optional, or required — per customer engagement.
- * Domain management: IT admins can now add, re-verify, and delete domains entirely through self-service.
- * Enterprise-ready controls: Pre-configure domains for your customers to verify, or pre-verify domains on their behalf — with verified domains automatically powering Organization Discovery when enabled.
+ * Automation: Allow your customer's admins to manage their own SCIM setup.
+ * Interoperability: Ensure seamless integration with a wide variety of customer IdPs.
+ * Consistency: Use a single, unified schema for easier support and debugging.
+ * Flexibility: Retain the ability to override attribute mappings for specific protocols if needed.
 
-To dive deeper, please review our updated documentation on Self-Service Enterprise Configuration.
+User Provisioning [//images.ctfassets.net/kbkgmx9upatd/1sLKLMX9mHZ3fwwnYVtM0p/bf92648b962e8ab7127231222020f59a/SS-SCIM.gif]
 
+To dive deeper, please review our updated documented on Self-Service Enterprise Configuration.
+
 April 28, 2026
 Version 202618
 
 added
 
-SELF-SERVICE PROVISIONING NOW IN GENERAL AVAILABILITY!
+SELF-SERVICE DOMAIN VERIFICATION NOW IN GENERAL AVAILABILTY!
 
 Copied to clipboard
 
-We’re thrilled to announce that the Self-Service Provisioning experience is now in General Availability! Empower your customers' IT teams to handle user onboarding and offboarding themselves, which means less manual work and fewer support tickets for your team.
+We're excited to announce that Self-Service Domain Verification is now in General Availability! Allow your customers' IT admins to verify their own email domains for HRD directly within the SSO setup assistant — no back-and-forth with your team required.
 
-Key Advantages at a Glance
+Key Advantages at a Glance:
 
- * Automation: Allow your customer's admins to manage their own SCIM setup.
- * Interoperability: Ensure seamless integration with a wide variety of customer IdPs.
- * Consistency: Use a single, unified schema for easier support and debugging.
- * Flexibility: Retain the ability to override attribute mappings for specific protocols if needed.
+ * Proven ownership: IT admins verify domains via DNS TXT record.
+ * Flexible requirements: Configure domain verification as off, optional, or required — per customer engagement.
+ * Domain management: IT admins can now add, re-verify, and delete domains entirely through self-service.
+ * Enterprise-ready controls: Pre-configure domains for your customers to verify, or pre-verify domains on their behalf — with verified domains automatically powering Organization Discovery when enabled.
 
-User Provisioning [//images.ctfassets.net/kbkgmx9upatd/1sLKLMX9mHZ3fwwnYVtM0p/bf92648b962e8ab7127231222020f59a/SS-SCIM.gif]
+To dive deeper, please review our updated documentation on Self-Service Enterprise Configuration.
 
-To dive deeper, please review our updated documented on Self-Service Enterprise Configuration.
-
 April 28, 2026
 Version 202618
 
 added
@@ -1460,8 +1478,22 @@
 
 Learn more: https://auth0.com/docs/customize/login-pages/universal-login/customize-text-elements
 
 April 8, 2026
+
+added
+
+EXPRESS SUBMISSION TO THE OKTA INTEGRATION NETWORK
+
+Copied to clipboard
+
+Auth0 developers leveraging Express Configuration with Okta now have a more streamlined process for submitting their application to the Okta Integration Network.
+
+The Okta Integration Network (OIN) Wizard has been updated with a new section for Auth0 developers that automatically populates the required configuration fields for OpenID Connect (OIDC), System for Cross-domain Identity Management (SCIM), and Global Token Revocation (GTR) integrations, based on information sourced from the Auth0 Dashboard.
+
+To learn more about Express Configuration with Okta and the Okta Integration Network (OIN), click here.
+
+April 8, 2026
 Version 202614
 
 added
 
@@ -1483,22 +1515,8 @@
  * Support across Management SDKs, Authentication SDKs, and Forms
 
 Visit Auth0 docs to get started.
 
-April 8, 2026
-
-added
-
-EXPRESS SUBMISSION TO THE OKTA INTEGRATION NETWORK
-
-Copied to clipboard
-
-Auth0 developers leveraging Express Configuration with Okta now have a more streamlined process for submitting their application to the Okta Integration Network.
-
-The Okta Integration Network (OIN) Wizard has been updated with a new section for Auth0 developers that automatically populates the required configuration fields for OpenID Connect (OIDC), System for Cross-domain Identity Management (SCIM), and Global Token Revocation (GTR) integrations, based on information sourced from the Auth0 Dashboard.
-
-To learn more about Express Configuration with Okta and the Okta Integration Network (OIN), click here.
-
 April 7, 2026
 
 added
 
@@ -1915,24 +1933,8 @@
  * Configure Session Metadata
  * Use Case: Organization Information in Session Metadata
 
 February 6, 2026
-
-added
-
-CREDENTIAL GUARD: BREACHED PHONE CREDENTIALS SUPPORT
-
-Copied to clipboard
-
-To strengthen defenses across the identity surface, we have added millions of breached phone credentials to our detection capabilities within Credential Guard
-
-This enhancement allows organizations using Phone as an Identifier to proactively identify compromised credentials and trigger automated security responses, such as login blocks or password resets.
-
-This expansion ensures that phone-based authentication is as secure as traditional email-based methods without impacting system performance.
-
-For more information on Credential Guard, check out our online documentation.
-
-February 6, 2026
 Version 202602
 
 added
 
@@ -1996,8 +1998,24 @@
 
  * auth0/agent-skills repo
  * Documentation
 
+February 6, 2026
+
+added
+
+CREDENTIAL GUARD: BREACHED PHONE CREDENTIALS SUPPORT
+
+Copied to clipboard
+
+To strengthen defenses across the identity surface, we have added millions of breached phone credentials to our detection capabilities within Credential Guard
+
+This enhancement allows organizations using Phone as an Identifier to proactively identify compromised credentials and trigger automated security responses, such as login blocks or password resets.
+
+This expansion ensures that phone-based authentication is as secure as traditional email-based methods without impacting system performance.
+
+For more information on Credential Guard, check out our online documentation.
+
 February 2, 2026
 
 added
 
@@ -2041,26 +2059,28 @@
 January 30, 2026
 
 added
 
-SELF-SERVICE DOMAIN VERIFICATION FOR ORGANIZATION DISCOVERY NOW IN EARLY ACCESS!
+NEW FGA DASHBOARD LOGGING UI IS BEING ROLLED OUT
 
 Copied to clipboard
 
-We’ve integrated Organization Discovery by Domain into the Self-Service SSO workflow, eliminating manual backend configuration and providing a seamless login experience for your enterprise users.
+We are excited to announce the FGA Logging UI! This introduces a web interface to the existing logging API, giving you the ability to view FGA logs directly in the FGA Dashboard.
 
-Zero-Touch Discovery Previously, verifying a domain only configured the SSO connection. Now, when a ticket is scoped to a single Organization, verified domains are automatically synced to the Organization record. This enables Organization Domain Discovery instantly, allowing end-users to log in with just their email address.
+Users can now filter, sort and inspect access logs directly from the FGA Dashboard, significantly reducing the time required for debugging and troubleshooting issues.
 
-Key Enhancements:
+The Logging UI provides an easy-to-use visual interface with capabilities to sort and filter log entries.
 
- * Verify One, Apply Everywhere: Verified domains are added to both the Connection and the Organization simultaneously.
- * Domain Association: If a domain was previously verified for an Organization, customers can now simply associate it with a new connection, skipping repeat DNS TXT steps.
- * Deterministic Routing: By gating this to a 1:1 mapping, we ensure users are routed to the correct IdP every time.
+ * Visual Interface: Users can now immediately view a list of log entries for operations like Check() and Write() in the main viewing area of the UI. Drilling down into a single log entry will open a side panel for a full detailed view of the log data in JSON format, with a convenient copy-and-paste button to quickly copy and paste log data into another application for viewing or saving.
 
-Learn more about Self-Service SSO in the product documentation.
+ * Date/time ranges: Viewing log data can be daunting due to sheer volume. The UI has a convenient date picker to set the time-bound log retrieval window.
 
-By using Self-Service SSO Domain Verification for Organization Discovery by Domain, you agree to the applicable Free Trial terms in Okta’s Master Subscription Agreement and Okta’s Privacy Policy during use of the Early Access feature. The Free Trial terms can be found within the Master Subscription Agreement at https://www.okta.com/agreements.
+ * Filtering: We’ve introduced a simple search box for filtering. Its simplicity does not take away from its power as the search accepts Lucene syntax (a subset) for advanced querying of logs. Now, retrieving all write operations is as easy as typing request.operation:"Write" into the search box.
 
+ * Sorting: The UI supports standard sorting of fields for ascending and descending ordering of data, used in situations, for example, when quickly needing to toggle between seeing “newest first” or “oldest first” log data.
+
+For more details, refer to Auth0 FGA’s logging documentation.
+
 January 30, 2026
 Version 202605
 
 added
@@ -2107,55 +2127,30 @@
 January 30, 2026
 
 added
 
-NEW FGA DASHBOARD LOGGING UI IS BEING ROLLED OUT
+SELF-SERVICE DOMAIN VERIFICATION FOR ORGANIZATION DISCOVERY NOW IN EARLY ACCESS!
 
 Copied to clipboard
 
-We are excited to announce the FGA Logging UI! This introduces a web interface to the existing logging API, giving you the ability to view FGA logs directly in the FGA Dashboard.
+We’ve integrated Organization Discovery by Domain into the Self-Service SSO workflow, eliminating manual backend configuration and providing a seamless login experience for your enterprise users.
 
-Users can now filter, sort and inspect access logs directly from the FGA Dashboard, significantly reducing the time required for debugging and troubleshooting issues.
+Zero-Touch Discovery Previously, verifying a domain only configured the SSO connection. Now, when a ticket is scoped to a single Organization, verified domains are automatically synced to the Organization record. This enables Organization Domain Discovery instantly, allowing end-users to log in with just their email address.
 
-The Logging UI provides an easy-to-use visual interface with capabilities to sort and filter log entries.
+Key Enhancements:
 
- * Visual Interface: Users can now immediately view a list of log entries for operations like Check() and Write() in the main viewing area of the UI. Drilling down into a single log entry will open a side panel for a full detailed view of the log data in JSON format, with a convenient copy-and-paste button to quickly copy and paste log data into another application for viewing or saving.
+ * Verify One, Apply Everywhere: Verified domains are added to both the Connection and the Organization simultaneously.
+ * Domain Association: If a domain was previously verified for an Organization, customers can now simply associate it with a new connection, skipping repeat DNS TXT steps.
+ * Deterministic Routing: By gating this to a 1:1 mapping, we ensure users are routed to the correct IdP every time.
 
- * Date/time ranges: Viewing log data can be daunting due to sheer volume. The UI has a convenient date picker to set the time-bound log retrieval window.
+Learn more about Self-Service SSO in the product documentation.
 
- * Filtering: We’ve introduced a simple search box for filtering. Its simplicity does not take away from its power as the search accepts Lucene syntax (a subset) for advanced querying of logs. Now, retrieving all write operations is as easy as typing request.operation:"Write" into the search box.
+By using Self-Service SSO Domain Verification for Organization Discovery by Domain, you agree to the applicable Free Trial terms in Okta’s Master Subscription Agreement and Okta’s Privacy Policy during use of the Early Access feature. The Free Trial terms can be found within the Master Subscription Agreement at https://www.okta.com/agreements.
 
- * Sorting: The UI supports standard sorting of fields for ascending and descending ordering of data, used in situations, for example, when quickly needing to toggle between seeing “newest first” or “oldest first” log data.
-
-For more details, refer to Auth0 FGA’s logging documentation.
-
 January 30, 2026
 
 added
 
-GOOGLE WORKSPACE INBOUND USER DIRECTORY SYNC IS NOW GENERALLY AVAILABLE!
-
-Copied to clipboard
-
-We’re excited to announce that Google Workspace User Directory Sync is now generally available! This feature keeps Auth0 user profiles up to date by syncing users from your Google Workspace directory into Auth0 - so user profile updates don’t depend on login events.
-
-Key highlights of this release:
-
- * Dashboard configuration: Enable and manage inbound user directory sync directly from the Auth0 Dashboard on your Google Workspace enterprise connection (including attribute mapping, automated sync, and manual sync).
- * Management API support: Programmatically enable, configure, and run inbound user directory sync using the Management API Connections endpoints.
- * Self-Service SSO experience: Your customers’ IT teams can configure Google Workspace inbound directory sync alongside SSO and SCIM provisioning, and manage user onboarding/offboarding directly.
-
-Learn more:
-
- * Sync Google Workspace Users to Auth0 with Directory Sync
- * Management API Connection Endpoints
-
-Screenshot 2026-01-30 at 10.47.49 AM [//images.ctfassets.net/kbkgmx9upatd/2bVmoNFeDlZBTetDmgw1gy/fd8428b105883b223c54d880a935214b/Screenshot_2026-01-30_at_10.47.49%C3%A2__AM.png]
-
-January 30, 2026
-
-added
-
 INBOUND SCIM GROUPS FOR ENTERPRISE CONNECTIONS IS NOW IN LIMITED EARLY ACCESS
 
 Copied to clipboard
 
@@ -2176,8 +2171,31 @@
 How to get access
 
 To join the Limited EA program and access SCIM Groups for Enterprise connections, complete the EA Terms & Conditions form and contact your Auth0 Account Team to request activation and supporting documentation.
 
+January 30, 2026
+
+added
+
+GOOGLE WORKSPACE INBOUND USER DIRECTORY SYNC IS NOW GENERALLY AVAILABLE!
+
+Copied to clipboard
+
+We’re excited to announce that Google Workspace User Directory Sync is now generally available! This feature keeps Auth0 user profiles up to date by syncing users from your Google Workspace directory into Auth0 - so user profile updates don’t depend on login events.
+
+Key highlights of this release:
+
+ * Dashboard configuration: Enable and manage inbound user directory sync directly from the Auth0 Dashboard on your Google Workspace enterprise connection (including attribute mapping, automated sync, and manual sync).
+ * Management API support: Programmatically enable, configure, and run inbound user directory sync using the Management API Connections endpoints.
+ * Self-Service SSO experience: Your customers’ IT teams can configure Google Workspace inbound directory sync alongside SSO and SCIM provisioning, and manage user onboarding/offboarding directly.
+
+Learn more:
+
+ * Sync Google Workspace Users to Auth0 with Directory Sync
+ * Management API Connection Endpoints
+
+Screenshot 2026-01-30 at 10.47.49 AM [//images.ctfassets.net/kbkgmx9upatd/2bVmoNFeDlZBTetDmgw1gy/fd8428b105883b223c54d880a935214b/Screenshot_2026-01-30_at_10.47.49%C3%A2__AM.png]
+
 January 28, 2026
 
 added
 
@@ -2548,8 +2566,26 @@
 You can read more about the solution suite and the component features in the Auth0 for AI documentation.
 
 November 18, 2025
 
+updated
+
+SECURITY CENTER THREAT BEHAVIOR METRICS UPDATE
+
+Copied to clipboard
+
+We’ve refined the logic behind how Security Center metrics are calculated to provide more accurate and actionable insights.
+
+Metrics now reflect IP activity using the following logic:
+
+When an IP address triggers more than 10 relevant events for a given metric within a single hour, it will now be counted toward that metric.
+
+This update ensures greater consistency and reliability across event-based metrics within the Security Center.
+
+For more details on which metrics are affected and their updated definitions, see the Security Center Metrics documentation
+
+November 18, 2025
+
 added
 
 AUTH FOR MCP: NOW IN EARLY ACCESS
 
@@ -2578,26 +2614,8 @@
 Auth for MCP is available today in Early Access. To participate, please submit the Early Access Form and/or contact your Auth0 Technical Account Manager.
 
 For setup instructions, SDKs, and sample applications, and more, visit the Auth for MCP documentation.
 
-November 18, 2025
-
-updated
-
-SECURITY CENTER THREAT BEHAVIOR METRICS UPDATE
-
-Copied to clipboard
-
-We’ve refined the logic behind how Security Center metrics are calculated to provide more accurate and actionable insights.
-
-Metrics now reflect IP activity using the following logic:
-
-When an IP address triggers more than 10 relevant events for a given metric within a single hour, it will now be counted toward that metric.
-
-This update ensures greater consistency and reliability across event-based metrics within the Security Center.
-
-For more details on which metrics are affected and their updated definitions, see the Security Center Metrics documentation
-
 November 13, 2025
 Version 202546
 
 added
@@ -2622,24 +2640,8 @@
 November 12, 2025
 
 added
 
-NEW DYNAMIC CLIENT REGISTRATION (DCR) SCOPE ADDED TO TENANT ACL
-
-Copied to clipboard
-
-Auth0 has added a Dynamic Client Registration (DCR) scope to the Tenant Access Control List (ACL).
-
-This enhancement allows administrators to control access to the /oidc/register endpoint based on a variety of network and client signals, helping prevent unauthorized or automated client creation.
-
-Configuration is available via the Management API.
-
-Learn more about our Tenant Access Control List in our online documentation found here
-
-November 12, 2025
-
-added
-
 ACTIONS - TYPESCRIPT DEFINITIONS IN NPM
 
 Copied to clipboard
 
@@ -2676,8 +2678,24 @@
 CAPTCHA Management: Fully manage your CAPTCHA provider selection and configuration, including Auth0’s native challenge or third-party solutions.
 
 To learn more about the new Bot Detection API endpoints check out our online documentation here
 
+November 12, 2025
+
+added
+
+NEW DYNAMIC CLIENT REGISTRATION (DCR) SCOPE ADDED TO TENANT ACL
+
+Copied to clipboard
+
+Auth0 has added a Dynamic Client Registration (DCR) scope to the Tenant Access Control List (ACL).
+
+This enhancement allows administrators to control access to the /oidc/register endpoint based on a variety of network and client signals, helping prevent unauthorized or automated client creation.
+
+Configuration is available via the Management API.
+
+Learn more about our Tenant Access Control List in our online documentation found here
+
 November 7, 2025
 Version 202544
 
 added
@@ -2729,22 +2747,9 @@
 
 How to Get Started: To join the Beta program and access Google Workspace User Directory Sync, complete the Beta Terms & Conditions form and contact your Auth0 Account Team to request activation and supporting documentation.
 
 November 3, 2025
-Version 202544
 
-deprecated
-
-PROMPT FOR ORGANIZATION NAME WITHOUT SSO
-
-Copied to clipboard
-
-Login flows initiated in the context of client applications associated with business users (organization_usage=require) and configured to prompt for the organization at the start of the login flow (organization_require_behavior=pre_login_prompt) will consider an existing authenticated session and allow single sign-on (SSO).
-
-The previous behavior where these flows disregarded SSO is deprecated. We have provided additional information and timelines for enforcing this change across tenants through a dashboard and support center notification.
-
-November 3, 2025
-
 added
 
 NEW PRIVATE CLOUD REGION IN THAILAND
 
@@ -2755,28 +2760,21 @@
 This launch plants our secure identity infrastructure in the heart of one of Southeast Asia's largest digital economies. Customers in the region can now leverage this new presence for significantly reduced latency and enhanced performance. It also provides a robust, in-country solution for organizations managing their data governance and sovereignty objectives.
 
 We are excited to support the rapid growth of Thailand's booming e-commerce, fintech, and digital service sectors with this new deployment.
 
-October 31, 2025
+November 3, 2025
+Version 202544
 
-added
+deprecated
 
-IGNORE DUPLICATE WRITES AND MISSING DELETES IN AUTH0 FGA
+PROMPT FOR ORGANIZATION NAME WITHOUT SSO
 
 Copied to clipboard
 
-We've enhanced the Auth0 FGA Write API endpoint to help streamline imports and reduce errors. You can now use two new optional parameters:
+Login flows initiated in the context of client applications associated with business users (organization_usage=require) and configured to prompt for the organization at the start of the login flow (organization_require_behavior=pre_login_prompt) will consider an existing authenticated session and allow single sign-on (SSO).
 
-on_duplicate: "ignore": This will gracefully skip any write operations for relationship tuples that already exist.
+The previous behavior where these flows disregarded SSO is deprecated. We have provided additional information and timelines for enforcing this change across tenants through a dashboard and support center notification.
 
-on_missing: "ignore": This will gracefully skip any delete operations for relationship tuples that do not exist.
-
-Previously, these common conditions would cause the entire Write request to fail. These new parameters prevent unnecessary failures, eliminating the need for complex client-side retry logic and improving import performance.
-
-This feature is available now via the API and our latest SDKs.
-
-Learn more about Writing Tuples in FGA from our product documentation or API Reference.
-
 October 31, 2025
 Version 202544
 
 added
@@ -2798,8 +2796,28 @@
 Learn more about Organization Discovery by Domain in our product documentation.
 
 By using Organization Discovery by Domain, you agree to the applicable Free Trial terms in Okta’s Master Subscription Agreement and Okta’s Privacy Policy during use of the Early Access feature. The Free Trial terms can be found within the Master Subscription Agreement at Legal Agreements | Okta.
 
+October 31, 2025
+
+added
+
+IGNORE DUPLICATE WRITES AND MISSING DELETES IN AUTH0 FGA
+
+Copied to clipboard
+
+We've enhanced the Auth0 FGA Write API endpoint to help streamline imports and reduce errors. You can now use two new optional parameters:
+
+on_duplicate: "ignore": This will gracefully skip any write operations for relationship tuples that already exist.
+
+on_missing: "ignore": This will gracefully skip any delete operations for relationship tuples that do not exist.
+
+Previously, these common conditions would cause the entire Write request to fail. These new parameters prevent unnecessary failures, eliminating the need for complex client-side retry logic and improving import performance.
+
+This feature is available now via the API and our latest SDKs.
+
+Learn more about Writing Tuples in FGA from our product documentation or API Reference.
+
 October 29, 2025
 
 added
 
@@ -2817,9 +2835,30 @@
 
 Get started today with our quick start guide to connect your Shopify store to Auth0 and our built-in Sign in with Shop social integration.
 
 October 28, 2025
+Version 202543
 
+changed
+
+UPCOMING CHANGES WHEN USING NON-VERIFIABLE CALLBACK URIS
+
+Copied to clipboard
+
+To enhance security and mitigate risks of application impersonation and phishing attacks, we are recommending the transition to HTTPS-based callbacks using Android App Links and Apple Universal Links whenever possible. In addition, we are introducing a change in how the service handles custom URI schemes and loopback URI as callbacks.
+
+More specifically, for authentication requests specifying a custom URI scheme or a loopback URI as the callback, we are introducing a login confirmation prompt used in scenarios that would previously return a response without requiring user interaction. For example, in a single sign-on (SSO) scenario, if authentication request requirements can be satisfied from an existing authenticated session, the service will display the new login confirmation prompt instead of seamlessly returning a response to the specified custom URI scheme / loopback URI callback.
+
+Additionally, authentication requests including prompt=none will be rejected when Applications use non-verifiable callback URIs and are configured to use the new login confirmation prompt.
+
+Review the User Confirmation Prompt section of Measures Against Application Impersonation to learn more about the new prompt.
+
+Tenants created before October 15, 2025, maintain the previous behavior as the default until April 28, 2026. After the October cutoff date, newly created tenants may default to displaying the new login confirmation prompt with some exceptions due to each environment's deployment schedule. For any tenant maintaining the previous behavior, we recommend you opt in beforehand to use the new behavior. Alternatively, you can opt out of using the additional confirmation prompt if strictly required. Additional information on this situation is available at Migrate to Custom URI Scheme Redirect End-User Confirmation.
+
+Login Confirmation Prompt [https://cdn.auth0.com/blog/Login-confirmation-prompt.png]
+
+October 28, 2025
+
 updated
 
 ENHANCED SIGNUP BOT DETECTION FOR STRONGER SECURITY AND SEAMLESS USER EXPERIENCE
 
@@ -2847,29 +2886,8 @@
 The rollout is in progress for all Enterprise customers with the Attack Protection add-on and will complete over the coming weeks in line with individual release schedules.
 
 For configuration guidance or to learn more about protecting your signup flows, please refer to our documentation or contact your account team.
 
-October 28, 2025
-Version 202543
-
-changed
-
-UPCOMING CHANGES WHEN USING NON-VERIFIABLE CALLBACK URIS
-
-Copied to clipboard
-
-To enhance security and mitigate risks of application impersonation and phishing attacks, we are recommending the transition to HTTPS-based callbacks using Android App Links and Apple Universal Links whenever possible. In addition, we are introducing a change in how the service handles custom URI schemes and loopback URI as callbacks.
-
-More specifically, for authentication requests specifying a custom URI scheme or a loopback URI as the callback, we are introducing a login confirmation prompt used in scenarios that would previously return a response without requiring user interaction. For example, in a single sign-on (SSO) scenario, if authentication request requirements can be satisfied from an existing authenticated session, the service will display the new login confirmation prompt instead of seamlessly returning a response to the specified custom URI scheme / loopback URI callback.
-
-Additionally, authentication requests including prompt=none will be rejected when Applications use non-verifiable callback URIs and are configured to use the new login confirmation prompt.
-
-Review the User Confirmation Prompt section of Measures Against Application Impersonation to learn more about the new prompt.
-
-Tenants created before October 15, 2025, maintain the previous behavior as the default until April 28, 2026. After the October cutoff date, newly created tenants may default to displaying the new login confirmation prompt with some exceptions due to each environment's deployment schedule. For any tenant maintaining the previous behavior, we recommend you opt in beforehand to use the new behavior. Alternatively, you can opt out of using the additional confirmation prompt if strictly required. Additional information on this situation is available at Migrate to Custom URI Scheme Redirect End-User Confirmation.
-
-Login Confirmation Prompt [https://cdn.auth0.com/blog/Login-confirmation-prompt.png]
-
 October 27, 2025
 Version 202541
 
 added
@@ -2931,47 +2949,47 @@
 This SDK is still in Beta and we need your feedback! Please share any feedback, questions or comments on GitHub.
 
 October 10, 2025
 
-added
+upcoming deprecation
 
-EASILY UPDATE YOUR FIREWALL WITH THE NEW IP ALLOW LIST
+AUDIENCE VALIDATION FOR PRIVATE KEY JWT CLIENT AUTHENTICATION
 
 Copied to clipboard
 
-We are excited to announce an improvement that makes it faster and easier for you to keep your firewall configurations up-to-date.
+When validating JWT assertions used for client application authentication, Auth0 will impose stricter requirements and accept only a tenant's issuer identifier as a single JSON string value in the "aud" (audience) claim.
 
-Our IP allow list for Auth0's Public Cloud regions is now available in a standardized, machine-readable format. This new format is designed to help you automate updates and ensure the most accurate configuration for your firewall.
+The possibility of providing an "aud" claim with either one of the approaches listed below is deprecated, and at a future date will cause the service to consider such JWT assertions invalid:
 
-What this means for you:
+ * A JSON array of strings, provided that one of the entries contains a valid issuer identifier or endpoint URL for the respective tenant and endpoint the client authenticates against.
+ * A single JSON string representing a valid endpoint URL for the respective tenant and endpoint the client authenticates against.
 
- * Automation: You can now programmatically fetch and parse the list, eliminating the need for manual updates.
- * Accuracy: The structured data ensures you're always using the latest and most accurate IP addresses.
- * Clarity: The changelogs highlight specific additions and removals, so you can easily see what has been updated.
+OIDC enterprise connections configured to use Private Key JWT in authenticated requests to the upstream identity provider will also be able to use the applicable issuer identifier represented as a JSON string in the "aud" claim included in JWT assertions.
 
-You can access this information at: https://cdn.auth0.com/ip-ranges.json
+We have provided additional information and timelines for enforcing this change across tenants through a dashboard and support center notification.
 
-For more details, please see our documentation on IP allow list.
-
 October 10, 2025
 
-upcoming deprecation
+added
 
-AUDIENCE VALIDATION FOR PRIVATE KEY JWT CLIENT AUTHENTICATION
+EASILY UPDATE YOUR FIREWALL WITH THE NEW IP ALLOW LIST
 
 Copied to clipboard
 
-When validating JWT assertions used for client application authentication, Auth0 will impose stricter requirements and accept only a tenant's issuer identifier as a single JSON string value in the "aud" (audience) claim.
+We are excited to announce an improvement that makes it faster and easier for you to keep your firewall configurations up-to-date.
 
-The possibility of providing an "aud" claim with either one of the approaches listed below is deprecated, and at a future date will cause the service to consider such JWT assertions invalid:
+Our IP allow list for Auth0's Public Cloud regions is now available in a standardized, machine-readable format. This new format is designed to help you automate updates and ensure the most accurate configuration for your firewall.
 
- * A JSON array of strings, provided that one of the entries contains a valid issuer identifier or endpoint URL for the respective tenant and endpoint the client authenticates against.
- * A single JSON string representing a valid endpoint URL for the respective tenant and endpoint the client authenticates against.
+What this means for you:
 
-OIDC enterprise connections configured to use Private Key JWT in authenticated requests to the upstream identity provider will also be able to use the applicable issuer identifier represented as a JSON string in the "aud" claim included in JWT assertions.
+ * Automation: You can now programmatically fetch and parse the list, eliminating the need for manual updates.
+ * Accuracy: The structured data ensures you're always using the latest and most accurate IP addresses.
+ * Clarity: The changelogs highlight specific additions and removals, so you can easily see what has been updated.
 
-We have provided additional information and timelines for enforcing this change across tenants through a dashboard and support center notification.
+You can access this information at: https://cdn.auth0.com/ip-ranges.json
 
+For more details, please see our documentation on IP allow list.
+
 October 8, 2025
 Version 202540
 
 added
@@ -3028,11 +3046,28 @@
 
 This release is currently rolling out to all environments. To enable the Additional Signing Algorithms Limited Early Access release in your Auth0 tenant once available in your environment, please contact your Technical Account Manager to request access.
 
 October 1, 2025
+Version 202538
 
 updated
 
+NATIVE PASSKEY MANAGEMENT NOW AVAILABLE ON MYACCOUNT
+
+Copied to clipboard
+
+We’re very excited to announce the availability of Native Passkey Management, extending the management of authentication methods using APIs. Customers can now delete passkeys using APIs and list all enrolled authentication methods for a user.
+
+Customers can build end-to-end management of the passkeys directly into their native applications.
+
+Native Passkey Management is in Limited EA - reach out to your Auth0 contact to get started today.
+
+To get started with MyAccount please read our documentation
+
+October 1, 2025
+
+updated
+
 REACT NATIVE SDK V5.0 (GA)
 
 Copied to clipboard
 
@@ -3087,25 +3122,29 @@
 Organizations Support for Native Passkeys is in Limited EA - reach out to your Auth0 contact to get started today.
 
 To get started with Passkey APIs and use them with Organizations, please see our documentation or read our blog for getting started with native applications.
 
-October 1, 2025
-Version 202538
+September 30, 2025
+Version 202537
 
-updated
+added
 
-NATIVE PASSKEY MANAGEMENT NOW AVAILABLE ON MYACCOUNT
+CROSS APP ACCESS (XAA) FOR RESOURCE APPLICATIONS IS NOW IN BETA
 
 Copied to clipboard
 
-We’re very excited to announce the availability of Native Passkey Management, extending the management of authentication methods using APIs. Customers can now delete passkeys using APIs and list all enrolled authentication methods for a user.
+We're excited to announce that Cross App Access (XAA) for Resource Applications is now in Beta.
 
-Customers can build end-to-end management of the passkeys directly into their native applications.
+Connecting AI Agents and Third Party Apps in an enterprise introduces two key challenges: poor IT visibility into data sharing and repetitive user consent flows. Cross App Access (XAA) solves this by enabling IT teams to centralize control over these connections, eliminating constant user consent prompts and providing better governance and visibility into data sharing.
 
-Native Passkey Management is in Limited EA - reach out to your Auth0 contact to get started today.
+This new feature provides built-in support for SaaS providers to get their APIs ready for secure connection by AI Agents and other SaaS Apps in enterprise environments. No code changes needed, simply configure the feature in your Auth0 tenant to instantly support central policy enforcement and a seamless user experience.
 
-To get started with MyAccount please read our documentation
+This Beta release is for testing purposes only.
 
+To learn more, read our documentation.
+
+XAA-Resource-Apps-Beta [https://cdn.auth0.com/blog/XAA-Resource-Apps-Beta.png]
+
 September 30, 2025
 Version 202540
 
 added
@@ -3134,29 +3173,8 @@
 Learn more about Self-Service and User Attribute Profile in our product documentation.
 
 By using Self-Service User Provisioning, you agree to the applicable Free Trial terms in Okta’s Master Subscription Agreement and Okta’s Privacy Policy during use of the Early Access feature. The Free Trial terms can be found within the Master Subscription Agreement at Legal Agreements | Okta.
 
-September 30, 2025
-Version 202537
-
-added
-
-CROSS APP ACCESS (XAA) FOR RESOURCE APPLICATIONS IS NOW IN BETA
-
-Copied to clipboard
-
-We're excited to announce that Cross App Access (XAA) for Resource Applications is now in Beta.
-
-Connecting AI Agents and Third Party Apps in an enterprise introduces two key challenges: poor IT visibility into data sharing and repetitive user consent flows. Cross App Access (XAA) solves this by enabling IT teams to centralize control over these connections, eliminating constant user consent prompts and providing better governance and visibility into data sharing.
-
-This new feature provides built-in support for SaaS providers to get their APIs ready for secure connection by AI Agents and other SaaS Apps in enterprise environments. No code changes needed, simply configure the feature in your Auth0 tenant to instantly support central policy enforcement and a seamless user experience.
-
-This Beta release is for testing purposes only.
-
-To learn more, read our documentation.
-
-XAA-Resource-Apps-Beta [https://cdn.auth0.com/blog/XAA-Resource-Apps-Beta.png]
-
 September 18, 2025
 
 updated
 
@@ -3208,8 +3226,29 @@
 
 Pre-assign Tenant Access [//images.ctfassets.net/kbkgmx9upatd/351BkTJanA3OvhU3CB2aJl/07e45de3ce5fc3cef31b3a36ae2a09e0/Screenshot_2025-09-15_at_12.12.51%C3%A2__AM.png]
 
 September 11, 2025
+
+updated
+
+BULK USER IMPORT / EXPORT NOW AVAILABLE IN THE MANAGEMENT DASHBOARD
+
+Copied to clipboard
+
+We are excited to share that Bulk User Import / Export is now available for everyone directly in the Auth0 Management Dashboard!
+
+What’s New:
+
+ * Streamlined experience: submit import / export jobs directly in the Dashboard UI - no Extension management required
+ * Expanded RBAC support: now available to tenant members with Editor - Users Role in addition to Admin
+ * Bulk update existing users: upserting pre-existing users in a connection is now available for manual import jobs
+ * Export as a sample: quickly validate export file structure and field naming by exporting a sample file of 10 users
+
+Deprecation Notice The Bulk Import / Export Extension will reach end of life in October 2025. We recommend switching to the new Dashboard experience as soon as possible.
+
+For more information on the new Import/Export UI, please refer to Bulk User Import / Export in the Auth0 docs.
+
+September 11, 2025
 Version 202535
 
 updated
 
@@ -3237,29 +3276,8 @@
 
  * Tenant ACL Documentation
  * Network ACL Management API
 
-September 11, 2025
-
-updated
-
-BULK USER IMPORT / EXPORT NOW AVAILABLE IN THE MANAGEMENT DASHBOARD
-
-Copied to clipboard
-
-We are excited to share that Bulk User Import / Export is now available for everyone directly in the Auth0 Management Dashboard!
-
-What’s New:
-
- * Streamlined experience: submit import / export jobs directly in the Dashboard UI - no Extension management required
- * Expanded RBAC support: now available to tenant members with Editor - Users Role in addition to Admin
- * Bulk update existing users: upserting pre-existing users in a connection is now available for manual import jobs
- * Export as a sample: quickly validate export file structure and field naming by exporting a sample file of 10 users
-
-Deprecation Notice The Bulk Import / Export Extension will reach end of life in October 2025. We recommend switching to the new Dashboard experience as soon as possible.
-
-For more information on the new Import/Export UI, please refer to Bulk User Import / Export in the Auth0 docs.
-
 September 9, 2025
 Version 202537
 
 added
@@ -3514,8 +3532,24 @@
 
 If the above does not address your needs or you have additional questions, contact us using the Auth0 by Okta Support Center or Auth0 by Okta Community.
 
 August 11, 2025
+
+added
+
+FLEXIBILITY FOR PASSWORDLESS ON UNIVERSAL LOGIN WITH CONNECTION SWITCHING
+
+Copied to clipboard
+
+We're introducing a new feature that gives your end-users the flexibility to choose how they log in. Using Universal Login Custom Prompts, you can now add custom buttons to your login pages. This empowers your users to easily switch between a traditional database (password-based) connection and a passwordless (OTP-based) connection.
+
+This update allows you to create a seamless experience where users can select their preferred authentication method directly from the login challenge screen.
+
+ConnectionSwitcher [//images.ctfassets.net/kbkgmx9upatd/3UrpRNsTVx7devcvh1opBi/c8b6668a4ae85dc37b1ac54291961ebb/image__5_.png]
+
+For full details on this new feature, check out our documentation. To learn more about how to use custom prompts, see the custom prompts documentation.
+
+August 11, 2025
 Version 202531
 
 updated
 
@@ -3538,24 +3572,8 @@
 
 Read our documentation Read the Quickstart
 
 August 11, 2025
-
-added
-
-FLEXIBILITY FOR PASSWORDLESS ON UNIVERSAL LOGIN WITH CONNECTION SWITCHING
-
-Copied to clipboard
-
-We're introducing a new feature that gives your end-users the flexibility to choose how they log in. Using Universal Login Custom Prompts, you can now add custom buttons to your login pages. This empowers your users to easily switch between a traditional database (password-based) connection and a passwordless (OTP-based) connection.
-
-This update allows you to create a seamless experience where users can select their preferred authentication method directly from the login challenge screen.
-
-ConnectionSwitcher [//images.ctfassets.net/kbkgmx9upatd/3UrpRNsTVx7devcvh1opBi/c8b6668a4ae85dc37b1ac54291961ebb/image__5_.png]
-
-For full details on this new feature, check out our documentation. To learn more about how to use custom prompts, see the custom prompts documentation.
-
-August 11, 2025
 Version 202531
 
 updated
 
@@ -3637,8 +3655,22 @@
 
 For more information - Log Streams
 
 July 22, 2025
+
+added
+
+NEW PRIVATE CLOUD REGION IN MEXICO
+
+Copied to clipboard
+
+Auth0 is delighted to introduce Mexico as the latest AWS region for Private Cloud deployments.
+
+This new region establishes our first Private Cloud presence in Mexico, directly addressing the needs of one of Latin America's largest and most dynamic digital economies. The addition of the Mexico region provides lower latency for customers throughout the country and helps meet local data residency and compliance requirements.
+
+We remain committed to expanding our global footprint to serve our customers wherever they are in the world.
+
+July 22, 2025
 Version 202528
 
 updated
 
@@ -3688,22 +3720,8 @@
 ----------------------------------------
 
 Learn more in our Native to Web SSO documentation
 
-July 22, 2025
-
-added
-
-NEW PRIVATE CLOUD REGION IN MEXICO
-
-Copied to clipboard
-
-Auth0 is delighted to introduce Mexico as the latest AWS region for Private Cloud deployments.
-
-This new region establishes our first Private Cloud presence in Mexico, directly addressing the needs of one of Latin America's largest and most dynamic digital economies. The addition of the Mexico region provides lower latency for customers throughout the country and helps meet local data residency and compliance requirements.
-
-We remain committed to expanding our global footprint to serve our customers wherever they are in the world.
-
 July 21, 2025
 Version 202526
 
 added
@@ -3916,16 +3934,34 @@
 Learn more
 
 June 18, 2025
 
-added
+deprecated
 
-CANADIAN FRENCH LANGUAGE SUPPORT ADDED TO AUTH0 DASHBOARD AND DOCS
+REAL-TIME WEBTASKS LOGS EXTENSION DEPRECATION
 
 Copied to clipboard
 
-We’ve added a new language option-Canadian French-to help our users in Canada and beyond build secure identity solutions more easily. If your language preference is set to Canadian French in your browser settings, Auth0 will detect this and automatically serve the Dashboard and Documentation in Canadian French. You can manually override this setting in the Auth0 Dashboard and Docs via the language switcher in the top-right corner.
+WHAT IS CHANGING?
 
+We are deprecating the Real-time Webtask Logs extension with a planned end-of-life after (EOL) September 16, 2025.
+
+As a replacement, we have published the Actions Real-time Logs feature integrated within the Auth0 Dashboard. The extension will cease to be available for new installations, but tenants with the extension already installed will maintain access until the planned EOL.
+
+WHY ARE WE MAKING THIS CHANGE?
+
+The transition to the dashboard will improve the security posture and maintainability of the functionality, while simplifying future enhancements.
+
+HOW ARE YOU AFFECTED?
+
+For active users of the Real-time Webtask Logs extension, its scheduled removal will affect you, as the transition from extension to a direct dashboard capability inherently implies some user experience differences.
+
+WHAT ACTION DO YOU NEED TO TAKE?
+
+You can start using the Actions Real-time Logs feature by navigating to Auth0 Dashboard > Monitoring > Actions Logs.
+
+We recommend that extension users familiarize themselves with the new user interface to avoid disruption once the extension becomes unavailable.
+
 June 18, 2025
 
 deprecated
 
@@ -3968,34 +4004,16 @@
 For example, for scenarios related to reusing secret information previously available from the request, the support for secret management (event.secrets) as part of actions may provide a potential alternative. If the requests include restricted property names, but the information sent within them is not considered sensitive, you may consider using a different parameter name in the request, or ideally, consider using custom parameters as part of pushed authorization requests to avoid disclosing/interception of the data by end-users in browser-based flows. If the data is static per client or connection, consider storing it as part of client or connection metadata.
 
 June 18, 2025
 
-deprecated
+added
 
-REAL-TIME WEBTASKS LOGS EXTENSION DEPRECATION
+CANADIAN FRENCH LANGUAGE SUPPORT ADDED TO AUTH0 DASHBOARD AND DOCS
 
 Copied to clipboard
 
-WHAT IS CHANGING?
+We’ve added a new language option-Canadian French-to help our users in Canada and beyond build secure identity solutions more easily. If your language preference is set to Canadian French in your browser settings, Auth0 will detect this and automatically serve the Dashboard and Documentation in Canadian French. You can manually override this setting in the Auth0 Dashboard and Docs via the language switcher in the top-right corner.
 
-We are deprecating the Real-time Webtask Logs extension with a planned end-of-life after (EOL) September 16, 2025.
-
-As a replacement, we have published the Actions Real-time Logs feature integrated within the Auth0 Dashboard. The extension will cease to be available for new installations, but tenants with the extension already installed will maintain access until the planned EOL.
-
-WHY ARE WE MAKING THIS CHANGE?
-
-The transition to the dashboard will improve the security posture and maintainability of the functionality, while simplifying future enhancements.
-
-HOW ARE YOU AFFECTED?
-
-For active users of the Real-time Webtask Logs extension, its scheduled removal will affect you, as the transition from extension to a direct dashboard capability inherently implies some user experience differences.
-
-WHAT ACTION DO YOU NEED TO TAKE?
-
-You can start using the Actions Real-time Logs feature by navigating to Auth0 Dashboard > Monitoring > Actions Logs.
-
-We recommend that extension users familiarize themselves with the new user interface to avoid disruption once the extension becomes unavailable.
-
 June 17, 2025
 
 added
 
@@ -7821,23 +7839,23 @@
 July 7, 2023
 
 updated
 
-IMPROVED PRODUCTION READINESS CHECKS EXPERIENCE
+TEAMS: EDITING OF TEAM NAME NOW SUPPORTED
 
 Copied to clipboard
 
-We have updated the CIC Production Readiness Checks tool found in the Auth0 Management Dashboard. Documentation links have been updated and "Configure" navigation has been improved to allow for easier use of the Production Readiness Checks tool.
+You requested the ability to change team names, and we have successfully delivered. To change the team name, go to the Teams dashboard, click the Settings icon, and update the Team Name in the Team information section. See the online documentation for additional information on changing team name or Teams in general. Teams Team Information [//images.ctfassets.net/kbkgmx9upatd/22uhv78GtZtQGUOjHxwPEc/3c98ea79a4f74edd655c5a0b86cc6d73/Team_Name_-_Dashboard_Setting.png]
 
 July 7, 2023
 
 updated
 
-TEAMS: EDITING OF TEAM NAME NOW SUPPORTED
+IMPROVED PRODUCTION READINESS CHECKS EXPERIENCE
 
 Copied to clipboard
 
-You requested the ability to change team names, and we have successfully delivered. To change the team name, go to the Teams dashboard, click the Settings icon, and update the Team Name in the Team information section. See the online documentation for additional information on changing team name or Teams in general. Teams Team Information [//images.ctfassets.net/kbkgmx9upatd/22uhv78GtZtQGUOjHxwPEc/3c98ea79a4f74edd655c5a0b86cc6d73/Team_Name_-_Dashboard_Setting.png]
+We have updated the CIC Production Readiness Checks tool found in the Auth0 Management Dashboard. Documentation links have been updated and "Configure" navigation has been improved to allow for easier use of the Production Readiness Checks tool.
 
 June 28, 2023
 
 added