For the complete documentation index, see llms.txt. This page is also available as Markdown.

New Account Setup Guide

Setting Up a New Customer Account

To request a new AccessNow customer account, customers or channel partners must first provide Gallagher with a Purchase Order (PO) and then complete a short AccessNow onboarding form.

What you'll have at the end

A tenancy where a requester picks an area, an approver approves it, and the access group membership appears on the cardholder in Command Centre automatically, with notification emails at each stage.

Estimated effort: Half a day, if Command Centre is already available.

Troubleshooting and support

If you encounter issues or problems, use the troubleshooting guide or FAQ, or contact Gallagher Support. You can also ask questions in natural language using the chat window in the top-right corner.

Phase 0 — Prerequisites

Have all of these before you start. Missing any one of them is the usual reason a setup stalls halfway.

Item
Where it comes from

AccessNow administrator login

Emailed by the AccessNow team after the demo request form is processed

Access to a Command Centre server, v9.10 or later, with Config Client admin rights

Gallagher demo server, partner lab server, or customer server (trials)

Command Centre licence file that includes AccessNow licences

Gallagher Sales Operations or Support team

Command Centre serial number, server time zone, and API Gateway region (Australia or United States)

Command Centre Config Client. This information is required to set up Command Centre and AccessNow integration.

Workflow template Access Request Workflow Template (JSON) and email templates

Two or more demo users with mailboxes you can access: one requester and one approver

You. A user can't approve their own request, even in test mode, so two email addresses or people are required for testing.

Phase 1 — Prepare Command Centre

Done in Command Centre Config Client (and Command Centre Client for cardholders).

Set a unique identifier on cardholder PDF

Similar to other integration types, AccessNow uses a unique PDF (usually an email address or employee ID) to identify cardholders between Command Centre and AccessNow.

Get Command Centre demo-ready

💡 All access groups from the operator's division appear in AccessNow as a flat list. Keep the demo division tidy, or you'll be hiding a lot of items later.

Integrate Command Centre and AccessNow

Enable Command Centre Cloud, create an AccessNow REST operator, and complete the AccessNow configuration.

AccessNow branding

Choose and upload a logo and colour in AccessNow settings. A white-label URL needs the customer's DNS team and certificate validation, which adds lead time and another party. Decide early whether you need a custom URL so it does not become the critical path to the demo date.

Phase 3 — Users and approver groups

You create people for account setup and testing: someone to request access and someone to approve it. You then place approvers into groups, including a default group that catches requests without a specific owner.

Create the AccessNow users

You need at least two people to test the full flow, because nobody can approve their own request. Each user's email must match the cardholder in Command Centre so AccessNow can link the two records. Assign users the appropriate privileges and titles through user management options such as roles and groups.

Single Sign-On integration

While SSO is optional for demos, it is the default way to create and authenticate users in a production setup.

Create approver groups

Routing approvals to the right people is one of AccessNow's main selling points. The default group ensures no request is left without an approver, even for areas with no owner assigned.

Phase 4 — Command Centre Lists

Import Command Centre lists

You pull the Access Groups, Personal Data Fields, Card types and Divisions from Command Centre into AccessNow. You rename Access Groups into plain language, hide anything that shouldn't be requestable, and assign the approver group for each area. This defines both the requester's menu and who approves each item on it.

Assign approvers to Access Groups

This connects the requester's chosen area to the right approver. Without it, every request goes to the default group, and you lose the strongest part of the demo.

Phase 5 — Email templates

You make sure the notification emails exist for each stage of a request: new task for the approver, plus completed, declined and failed for the requester. Without them, the workflow runs but nobody finds out what happened.

Configure notification templates

Emails are how approvers find out about new tasks and how requesters hear the result. The workflow needs a template selected for each field.

Phase 6 — Build the workflows

You import Gallagher's workflow template and connect it to everything built so far: the area list, approver groups, unique identifier, cardholder details and email templates. The phase ends when the workflow builder shows no red validation errors.

Create the workflows from templates

At the moment, workflows can only be built from templates. This approach is much faster and less error-prone than building from scratch. The template also highlights any remaining configuration in red.

Phase 7 — Test

Test the workflows

You run the workflow end to end, using separate requester and approver accounts. You check that emails arrive, approvers see the right details, and approved access shows up on the cardholder in Command Centre. Remember that test actions make real changes in Command Centre.

Phase 8 — Publish and control visibility

Publish Workflows

You make the tested workflow live on the Make a Request dashboard and lock that version against edits. You then restrict visibility so only the right demo users can see it.

Final checklist

Last updated

Was this helpful?