> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/accessnow-release-notes/2026/september.md).

# September

Latest release 3b69b09 on 30 September 2026

{% hint style="success" %}

## Feature improvement

**Date applied: 30 September 2026**

### Original Command Centre access group names retained

Administrators can now see the original Command Centre entity name, such as an Access Group name, after changing it in AccessNow. Access Group and Card Type names can be changed in AccessNow to more user-friendly names. The user-friendly name is now visible next to the original Command Centre name.
{% endhint %}

<div data-with-frame="true"><figure><img src="https://1641710072-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFBryEHtepuLw1MCVX9e4%2Fuploads%2FQNNNf9dcoknYf94MKKy6%2FScreenshot%202026-10-01%20at%2016.00.10.png?alt=media&amp;token=f3809f51-3b83-4d3a-b6e7-0b5cbfaf8042" alt=""><figcaption></figcaption></figure></div>

{% hint style="success" %}

## Feature improvement

**Date applied: 30 September 2026**

### Support for Command Centre unique identifiers

Administrators can now select only PDFs marked as Unique in Command Centre when configuring a unique requester/cardholder identifier. Additional validation and user messaging help administrators quickly identify when no unique PDF is defined in Command Centre. Learn more about [Command Centre unique identifiers](/knowledge-hub/accessnow-user-guide/system-administration/command-centre-integration/set-command-centre-unique-identifiers.md).
{% endhint %}

<figure><img src="https://1641710072-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFBryEHtepuLw1MCVX9e4%2Fuploads%2FKkPOI7EgnAcLrvruhk65%2Fimage.png?alt=media&amp;token=6a519c25-7bad-412a-9737-e75ef917c76e" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}

## Feature improvement

**Date applied: 30 September 2026**

### Improved workflow visualisation and configuration for complex approval processes

**Workflow diagram clarity**

Workflow diagrams now provide a clearer representation of multi-approval workflows, making it easier for administrators to understand approval paths and configure complex templates.
{% endhint %}

<figure><img src="https://1641710072-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFBryEHtepuLw1MCVX9e4%2Fuploads%2FAVOV4VoBOZQmkEOCJ7Pd%2Fimage.png?alt=media&amp;token=8d446081-713d-4bc3-90e9-d072c661b7bf" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}

## Feature improvement

**Date applied: 30 September 2026**

### Improved workflow data initialisation configuration

Workflow builder controls have been refined with updated dropdown styling and improved handling of required-field indicators, creating a more intuitive and consistent administration experience.
{% endhint %}

<figure><img src="https://1641710072-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFBryEHtepuLw1MCVX9e4%2Fuploads%2F7EiBfemtv7V79kOWSRXw%2Fimage.png?alt=media&amp;token=082175f0-2ac8-4403-bac0-825c8f8df52e" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}

## Feature release

**Date applied: 3 September 2026**

### Custom branding and colours

Customers can now apply their own branding and colours in **Settings**.
{% endhint %}

> ### Security patch and maintenance
>
> **Date applied: 3 September 2026**<br>
>
> **Security patches applied**
>
> * Next.js — `CVE-2026-75604` and `GHSA-2xp9-vwfh-vxw4`
>
> \
> **Maintenance updates**\
> \
> Backend system improvements and bug fixes


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/accessnow-release-notes/2026/september.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.