> 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-account-set-up/new-account-request.md).

# New Account Request

## Account types and which form to use

<table data-header-hidden><thead><tr><th valign="top">Account type</th><th valign="top">Who it is for</th><th valign="top">Request route</th><th valign="top">Key conditions</th></tr></thead><tbody><tr><td valign="top"><strong>Demo account</strong></td><td valign="top">Gallagher staff and Channel Partners preparing demos, training or proof-of-concept work</td><td valign="top"><a href="https://forms.office.com/r/aMggv5j73Q">Staff &#x26; Channel Partner demo form</a></td><td valign="top">Used for sales demos and partner enablement. Not for customer production use.</td></tr><tr><td valign="top">90-day End User trial</td><td valign="top">End-user customers who want to evaluate AccessNow in their own environment</td><td rowspan="2" valign="top"><a href="https://forms.office.com/r/ujj7pTCMtS">End-user trial &#x26; paid account form</a></td><td valign="top">Granted at Gallagher Security’s discretion. Runs for 90 days.</td></tr><tr><td valign="top">Paid account</td><td valign="top">Customers who have purchased AccessNow</td><td valign="top">A Purchase Order (PO) must already be submitted. Forms without a PO are not processed.</td></tr></tbody></table>

## Requirements

* Complete [AccessNow Training](https://scorm-modules.training-platform.security-training.gallagher.com/accessnowbuilder/content/index.html#/)
* Fill in the account request form (see the above links).
* You must run Command Centre environment version 9.1 as a minimum.
* Enable the AccessNow feature through a licence file update (`AccessNow = 1`).

### Paid account requirements

* Submit a purchase order (PO) before submitting an onboarding form for a paid account. We process requests only after receiving the PO.

## What happens next

After receiving the form and PO, we create the account within five business days.

We send administrator login details to the nominated Channel Partner, end user, and dedicated Gallagher staff representatives. We then hold project planning and training meetings to familiarise everyone with the process and configuration steps.

## Request an account

* [Request a demo account for Channel Partners or Gallagher staff](https://forms.office.com/r/aMggv5j73Q)
* [Request an end-user trial or paid account](https://forms.office.com/Pages/ResponsePage.aspx?id=abhWIR9DFUiyzrSJO1yaqlvf4uuT_X1Dq61aIYfvrHFUQUZISlZMRDEyVFdVOTI5RkdKM0VEUkRYUy4u)


---

# 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-account-set-up/new-account-request.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.
