Multi-Tenant Access and Multiple Auth Providers
The August 2026 weekly v2026.8.3 release adds support for belonging to multiple tenants under the same DNS namespace and switching between them. Tenant admins can invite people regardless of email domain and allow multiple authentication providers within one tenant.
Aiden integrations, workspace chat, alert filters, LLM testing, and Jira intake updates are in Aiden v2026.8.3.
Explore the sections below to see what's new and enhanced in this update.
| Feature | Link | |
|---|---|---|
| What's New | Platform | Multi-Tenant Access and Cross-Domain Invites |
| What's Enhanced | Platform | Multiple Auth Providers Within a Tenant |
What's New
Multi-Tenant Access and Cross-Domain Invites
Click to view
Tenancy and authentication changes are rolling out gradually. Not every environment has multi-tenant switching enabled yet (for example some shared demo environments may still be single-tenant). Expect growing pains while this lands broadly. Contact support@stackgen.com or your Customer Service Manager if you need enablement.
We've added the ability to belong to multiple tenants under the same DNS namespace and to invite people into a tenant regardless of their email domain.
Previously, getting StackGen or Aiden staff into a customer environment often meant joining the customer IdP (for example Entra), and shared demo tenants made it hard to keep isolated demo data. Now, where enabled, you can switch between tenants you belong to, and tenant admins can invite collaborators (for example CS or SE) directly in product without requiring the same email domain.
Key Features
- Multi-Tenant Membership - One login under a DNS namespace can belong to more than one tenant. Switch enterprises or tenants from the UI when the feature is enabled for that environment.
- Cross-Domain Invites - Invite users into a tenant even when their email domain differs from the tenant’s usual domain.
- Org Admin vs User Affordance - The UI distinguishes org admin from regular user membership on the tenant switcher (icon difference).
Why It Matters
Field and CS teams can get isolated tenants for demos or PoCs, and customers can invite StackGen helpers into their tenant without IdP onboarding as the only path.
Read more in StackGen Settings and Navigating UI.
What's Enhanced
Multiple Auth Providers Within a Tenant
Click to view
We've enhanced tenant authentication so a single tenant can allow more than one authentication provider.
Previously, v2026.7.7 covered linking multiple providers to the same account so PoC and production logins did not fork into separate tenants. Now, a tenant can enable multiple providers side by side (for example Google for invited StackGen staff and Entra ID for the customer), and each person authenticates with the provider the tenant allows for them.
Key Features
- Per-Tenant Multi-Provider - Enable more than one auth provider on the same tenant.
- Invite Without Shared IdP - Customer admins can allow an alternate provider so invited collaborators sign in without joining the customer IdP.
- Customer-Controlled Access - The customer still has to allow the provider path you will use. There is no bypass of tenant authentication policy.
Current Constraints
- Custom OAuth (client ID and secret) setup for some providers can still be a manual StackGen-assisted process. More self-serve auth configuration is planned.
- OTP-based and fuller self-serve PoC tenant flows called out as follow-ups are not the focus of this cut.
Why It Matters
PoCs and support engagements can mix customer SSO with an alternate login for invited helpers, without forcing everyone onto one IdP.
Read more in Multiple Authentication Providers (v2026.7.7), StackGen Settings, and Microsoft Entra ID (Azure AD) OAuth.