v3.47.0
We are happy to announce release v3.47.0 of Elimity Insights, released on 10 September 2026.
Summary
This section summarizes the most important changes in release v3.47.0.
New functionality
MCP server support
The Elimity Insights MCP server makes an Elimity Insights tenant available to AI assistants through the Model Context Protocol. Users can then ask questions about their identity data from an MCP client (e.g. Claude Code, Claude Desktop, …) instead of clicking through the web application.
This release adds the platform side of that integration: the configuration options and authentication flow that the MCP server connects to. Both are stable and come with the same backwards compatibility guarantees as the rest of the platform.
The MCP server itself is a separate component: a stateless microservice that stores no data of its own and that fronts exactly one Elimity Insights tenant. It is still in testing and we expect to release it somewhere in October, so its tools can still change until then. Answers produced by an AI assistant are also not deterministic, so we don't recommend relying on them as evidence for audits or as input for automated processes yet.
Additional endpoint: GET /api/agent/stored-query-results;format=json
Elimity Insights now provides a new endpoint to list the results of a stored query as JSON. The endpoint takes the stored query's identifier in the required queryId query parameter and returns the identifier and name of every matching entity. It can be called using an API token.
Subscription count column
There now is an extra column in the stored query table showing how many notification channels are subscribed to each query. The count is also included in the Excel export. The column is only shown to users whose role allows them to see subscriptions.
Bug fixes & improvements
Tooltips for truncated values in data tables
Data table cells no longer hide values that are too large for the available column width. Hovering a cell now shows its full value in a tooltip.
API errors are now reported in the interface
Elimity Insights now reports failing API calls in a snackbar containing the error returned by the server, instead of a generic message per screen. This makes it clear why an action did not succeed.
Duplicate query subscriptions are now prevented
Adding a subscription that is identical to an existing subscription of the same stored query is no longer possible.
Stored query table columns : 'scope', 'results' and 'public' are click-to-sort now
The columns 'scope', 'results' and 'public' can now be sorted in the stored query table by clicking on the corresponding column titles.
Archived sources don't show up on the dashboard
Archived sources are now hidden on the dashboard.
Summary cards of archived sources are now hidden in the dialog.
Reordering tiles now shows the source name of summary cards.
Typo in the 'add card' dialog was corrected.
Minor bug fixes & improvements
As always, this new release brings some smaller bug fixes and improvements:
Fixed an issue where the interface could break after refreshing the page.
More sortable columns: the 'scope', 'results' and 'public' columns are click-to-sort now.
A name is now required when creating or editing a scope or an access profile.
A logout button was added to the setup screen, so users can log out when they don't have any imports yet.
The Entra ID built-in connector now includes a new 'employee type' attribute type for users.
The DocuSign built-in connector no longer drops the relationships between users and their permission profiles.
The 'download overview' button on the scope detail page now exports correctly.
The 'column entities' step of the access review wizard now shows the actual number of included column entities.
The icon of an entity type now follows that entity type when reordering entity types of a custom connector.
The paginators of the change requests and user accounts pages no longer scroll out of view together with the table.
Due to an update of our internal toolchain, requests bigger than 32MB failed. This is now fixed.
Migration information
To migrate from v3.46.x to v3.47.0, we suggest the following steps:
Make a backup of your existing database.
Make a backup of your existing installation directory.
Upgrade your installation by bumping the container image version.
Migrate your database, as described in our dedicated documentation.
Start the server and validate that it works as before.
Last updated