> 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/2025/june.md).

# June

Version d9ee3f8

**Date applied:** 27/06/2025

## Changes Implemented

### **New Features**

#### [Host a Visitor Workflow](/knowledge-hub/accessnow-release-notes/2025/june/host-a-visitor-workflow.md)

The workflow creates visitor records in Gallagher Command Centre Visitor Management. It also lets users edit visit details and mark visits as cancelled or completed.

#### Add a non-SSO AccessNow user

While most users are created automatically in AccessNow through Single Sign-On (SSO), you can now manually create accounts needed for initial system configuration. Visit the user guide to learn how to [manage users in AccessNow](/knowledge-hub/accessnow-user-guide/system-administration/user-management.md).

**Prerequisites**

Most workflow templates require the user to exist as a cardholder in Command Centre. Before making requests, create the user in Command Centre.

### **User Experience Improvements**

* Improved usability of the Roles module
* Pagination bar for the request and approval tabs in the user activity log.
* Landing page for failed requests.
* Reordered tabs in the mobile interface.


---

# 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/2025/june.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.