v26.08-2 Release Note

Countdown — 2 months remaining for API Change!

We would like to remind all users about upcoming API changes related to the ongoing infrastructure migration. These changes will be rolled out gradually until October 2026.
Please review the updated API documentation and ensure your integrations remain compatible throughout the transition period.

Knowledge Base Article: Update to Parashift API & Domains.

Changes to Tenant Security Management

We’ve reorganized Tenant & User to make tenant configuration clearer and give administrators more control over how users authenticate and access the platform.

The previous Tenant & User area is now divided into four sections based on their purpose:

General — Manage the tenant name and branding, including the logo and colors.
Security — check authentication methods, IP whitelisting, and URL integration settings.
Hierarchy — View the current tenant hierarchy.
Users — Manage existing users, pending invitations, and user permissions.

What’s new in Tenant Security?

The new Security model gives you more flexibility in deciding how your tenant and its users are protected

Choose how users authenticate

You can now choose how users within your tenant and its hierarchy authenticate when signing in.

Depending on your security requirements, you can choose from:

Password
Password + Two-Factor Authentication (2FA)
Single Sign-On (SSO)

These authentication methods can be used individually or combined. For example, you can enable SSO alongside Email + Password and 2FA, giving users multiple available ways to authenticate.

SSO is now configured at the tenant level

One of the most important changes is how Single Sign-On (SSO) configuration works.

Previously, SSO configuration applied to the entire tenant hierarchy. With the new security management model, SSO is configured at the individual tenant level.

This means different tenants within the same hierarchy can use different SSO providers.

For example, if your hierarchy contains multiple customer tenants, each customer can use an SSO provider that matches their own identity and access management setup.

Example

A hierarchy could now be configured as follows:

Parent tenant → SSO Provider A
Customer Tenant 1 → SSO Provider B
Customer Tenant 2 → SSO Provider C
Customer Tenant 3 → Password + 2FA

This provides greater flexibility for organizations managing multiple customers, business units, or environments with different authentication requirements.

Learn more: Tenant Security Management

Need Help?

Have questions or need advice or assistance with configuration? Our support team is here to help.