> 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/products/cloud-services/accessnow.md).

# AccessNow

Automate physical identity and access workflows with AccessNow.

AccessNow is Gallagher's **PIAM** (Physical Identity and Access Management) product, a cloud-native SaaS layer that automates the lifecycle of physical identities and their access: requests, approvals, and provisioning. It sits above raw access control. Command Centre grants the access; AccessNow governs who should get it and runs the workflow to make it happen. It is sold as an **annual subscription** with a two-part price: workflows plus request packs.

## What it is

AccessNow streamlines and automates the process of granting access to physical spaces. As a PIAM system it focuses on managing the **lifecycle** of physical identities and their access, enhancing security and compliance while providing a seamless user experience.

By leveraging cloud-native technology, AccessNow delivers access management through automated **requests, approvals, and provisioning**, rather than manual administration in the access-control client.

## Licensing

AccessNow is provided as an **annual subscription service** with a two-part pricing structure:

> **Workflows + Request Packs = Annual Cost**

<table><thead><tr><th width="269">Item</th><th width="88">Part #</th><th>Description</th></tr></thead><tbody><tr><td>AccessNow Workflow</td><td><strong>C16110</strong></td><td>A step-by-step process used for tasks such as issuing credentials or granting access to secure spaces. Each workflow includes a small request pack.</td></tr><tr><td>AccessNow small request pack</td><td><strong>C16111</strong></td><td>1,000 requests. Requests are shared across workflows.</td></tr><tr><td>AccessNow large request pack</td><td><strong>C16112</strong></td><td>30,000 requests. Requests are shared across workflows.</td></tr></tbody></table>

**Key mechanics:**

* A **workflow** is the unit of automation, for example "issue a contractor credential" or "grant access to a secure lab".
* **Requests** are consumed as the workflows run, and are **pooled across all workflows** on the subscription, not ring-fenced per workflow.
* Each workflow ships with a small request pack. Top up with small (1,000) or large (30,000) packs as volume grows.

## Learn more

* [AccessNow User Guide](https://help.security.gallagher.com/command-centre/)
* [AccessNow Training Module (SCORM)](https://scorm-modules.training-platform.security-training.gallagher.com/accessnowbuilder/content/index.html) - interactive e-learning module; opens in browser


---

# 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/products/cloud-services/accessnow.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.