We're excited to announce that API Access Policies for Applications is now in Early Access for all Auth0 customers and is fully supported for production use.
This feature enables you to control how applications access your APIs registered in Auth0. You can configure separate application API access policies for user access and client (machine-to-machine) flows, giving you declarative, granular and easy-to-reason control over which applications can obtain an access token for a specific API. For instance, with the require_client_grant policy, you can ensure that only explicitly authorized applications can get tokens, even during user flows. This strengthens your security posture by preventing unauthorized applications from accessing sensitive API resources on behalf of a user.
To learn more, check out the documentation.
We're excited to announce that API Access Policies for Applications is now in Early Access for all Auth0 customers and is fully supported for production use.
This feature enables you to control how applications access your APIs registered in Auth0. You can configure separate application API access policies for user access and client (machine-to-machine) flows, giving you declarative, granular and easy-to-reason control over which applications can obtain an access token for a specific API. For instance, with the require_client_grant policy, you can ensure that only explicitly authorized applications can get tokens, even during user flows. This strengthens your security posture by preventing unauthorized applications from accessing sensitive API resources on behalf of a user.
To learn more, check out the documentation.
We're excited to announce that API Access Policies for Applications is now in Early Access for all Auth0 customers and is fully supported for production use.
This feature enables you to control how applications access your APIs registered in Auth0. You can configure separate application API access policies for user access and client (machine-to-machine) flows, giving you declarative, granular and easy-to-reason control over which applications can obtain an access token for a specific API. For instance, with the require_client_grant policy, you can ensure that only explicitly authorized applications can get tokens, even during user flows. This strengthens your security posture by preventing unauthorized applications from accessing sensitive API resources on behalf of a user.
To learn more, check out the documentation.
One of the most requested features for the Auth0 Deploy CLI is here: you can now preview your deployment changes before applying them.
Say goodbye to deployment anxiety. With the new --dry-run flag, you can get a detailed summary of exactly what resources will be created, updated, or deleted before you run an import. This brings the confidence of infrastructure-as-code practices like terraform plan to your Auth0 tenant management.
Get started by simply adding the --dry-run flag to your import command to see a safe preview of your changes.
This will help you and your team:
The Dry Run feature is now available in Early Access. Update to the latest version of the Deploy CLI to get started.
One of the most requested features for the Auth0 Deploy CLI is here: you can now preview your deployment changes before applying them.
Say goodbye to deployment anxiety. With the new --dry-run flag, you can get a detailed summary of exactly what resources will be created, updated, or deleted before you run an import. This brings the confidence of infrastructure-as-code practices like terraform plan to your Auth0 tenant management.
Get started by simply adding the --dry-run flag to your import command to see a safe preview of your changes.
This will help you and your team:
The Dry Run feature is now available in Early Access. Update to the latest version of the Deploy CLI to get started.
One of the most requested features for the Auth0 Deploy CLI is here: you can now preview your deployment changes before applying them.
Say goodbye to deployment anxiety. With the new --dry-run flag, you can get a detailed summary of exactly what resources will be created, updated, or deleted before you run an import. This brings the confidence of infrastructure-as-code practices like terraform plan to your Auth0 tenant management.
Get started by simply adding the --dry-run flag to your import command to see a safe preview of your changes.
This will help you and your team:
The Dry Run feature is now available in Early Access. Update to the latest version of the Deploy CLI to get started.
One of the most requested features for the Auth0 Deploy CLI is here: you can now preview your deployment changes before applying them.
Say goodbye to deployment anxiety. With the new --dry-run flag, you can get a detailed summary of exactly what resources will be created, updated, or deleted before you run an import. This brings the confidence of infrastructure-as-code practices like terraform plan to your Auth0 tenant management.
Get started by simply adding the --dry-run flag to your import command to see a safe preview of your changes.
This will help you and your team:
The Dry Run feature is now available in Early Access. Update to the latest version of the Deploy CLI to get started.
One of the most requested features for the Auth0 Deploy CLI is here: you can now preview your deployment changes before applying them.
Say goodbye to deployment anxiety. With the new --dry-run flag, you can get a detailed summary of exactly what resources will be created, updated, or deleted before you run an import. This brings the confidence of infrastructure-as-code practices like terraform plan to your Auth0 tenant management.
Get started by simply adding the --dry-run flag to your import command to see a safe preview of your changes.
This will help you and your team:
The Dry Run feature is now available in Early Access. Update to the latest version of the Deploy CLI to get started.
One of the most requested features for the Auth0 Deploy CLI is here: you can now preview your deployment changes before applying them.
Say goodbye to deployment anxiety. With the new --dry-run flag, you can get a detailed summary of exactly what resources will be created, updated, or deleted before you run an import. This brings the confidence of infrastructure-as-code practices like terraform plan to your Auth0 tenant management.
Get started by simply adding the --dry-run flag to your import command to see a safe preview of your changes.
This will help you and your team:
The Dry Run feature is now available in Early Access. Update to the latest version of the Deploy CLI to get started.
One of the most requested features for the Auth0 Deploy CLI is here: you can now preview your deployment changes before applying them.
Say goodbye to deployment anxiety. With the new --dry-run flag, you can get a detailed summary of exactly what resources will be created, updated, or deleted before you run an import. This brings the confidence of infrastructure-as-code practices like terraform plan to your Auth0 tenant management.
Get started by simply adding the --dry-run flag to your import command to see a safe preview of your changes.
This will help you and your team:
The Dry Run feature is now available in Early Access. Update to the latest version of the Deploy CLI to get started.
One of the most requested features for the Auth0 Deploy CLI is here: you can now preview your deployment changes before applying them.
Say goodbye to deployment anxiety. With the new --dry-run flag, you can get a detailed summary of exactly what resources will be created, updated, or deleted before you run an import. This brings the confidence of infrastructure-as-code practices like terraform plan to your Auth0 tenant management.
Get started by simply adding the --dry-run flag to your import command to see a safe preview of your changes.
This will help you and your team:
The Dry Run feature is now available in Early Access. Update to the latest version of the Deploy CLI to get started.
One of the most requested features for the Auth0 Deploy CLI is here: you can now preview your deployment changes before applying them.
Say goodbye to deployment anxiety. With the new --dry-run flag, you can get a detailed summary of exactly what resources will be created, updated, or deleted before you run an import. This brings the confidence of infrastructure-as-code practices like terraform plan to your Auth0 tenant management.
Get started by simply adding the --dry-run flag to your import command to see a safe preview of your changes.
This will help you and your team:
The Dry Run feature is now available in Early Access. Update to the latest version of the Deploy CLI to get started.
What's new:
Non-Unique Emails is now in Open Early Access and rolling out to all environments. With this feature, multiple user accounts can share the same email address within a database connection. This enables support for real-world scenarios like:
Parent/child accounts using a shared inbox
Small businesses with a single location email
Users managing multiple roles under one email address
Key details:
Rollout has just begun and will take 1--4 weeks to reach every environment.
Available only for new database connections.
Email cannot be used as a primary identifier, customers must configure username or phone number.
Email communications will still be delivered to the shared email.
Once enabled, the non-unique email setting is permanent.
Status:
This feature is production-ready.
No opt-in required, all customers will gain access once rollout reaches their environment.
GA planned for Q4 2025.
Getting started:
Customers can create a new database connection with Non-Unique Emails in the Dashboard or via the Management API. See full documentation here:
Non-Unique Emails Documentation
What's new:
Non-Unique Emails is now in Open Early Access and rolling out to all environments. With this feature, multiple user accounts can share the same email address within a database connection. This enables support for real-world scenarios like:
Parent/child accounts using a shared inbox
Small businesses with a single location email
Users managing multiple roles under one email address
Key details:
Rollout has just begun and will take 1--4 weeks to reach every environment.
Available only for new database connections.
Email cannot be used as a primary identifier, customers must configure username or phone number.
Email communications will still be delivered to the shared email.
Once enabled, the non-unique email setting is permanent.
Status:
This feature is production-ready.
No opt-in required, all customers will gain access once rollout reaches their environment.
GA planned for Q4 2025.
Getting started:
Customers can create a new database connection with Non-Unique Emails in the Dashboard or via the Management API. See full documentation here:
Non-Unique Emails Documentation
What's new:
Non-Unique Emails is now in Open Early Access and rolling out to all environments. With this feature, multiple user accounts can share the same email address within a database connection. This enables support for real-world scenarios like:
Parent/child accounts using a shared inbox
Small businesses with a single location email
Users managing multiple roles under one email address
Key details:
Rollout has just begun and will take 1--4 weeks to reach every environment.
Available only for new database connections.
Email cannot be used as a primary identifier, customers must configure username or phone number.
Email communications will still be delivered to the shared email.
Once enabled, the non-unique email setting is permanent.
Status:
This feature is production-ready.
No opt-in required, all customers will gain access once rollout reaches their environment.
GA planned for Q4 2025.
Getting started:
Customers can create a new database connection with Non-Unique Emails in the Dashboard or via the Management API. See full documentation here:
Non-Unique Emails Documentation
What's new:
Non-Unique Emails is now in Open Early Access and rolling out to all environments. With this feature, multiple user accounts can share the same email address within a database connection. This enables support for real-world scenarios like:
Parent/child accounts using a shared inbox
Small businesses with a single location email
Users managing multiple roles under one email address
Key details:
Rollout has just begun and will take 1--4 weeks to reach every environment.
Available only for new database connections.
Email cannot be used as a primary identifier, customers must configure username or phone number.
Email communications will still be delivered to the shared email.
Once enabled, the non-unique email setting is permanent.
Status:
This feature is production-ready.
No opt-in required, all customers will gain access once rollout reaches their environment.
GA planned for Q4 2025.
Getting started:
Customers can create a new database connection with Non-Unique Emails in the Dashboard or via the Management API. See full documentation here:
Non-Unique Emails Documentation
What's new:
Non-Unique Emails is now in Open Early Access and rolling out to all environments. With this feature, multiple user accounts can share the same email address within a database connection. This enables support for real-world scenarios like:
Parent/child accounts using a shared inbox
Small businesses with a single location email
Users managing multiple roles under one email address
Key details:
Rollout has just begun and will take 1--4 weeks to reach every environment.
Available only for new database connections.
Email cannot be used as a primary identifier, customers must configure username or phone number.
Email communications will still be delivered to the shared email.
Once enabled, the non-unique email setting is permanent.
Status:
This feature is production-ready.
No opt-in required, all customers will gain access once rollout reaches their environment.
GA planned for Q4 2025.
Getting started:
Customers can create a new database connection with Non-Unique Emails in the Dashboard or via the Management API. See full documentation here:
Non-Unique Emails Documentation
What's new:
Non-Unique Emails is now in Open Early Access and rolling out to all environments. With this feature, multiple user accounts can share the same email address within a database connection. This enables support for real-world scenarios like:
Parent/child accounts using a shared inbox
Small businesses with a single location email
Users managing multiple roles under one email address
Key details:
Rollout has just begun and will take 1--4 weeks to reach every environment.
Available only for new database connections.
Email cannot be used as a primary identifier, customers must configure username or phone number.
Email communications will still be delivered to the shared email.
Once enabled, the non-unique email setting is permanent.
Status:
This feature is production-ready.
No opt-in required, all customers will gain access once rollout reaches their environment.
GA planned for Q4 2025.
Getting started:
Customers can create a new database connection with Non-Unique Emails in the Dashboard or via the Management API. See full documentation here:
Non-Unique Emails Documentation
What's new:
Non-Unique Emails is now in Open Early Access and rolling out to all environments. With this feature, multiple user accounts can share the same email address within a database connection. This enables support for real-world scenarios like:
Parent/child accounts using a shared inbox
Small businesses with a single location email
Users managing multiple roles under one email address
Key details:
Rollout has just begun and will take 1--4 weeks to reach every environment.
Available only for new database connections.
Email cannot be used as a primary identifier, customers must configure username or phone number.
Email communications will still be delivered to the shared email.
Once enabled, the non-unique email setting is permanent.
Status:
This feature is production-ready.
No opt-in required, all customers will gain access once rollout reaches their environment.
GA planned for Q4 2025.
Getting started:
Customers can create a new database connection with Non-Unique Emails in the Dashboard or via the Management API. See full documentation here:
Non-Unique Emails Documentation
What's new:
Non-Unique Emails is now in Open Early Access and rolling out to all environments. With this feature, multiple user accounts can share the same email address within a database connection. This enables support for real-world scenarios like:
Parent/child accounts using a shared inbox
Small businesses with a single location email
Users managing multiple roles under one email address
Key details:
Rollout has just begun and will take 1--4 weeks to reach every environment.
Available only for new database connections.
Email cannot be used as a primary identifier, customers must configure username or phone number.
Email communications will still be delivered to the shared email.
Once enabled, the non-unique email setting is permanent.
Status:
This feature is production-ready.
No opt-in required, all customers will gain access once rollout reaches their environment.
GA planned for Q4 2025.
Getting started:
Customers can create a new database connection with Non-Unique Emails in the Dashboard or via the Management API. See full documentation here:
Non-Unique Emails Documentation
We are pleased to announce that API Access Policies for Applications is now Generally Available (GA) for all Auth0 customers. This feature…
We are pleased to announce that API Access Policies for Applications is now Generally Available (GA) for all Auth0 customers. This feature…