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
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 excited to announce a major update for our Private Cloud customers, extending the powerful management and security capabilities of Auth0 Teams to your private cloud environments. This release introduces the Beta versions of Tenant Member Management and SSO Enforcement, closing the feature gap with our Public Cloud offering.
Tenant Member Management (Beta) for Private Cloud:
You can now centrally manage tenant membership and roles for your team members directly from the Auth0 Teams dashboard. This feature simplifies user administration by allowing you to:
SSO Enforcement (Beta) for Private Cloud:
Strengthen your organization's security posture by requiring all team and tenant members to authenticate using one of your configured Enterprise Identity Provider (IdP) connections. This ensures that access to Auth0 resources is governed by your corporate identity solution.
Activity Log Integration for Tenant Management:
All operations related to Tenant Member Management (e.g., adding, updating or deleting) are now recorded in the Auth0 Teams Activity Log, providing a complete audit trail for compliance and security monitoring. (Note Now available to all Auth0 Teams customers.)
Session Revocation for Private Cloud:
Administrators now have the ability to revoke active user sessions for Private Cloud tenants, providing an immediate way to off-board users or respond to security events.
Streamlined Private Cloud User Invites:
Team members can now be invited directly to a Private Cloud tenant through the Teams interface. This removes the previous requirement of first adding the user to the configuration tenant, simplifying and accelerating the onboarding workflow.
Increased Bulk Tenant:
The limit for bulk tenant assignment has been doubled, allowing you to grant or modify access to 10 tenants at once, up from the previous limit of 5.
Tenant Member Management and SSO Enforcement features for Private Cloud are being released in Beta.
We are excited to announce a major update for our Private Cloud customers, extending the powerful management and security capabilities of Auth0 Teams to your private cloud environments. This release introduces the Beta versions of Tenant Member Management and SSO Enforcement, closing the feature gap with our Public Cloud offering.
Tenant Member Management (Beta) for Private Cloud:
You can now centrally manage tenant membership and roles for your team members directly from the Auth0 Teams dashboard. This feature simplifies user administration by allowing you to:
SSO Enforcement (Beta) for Private Cloud:
Strengthen your organization's security posture by requiring all team and tenant members to authenticate using one of your configured Enterprise Identity Provider (IdP) connections. This ensures that access to Auth0 resources is governed by your corporate identity solution.
Activity Log Integration for Tenant Management:
All operations related to Tenant Member Management (e.g., adding, updating or deleting) are now recorded in the Auth0 Teams Activity Log, providing a complete audit trail for compliance and security monitoring. (Note Now available to all Auth0 Teams customers.)
Session Revocation for Private Cloud:
Administrators now have the ability to revoke active user sessions for Private Cloud tenants, providing an immediate way to off-board users or respond to security events.
Streamlined Private Cloud User Invites:
Team members can now be invited directly to a Private Cloud tenant through the Teams interface. This removes the previous requirement of first adding the user to the configuration tenant, simplifying and accelerating the onboarding workflow.
Increased Bulk Tenant:
The limit for bulk tenant assignment has been doubled, allowing you to grant or modify access to 10 tenants at once, up from the previous limit of 5.
Tenant Member Management and SSO Enforcement features for Private Cloud are being released in Beta.
We are excited to announce a major update for our Private Cloud customers, extending the powerful management and security capabilities of Auth0 Teams to your private cloud environments. This release introduces the Beta versions of Tenant Member Management and SSO Enforcement, closing the feature gap with our Public Cloud offering.
Tenant Member Management (Beta) for Private Cloud:
You can now centrally manage tenant membership and roles for your team members directly from the Auth0 Teams dashboard. This feature simplifies user administration by allowing you to:
SSO Enforcement (Beta) for Private Cloud:
Strengthen your organization's security posture by requiring all team and tenant members to authenticate using one of your configured Enterprise Identity Provider (IdP) connections. This ensures that access to Auth0 resources is governed by your corporate identity solution.
Activity Log Integration for Tenant Management:
All operations related to Tenant Member Management (e.g., adding, updating or deleting) are now recorded in the Auth0 Teams Activity Log, providing a complete audit trail for compliance and security monitoring. (Note Now available to all Auth0 Teams customers.)
Session Revocation for Private Cloud:
Administrators now have the ability to revoke active user sessions for Private Cloud tenants, providing an immediate way to off-board users or respond to security events.
Streamlined Private Cloud User Invites:
Team members can now be invited directly to a Private Cloud tenant through the Teams interface. This removes the previous requirement of first adding the user to the configuration tenant, simplifying and accelerating the onboarding workflow.
Increased Bulk Tenant:
The limit for bulk tenant assignment has been doubled, allowing you to grant or modify access to 10 tenants at once, up from the previous limit of 5.
Tenant Member Management and SSO Enforcement features for Private Cloud are being released in Beta.
We are excited to announce a major update for our Private Cloud customers, extending the powerful management and security capabilities of Auth0 Teams to your private cloud environments. This release introduces the Beta versions of Tenant Member Management and SSO Enforcement, closing the feature gap with our Public Cloud offering.
Tenant Member Management (Beta) for Private Cloud:
You can now centrally manage tenant membership and roles for your team members directly from the Auth0 Teams dashboard. This feature simplifies user administration by allowing you to:
SSO Enforcement (Beta) for Private Cloud:
Strengthen your organization's security posture by requiring all team and tenant members to authenticate using one of your configured Enterprise Identity Provider (IdP) connections. This ensures that access to Auth0 resources is governed by your corporate identity solution.
Activity Log Integration for Tenant Management:
All operations related to Tenant Member Management (e.g., adding, updating or deleting) are now recorded in the Auth0 Teams Activity Log, providing a complete audit trail for compliance and security monitoring. (Note Now available to all Auth0 Teams customers.)
Session Revocation for Private Cloud:
Administrators now have the ability to revoke active user sessions for Private Cloud tenants, providing an immediate way to off-board users or respond to security events.
Streamlined Private Cloud User Invites:
Team members can now be invited directly to a Private Cloud tenant through the Teams interface. This removes the previous requirement of first adding the user to the configuration tenant, simplifying and accelerating the onboarding workflow.
Increased Bulk Tenant:
The limit for bulk tenant assignment has been doubled, allowing you to grant or modify access to 10 tenants at once, up from the previous limit of 5.
Tenant Member Management and SSO Enforcement features for Private Cloud are being released in Beta.
We are excited to announce a major update for our Private Cloud customers, extending the powerful management and security capabilities of Auth0 Teams to your private cloud environments. This release introduces the Beta versions of Tenant Member Management and SSO Enforcement, closing the feature gap with our Public Cloud offering.
Tenant Member Management (Beta) for Private Cloud:
You can now centrally manage tenant membership and roles for your team members directly from the Auth0 Teams dashboard. This feature simplifies user administration by allowing you to:
SSO Enforcement (Beta) for Private Cloud:
Strengthen your organization's security posture by requiring all team and tenant members to authenticate using one of your configured Enterprise Identity Provider (IdP) connections. This ensures that access to Auth0 resources is governed by your corporate identity solution.
Activity Log Integration for Tenant Management:
All operations related to Tenant Member Management (e.g., adding, updating or deleting) are now recorded in the Auth0 Teams Activity Log, providing a complete audit trail for compliance and security monitoring. (Note Now available to all Auth0 Teams customers.)
Session Revocation for Private Cloud:
Administrators now have the ability to revoke active user sessions for Private Cloud tenants, providing an immediate way to off-board users or respond to security events.
Streamlined Private Cloud User Invites:
Team members can now be invited directly to a Private Cloud tenant through the Teams interface. This removes the previous requirement of first adding the user to the configuration tenant, simplifying and accelerating the onboarding workflow.
Increased Bulk Tenant:
The limit for bulk tenant assignment has been doubled, allowing you to grant or modify access to 10 tenants at once, up from the previous limit of 5.
Tenant Member Management and SSO Enforcement features for Private Cloud are being released in Beta.
We are excited to announce a major update for our Private Cloud customers, extending the powerful management and security capabilities of Auth0 Teams to your private cloud environments. This release introduces the Beta versions of Tenant Member Management and SSO Enforcement, closing the feature gap with our Public Cloud offering.
Tenant Member Management (Beta) for Private Cloud:
You can now centrally manage tenant membership and roles for your team members directly from the Auth0 Teams dashboard. This feature simplifies user administration by allowing you to:
SSO Enforcement (Beta) for Private Cloud:
Strengthen your organization's security posture by requiring all team and tenant members to authenticate using one of your configured Enterprise Identity Provider (IdP) connections. This ensures that access to Auth0 resources is governed by your corporate identity solution.
Activity Log Integration for Tenant Management:
All operations related to Tenant Member Management (e.g., adding, updating or deleting) are now recorded in the Auth0 Teams Activity Log, providing a complete audit trail for compliance and security monitoring. (Note Now available to all Auth0 Teams customers.)
Session Revocation for Private Cloud:
Administrators now have the ability to revoke active user sessions for Private Cloud tenants, providing an immediate way to off-board users or respond to security events.
Streamlined Private Cloud User Invites:
Team members can now be invited directly to a Private Cloud tenant through the Teams interface. This removes the previous requirement of first adding the user to the configuration tenant, simplifying and accelerating the onboarding workflow.
Increased Bulk Tenant:
The limit for bulk tenant assignment has been doubled, allowing you to grant or modify access to 10 tenants at once, up from the previous limit of 5.
Tenant Member Management and SSO Enforcement features for Private Cloud are being released in Beta.
We are excited to announce a major update for our Private Cloud customers, extending the powerful management and security capabilities of Auth0 Teams to your private cloud environments. This release introduces the Beta versions of Tenant Member Management and SSO Enforcement, closing the feature gap with our Public Cloud offering.
Tenant Member Management (Beta) for Private Cloud:
You can now centrally manage tenant membership and roles for your team members directly from the Auth0 Teams dashboard. This feature simplifies user administration by allowing you to:
SSO Enforcement (Beta) for Private Cloud:
Strengthen your organization's security posture by requiring all team and tenant members to authenticate using one of your configured Enterprise Identity Provider (IdP) connections. This ensures that access to Auth0 resources is governed by your corporate identity solution.
Activity Log Integration for Tenant Management:
All operations related to Tenant Member Management (e.g., adding, updating or deleting) are now recorded in the Auth0 Teams Activity Log, providing a complete audit trail for compliance and security monitoring. (Note Now available to all Auth0 Teams customers.)
Session Revocation for Private Cloud:
Administrators now have the ability to revoke active user sessions for Private Cloud tenants, providing an immediate way to off-board users or respond to security events.
Streamlined Private Cloud User Invites:
Team members can now be invited directly to a Private Cloud tenant through the Teams interface. This removes the previous requirement of first adding the user to the configuration tenant, simplifying and accelerating the onboarding workflow.
Increased Bulk Tenant:
The limit for bulk tenant assignment has been doubled, allowing you to grant or modify access to 10 tenants at once, up from the previous limit of 5.
Tenant Member Management and SSO Enforcement features for Private Cloud are being released in Beta.
We are excited to announce a major update for our Private Cloud customers, extending the powerful management and security capabilities of Auth0 Teams to your private cloud environments. This release introduces the Beta versions of Tenant Member Management and SSO Enforcement, closing the feature gap with our Public Cloud offering.
Tenant Member Management (Beta) for Private Cloud:
You can now centrally manage tenant membership and roles for your team members directly from the Auth0 Teams dashboard. This feature simplifies user administration by allowing you to:
SSO Enforcement (Beta) for Private Cloud:
Strengthen your organization's security posture by requiring all team and tenant members to authenticate using one of your configured Enterprise Identity Provider (IdP) connections. This ensures that access to Auth0 resources is governed by your corporate identity solution.
Activity Log Integration for Tenant Management:
All operations related to Tenant Member Management (e.g., adding, updating or deleting) are now recorded in the Auth0 Teams Activity Log, providing a complete audit trail for compliance and security monitoring. (Note Now available to all Auth0 Teams customers.)
Session Revocation for Private Cloud:
Administrators now have the ability to revoke active user sessions for Private Cloud tenants, providing an immediate way to off-board users or respond to security events.
Streamlined Private Cloud User Invites:
Team members can now be invited directly to a Private Cloud tenant through the Teams interface. This removes the previous requirement of first adding the user to the configuration tenant, simplifying and accelerating the onboarding workflow.
Increased Bulk Tenant:
The limit for bulk tenant assignment has been doubled, allowing you to grant or modify access to 10 tenants at once, up from the previous limit of 5.
Tenant Member Management and SSO Enforcement features for Private Cloud are being released in Beta.
We are excited to announce a major update for our Private Cloud customers, extending the powerful management and security capabilities of Auth0 Teams to your private cloud environments. This release introduces the Beta versions of Tenant Member Management and SSO Enforcement, closing the feature gap with our Public Cloud offering.
Tenant Member Management (Beta) for Private Cloud:
You can now centrally manage tenant membership and roles for your team members directly from the Auth0 Teams dashboard. This feature simplifies user administration by allowing you to:
SSO Enforcement (Beta) for Private Cloud:
Strengthen your organization's security posture by requiring all team and tenant members to authenticate using one of your configured Enterprise Identity Provider (IdP) connections. This ensures that access to Auth0 resources is governed by your corporate identity solution.
Activity Log Integration for Tenant Management:
All operations related to Tenant Member Management (e.g., adding, updating or deleting) are now recorded in the Auth0 Teams Activity Log, providing a complete audit trail for compliance and security monitoring. (Note Now available to all Auth0 Teams customers.)
Session Revocation for Private Cloud:
Administrators now have the ability to revoke active user sessions for Private Cloud tenants, providing an immediate way to off-board users or respond to security events.
Streamlined Private Cloud User Invites:
Team members can now be invited directly to a Private Cloud tenant through the Teams interface. This removes the previous requirement of first adding the user to the configuration tenant, simplifying and accelerating the onboarding workflow.
Increased Bulk Tenant:
The limit for bulk tenant assignment has been doubled, allowing you to grant or modify access to 10 tenants at once, up from the previous limit of 5.
Tenant Member Management and SSO Enforcement features for Private Cloud are being released in Beta.