> 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/plan-your-deployment/accessnow-fit-assessment.md).

# AccessNow fit assessment

Assess whether a customer's Command Centre environment, workflows, and sign-in requirements suit AccessNow.

Review these requirements with the customer before requesting an account. A requirement that is not met does not always rule out AccessNow. Discuss it with Gallagher Security first.

### Command Centre requirements

| Question                                                             | Requirement                                                                                                                 |
| -------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| Which Command Centre version is in use?                              | Version 9.10 or later                                                                                                       |
| How many Command Centre servers need AccessNow?                      | One Command Centre server. One or more AccessNow tenancies can connect to it.                                               |
| Can requesters select access from a flat list of access groups?      | Yes. Access groups appear in one list. You can rename or hide them.                                                         |
| Does every cardholder have a unique field, such as an email address? | AccessNow looks up or creates Command Centre cardholders. It uses a unique identifier to match records between the systems. |

### Processes to automate

Discuss the following questions with the customer:

* What requests should people make, such as access, new credential, lost credential, or requests on behalf of others?
* What happens for each request today?
* Who approves requests for each area? Does this vary by site or division?
* Do different user groups need different workflows?

Document the answers by following [General Approach to Mapping Workflows](https://help.security.gallagher.com/knowledge-hub/accessnow-user-guide/intro-to-workflows/workflow-mapping/general-approach-to-mapping-workflows.md).

### Sign-in requirements

Every requester must sign in. AccessNow does not provide anonymous public request forms.

* **Staff:** Sign in through the customer's single sign-on (SSO) provider. Each tenancy supports one SSO provider.
* **Contractor managers and partners:** Use local AccessNow accounts with passwords and multi-factor authentication.
* **Contractors:** Appoint a contract manager to submit requests for their workers.

### Annual subscription

AccessNow is an **annual subscription.** Choose the workflows to automate and purchase a request pool shared across them throughout the year. There is no user limit. An **active Care Plan is required**.

Your Gallagher Security representative prepares the quote using the AccessNow ROI Calculator. They will ask:

* How many cardholders will use AccessNow? How many requests will each cardholder make each year? This may help assess the annual request pool required.
* What percentage of credentials are newly issued each year?
* What percentage of credentials are lost or replaced each year?


---

# 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/plan-your-deployment/accessnow-fit-assessment.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.
