Skip to content

Release 2026-03-29 (1.88.0–1.92.0)

Backend: 1.166.0–1.169.0
Frontend: 1.88.0–1.92.0
Release period: 2026-03-20 to 2026-03-29

Sub-processor transparency in AI model tables

Section titled “Sub-processor transparency in AI model tables”

Each AI model in the admin panel now includes a dedicated Sub-processor column. This shows which company directly processes data when a given model is used. For models accessed via external APIs, this is the respective model vendor. For models hosted by Intric, it reflects the underlying infrastructure provider.

Space administrators can now grant a specific user editing access to a single assistant, without giving that user broader access to the rest of the space. To add a collaborator, open the assistant settings and add a space member from there. This is the first step toward more precise, assistant-level permission management.

ℹ️ This feature is currently available in V4 of Intric. Both permission systems are running in parallel during the transition.

All tables in the administration section now include an export button in the table footer. Click it to download the full table as a CSV file — useful for reporting, auditing, or further analysis.

Files that have been uploaded but not yet sent in a conversation are now preserved if your session expires or you close the browser tab. When you return, you will be prompted to recover or discard any pending files — so no upload is lost by accident.

The Usage section now includes a new table showing token consumption broken down by user group, in addition to the existing per-model breakdown. Navigate to Usage > Tokens and scroll down to find the new table.

GPT 5.4 is now available. Administrators can activate it under Administration > AI Models.

Org-wide administrators now see spaces and their content as regular users do when browsing the platform — only content they have membership access to will appear. Full administrative access remains available through the admin section.


🔴 Breaking change — self-managed Zitadel installations only

If your organization manages its own Zitadel authentication instance (not managed by Intric), you must update the access token type to JWT format in your Zitadel login application configuration. Login will not function correctly until this change is made.

Organizations using Intric’s managed Zitadel instance are not affected.

⚠️ Breaking change — manual action required

Action required: within a week

Contact support@intric.ai if you need help with this upgrade.