> 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-user-guide/training/how-accessnow-works.md).

# How AccessNow works

Understand how AccessNow routes requests, approvals, and provisioning to Command Centre.

AccessNow is a cloud service that manages access requests for Command Centre. It routes requests for approval, then applies approved changes in Command Centre.

### Example request journey

1. A signed-in user selects **Make a Request** and chooses a workflow, such as requesting access to an area.
2. AccessNow **matches the requester to their Command Centre cardholder record**. It uses a unique identifier, usually an email address.
3. AccessNow **creates an approval task** for the approver group responsible for the requested area. It notifies the group by email.
4. When the request is approved, the workflow **applies the required change in Command Centre**. For example, it can add an access group or create a credential.
5. AccessNow **emails the outcome** to the requester. It also records each stage in the user's activity history.

### Required connections

These connections support each request. A request can fail when one is not configured correctly.

<table><thead><tr><th width="206.86297607421875">Link</th><th width="533.2125244140625">What it connects</th></tr></thead><tbody><tr><td>Person ↔ cardholder</td><td>An AccessNow user and their Command Centre cardholder, matched by a unique Personal Data Field (PDF), such as email</td></tr><tr><td>Area ↔ Access Group ↔ Approver group</td><td>The available request, the Command Centre access it grants, and the group that approves it</td></tr><tr><td>Workflow ↔ template</td><td>The request form, approval stages, and Command Centre actions for a request type</td></tr></tbody></table>

### AccessNow modules

<table><thead><tr><th width="185.98822021484375">Module</th><th width="180.370361328125">Primary users</th><th>Purpose</th></tr></thead><tbody><tr><td><strong>Make a Request</strong></td><td>Everyone</td><td>Submit an access request</td></tr><tr><td><strong>Requests</strong> and <strong>My Requests</strong></td><td>Requesters</td><td>View request status and history</td></tr><tr><td><strong>Tasks</strong></td><td>Approvers</td><td>Approve, amend, or reject requests</td></tr><tr><td><strong>Areas</strong></td><td>Approvers</td><td>Manage area approvers and review current access</td></tr><tr><td><strong>Users</strong>, <strong>Groups</strong>, and <strong>Roles</strong></td><td>Administrators</td><td>Manage sign-in access and permissions</td></tr><tr><td><strong>Lists</strong></td><td>Administrators</td><td>Manage access groups, PDFs, card types, divisions, and custom drop-down lists</td></tr><tr><td><strong>Email Templates</strong></td><td>Administrators</td><td>Customize notification content and branding</td></tr><tr><td><strong>Workflow Builder</strong></td><td>Workflow managers</td><td>Create, import, edit, version, and publish workflows</td></tr><tr><td><strong>Workflow Management</strong></td><td>Workflow managers</td><td>Run test versions and control published-workflow visibility</td></tr><tr><td><strong>Settings</strong></td><td>Administrators</td><td>Configure the Command Centre connection, Area Management, and branding</td></tr></tbody></table>


---

# 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-user-guide/training/how-accessnow-works.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.
