> 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/new-customers/new-customer-feasibility-assessment.md).

# New customer feasibility assessment

AccessNow offers a range of highly useful features that can automate physical access processes across different use cases in our customers' organizations. Additionally, Gallagher continuously develops and delivers new functions regularly, ensuring more value over time.

Refer to the [**Features Overview**](/knowledge-hub/accessnow-user-guide/introduction/features-overview.md) to explore all the outstanding features currently available.

To ensure seamless integration with AccessNow, new customers should evaluate the alignment of their Command Centre setup and automation processes with its capabilities. Consider the following before implementing AccessNow:

### 1. Command Centre site setup

While we're working on supporting more sophisticated setups, **a single AccessNow tenancy currently supports only one Command Centre server**.

All **Access Groups** from Command Centre are imported into AccessNow as a **flat list**. Users can manage their display by hiding groups or renaming them.

Consider the following:

* AccessNow requires **Command Centre version 9.1 or later**.
* How many Command Centre servers are you currently running? Would all of them require integration with AccessNow? If so, how are they configured? For example, do they operate across multiple sites or have real-time synchronization?
* Can a separate AccessNow tenancy be implemented for each Command Centre server?
* Is it acceptable to display a flat list of Access Groups to users requesting access?

### 2. Mapping your access provisioning workflow

To help us better understand your needs, please outline the access provisioning process you’d like to automate. Consider the following questions.

* What are your primary use cases for access requests? What is your current process for granting access or credentials?
* What approvals are required, and who is responsible for approving them?
* Who will be the approvers for access requests, and are they clearly separated by site or division?
* Do you need the ability to support different access provisioning workflows for different groups of users?

### 3. Authentication is required for making requests

AccessNow requires an authenticated requester. Users must sign in before submitting an access request, either through the organization’s SSO or an AccessNow account for external users. Access requests are not available through an anonymous public form.

* **Every requester must log in to AccessNow before submitting a request.** Anonymous/public access requests are not currently supported.
* **Internal or known users can sign in through SSO.** This is the primary approach for employees and other users already covered by the organization’s SSO environment.
* **External users do not have to be part of the organization's SSO.** They can be provided with their own AccessNow login account using a username and password with multi-factor authentication.
* **For contractor scenarios, appoint a contractor or contract manager as the authenticated requester.** Contract managers from different service providers can be granted access to the customer's AccessNow instance and submit requests on behalf of people needing site access.

### 4. Data to help with quoting

{% hint style="info" %}
Use the **AccessNow ROI Calculator** for service quoting, ROI calculation, and assessing the required licenses. <https://accessnowroi.security.gallagher.com/>
{% endhint %}

AccessNow is charged based on usage and automated use cases. To ensure accurate pricing, the AccessNow quote calculator takes expected usage patterns into account. You will be asked to provide the following details to help us estimate your needs:

* How many cardholders do you expect to manage?
* Would all cardholders make access requests? On average, how many access requests do you anticipate per cardholder per year?
* What percentage of credentials are newly issued each year?
* What percentage of credentials are typically lost or replaced?


---

# 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/new-customers/new-customer-feasibility-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.