> For the complete documentation index, see [llms.txt](https://docs.elimity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elimity.com/release-notes/v3.44.0.md).

# v3.44.0

We are happy to announce release v3.44.0 of Elimity Insights, released on 19 March 2026.

## Summary

This section summarizes the most important changes in release v3.44.0.

<details>

<summary>New functionality</summary>

* Configure visible attribute types for access reviews
* Support for editing campaign names and due dates
* Support for configuring the access review toolbar text color

</details>

<details>

<summary>Bug fixes &#x26; improvements</summary>

* Access profiles no longer apply for access reviews and access review managers
* Support authenticating to Postgres via Azure Managed Identity
* Support reading configuration from a config file for the migration CLI
* Minor bug fixes & improvements

</details>

<details>

<summary>Deployment changes</summary>

* Required update of the SharePoint and Jira Data Center gateways
* Added support for reading configuration from a single environment variable or file
* Official support for Postgres 15 and 17

</details>

## New functionality <a href="#h_01h9mxgpqsnkh8tpyx32gwcbsr" id="h_01h9mxgpqsnkh8tpyx32gwcbsr"></a>

### Configure visible attribute types for access reviews

Elimity Insights v3.44.0 includes support for configuring visible attribute types for access reviews. You can now manage and select visible attribute types directly when creating access reviews. This functionality is also available in the campaign template creation wizard and when editing campaign templates.

<figure><img src="https://2067057569-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7b6iwtH0Lr9Z5pj9MCO2%2Fuploads%2FRr9a4jpDebnHwJfWVz64%2FScreenshot%202026-02-26%20at%2015-15-05%20Elimity.png?alt=media&amp;token=519e7590-bbb8-4900-a317-5a5db0f48e63" alt=""><figcaption></figcaption></figure>

### Support for editing campaign names and due dates

In this release, campaign names and due dates can now be easily edited after a campaign has been created.

<figure><img src="https://2067057569-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7b6iwtH0Lr9Z5pj9MCO2%2Fuploads%2FIhvOd5TsEx8BU9btURZc%2FScreenshot%202026-02-26%20at%2015-15-30%20Elimity.png?alt=media&amp;token=0946bf82-c147-4b52-bdb7-7eb03aa9ae44" alt=""><figcaption></figcaption></figure>

### Support for configuring the access review toolbar text color

The v3.44.0 release includes support for configuring the text color of the access review toolbar. You can now add the `accessReviewToolbarTextColor` configuration option to your `config.hjson` file. This works similarly to the existing `accessReviewToolbarBackgroundColor` option and defaults to white.

## Bug fixes & improvements

### Access profiles no longer apply for access reviews and access review managers

Access profiles no longer apply to access reviews. Users assigned the Access Review Manager role can now fully manage access reviews and campaigns, bypassing any previous access profile restrictions. This also means that access review managers can view identity data for all sources, so make sure to reassign roles as needed before you upgrade.

### Support authenticating to Postgres via Azure Managed Identity

For customers deploying in Azure environments, Elimity Insights now supports authenticating to your Postgres database using Azure Managed Identity, streamlining credentials management.

To enable this feature, simply set the `pgAzureManagedIdentity` flag to `true` in your `config.hjson` file. When enabled, Elimity Insights will retrieve an access token from Azure and use it as a password for authentication with PostgreSQL.

### Support reading configuration from a config file for the migration CLI&#x20;

To simplify the [database migration](/reference-manual/installation/elimity-insights-server.md#upgrades) process, the migration CLI now supports reading configuration from a `config.json` file instead of requiring lengthy command-line arguments.

### Minor bug fixes & improvements <a href="#h_01js1h4hg2ekpaqj0a5kpn1hc0" id="h_01js1h4hg2ekpaqj0a5kpn1hc0"></a>

As always, this new release brings some smaller bug fixes and improvements:

* Added 'Created by' column to the table of access reviews on the campaign details page; previously you could only find this information on the access review details page.
* Fixed an issue where filtering descriptions for data tables on entity detail pages showed incorrect counts.
* The [Entra ID built-in connector](/reference-manual/built-in-connectors/azure-ad.md) now includes 'app' and 'LastSuccessfulSignInDateTime' attribute types.
* We've added a few enhancements for the [SharePoint built-in connector](/reference-manual/built-in-connectors/sharepoint.md):
  * you can exclude files based on a configurable glob pattern, and
  * we added some extra attributes for each imported site.
* Customers using our [SCIM built-in connector](/reference-manual/built-in-connectors/scim.md) can now provide a bearer token instead of username and password for authentication.

## Deployment changes

### Required update of the SharePoint and Jira Data Center gateways <a href="#required-update-of-the-ntfs-gateway" id="required-update-of-the-ntfs-gateway"></a>

Customers using the [SharePoint](/gateways-sharepoint/step-by-step-deployment-guide.md) and [Jira Data Center](/gateways-jira-data-center/step-by-step-deployment-guide.md) built-in connectors must update their gateways to major versions 5 and 3 respectively.

### Added support for reading configuration from a single environment variable or file

Previously, configurations and secrets were split across two separate files (`elimity.yml` and `secrets.yml`).

Moving forward, you can consolidate your entire configuration into a single `config.hjson` file. Alternatively you can pass this unified configuration using a single new environment variable: `INSIGHTS_CONFIG_HJSON`. See [our dedicated documentation](/reference-manual/server-configuration.md) for more information.\
\
Please note that this will be the last release to support YAML file configuration.

### Official support for Postgres 15 and 17

Elimity Insights now officially supports PostgreSQL 15 and 17.&#x20;

Please note that this will be the last release to support PostgreSQL 15.

## Migration information <a href="#h_01h9mxgpqs599yv2hb64zhwdk9" id="h_01h9mxgpqs599yv2hb64zhwdk9"></a>

To migrate from v3.43.x to v3.44.0, we suggest the following steps:

1. Make a backup of your existing database.
2. Make a backup of your existing installation directory.
3. Upgrade your installation by bumping the container image version.
4. Migrate your database, as described in [our dedicated documentation](/reference-manual/installation/elimity-insights-server.md#upgrades).
5. Start the server and validate that it works as before.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.elimity.com/release-notes/v3.44.0.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.