Support and Troubleshooting

Getting help

Check the troubleshooting topics below first. If the issue persists, contact your certified Gallagher Channel Partner for support.

Gallagher Channel Partners provide product installation, technical advice, and ongoing support. Find further support options through Gallagher Technical Support.

AccessNow Availability

AccessNow is not available

Check the Gallagher Security status page to confirm that cloud services are operational and that there are no planned or unplanned outages. https://status.gallagher.com/

Logging in

I forgot my password

Corporate organisation and enterprise customers use single sign-on, so the login and password are the corporate authentication details.

To recover your password, for a local AccessNow account (non-SSSO) use the Forgot password option on the login screen after entering your login email address.

I forgot my login

Corporate organisation and enterprise customers use single sign-on, so their login is their corporate email address.

For Gallagher Security demo accounts, contact support to receive a login reminder.

Login loop or trouble logging in to AccessNow with a local non-SSO account

Login issues, repeated login loops, or unexpected logouts are often related to cookie settings. Make sure cookies are enabled. If AccessNow is bookmarked in your browser, remove the old bookmark. Then create a new bookmark using https://accessnow.security.gallagher.cloud/.

Request tracking

Request status tracking

The requester and assigned approvers can track a request's status.

Requesters: To check your request status, go to the Requests module or My Requests on the dashboard. Click a request record to open the side panel with request status and details.

Approvers: The Tasks module provides the same side panel with request details, status, and history. By default, it shows Active requests that require.

To view requests already processed, choose All from the filter bar. Click a request record to open the side panel.

Click a request record to open the side panel, where you can track its status. You also receive email notifications when the status changes.

A request failed — how do I find out why?

Use the Request status tracking guidance to open the side panel with the request details. For failed requests, the side panel contains an error message explaining the failure.

When a request fails, both the requester and approvers receive an email notification.

Command Centre integration

Command Centre imports fail, for example PDFs, card types, or access groups

• First, check whether the Command Centre connection is working. See Test the connection.

• If Command Centre is connected properly, check the AccessNow REST Operator privileges in Command Centre. The list of privileges is provided here: AccessNow Operator Privileges.

• Lastly, assigned privileges may not have been refreshed for the AccessNow REST Operator. Refresh them in Command Centre as shown below.

Cardholder lookup returns a user but displays no details

When Workflow finds a user but returns no cardholder details, the user may exist in Command Centre without the expected personnel data, such as PDFs.

To resolve this issue, verify that the cardholder exists in Command Centre. Confirm that the unique cardholder identifier, such as an email address or user ID, is correct. Check that the cardholder record contains the expected data. If necessary, test with a known valid user record.

Workflow configuration

Workflow error: Cardholder lookup failed

• Most of the workflow templates require the requester to already exist in Command Centre. If the workflow cannot find the cardholder, it shows the Cardholder lookup failed error.

• To fix this issue, make sure the requester already exists as a Command Centre cardholder. AccessNow requesters and Command Centre cardholders are usually matched by email or IAM ID. The email address used by the cardholder in Command Centre must exactly match the login email used by the user in AccessNow. The email (or ID) must be identical in both systems for the cardholder lookup to succeed.

Request appears to come from the wrong person

The workflow configuration likely uses an incorrect unique identifier for cardholders. Configure the workflow to use a PDF list. Then select the correct PDF, such as Email or Unique ID, as the unique user identifier.

Can't see or approve a request

AccessNow prevents users from approving their own requests. A second approver account is required to view, approve, or reject the request during the Under Review stage.

Approvers must belong to the relevant Approver Group to view a request. For access requests, use the approver group assigned to the access group. For credential requests, use the approver group configured in the workflow.

Photo upload or PDF update fails

In Command Centre, check that the corresponding PDF Default Accessibility property is set to Editable. See the example properties below. Once it is editable, the PDF update should succeed.

AccessNow sends an incorrect email

The published workflow was likely configured with the wrong email template, such as "Approval notification" instead of "Contact the team". Identify the correct email template. Update the workflow, then republish it.

Access Request workflows

Why aren't all access groups showing in AccessNow?

To ensure access groups appear in AccessNow, an AccessNow operator must be created within the appropriate division in Command Centre. Only the access groups associated with this designated division will be imported into AccessNow. This setup is essential for accurate syncing and visibility of access groups within the system.

The workflow fails when assigning the selected access group: Failed to assign access

If the workflow only fails when assigning access, the requested access group may no longer exist in Command Centre. This can occur when the AccessNow access group list has not been synchronized with the latest Command Centre configuration.

The workflow can still allow users to select an obsolete access group. However, Command Centre rejects the assignment because the group is no longer valid.

Synchronise the Access Groups List in AccessNow to resolve the issue. Refresh the list regularly when access groups are added, removed, or modified in Command Centre.

Access group synchronization is not automatic. Obsolete access groups can remain selectable until the list is synchronized.

Credential workflows

Pick-up location dropdown shows access groups in the Credential workflow

If the Delivery location field displays access groups instead of locations, the workflow uses the wrong list type. It uses an Access Group list instead of a Location list.

Card types do not appear in the Credential Request workflow

Check that card types in the Card Type List are not hidden. Unhide at least one card type in the list to resolve the issue.

Area Management

Area Management menu item does not appear

The Areas option is not visible for the approver.

• To show Area Management for any user, first configure the option. Follow the instructions in Area Management Set Up.

• If the menu item does not appear for one user, they are not an approver. Add them to an approver user group. Assign the approver group to at least one access group.

  The wrong access group may also be configured in the Area Management settings. This can occur when multiple access groups are configured in AccessNow. Choose the primary access group list for identifying Area Managers. Then select that list in the Area Management settings. See Area Management Set Up for detailed instructions.

Missing cardholder information in the Area Management side panel

The Area Management module can display selected cardholder information. Select a cardholder record to open the side panel. The side panel can include PDFs and competencies.

If the information is configured in the Area Management settings but does not appear, it is not filled in within Command Centre. See Area Management Set Up.

Email notifications

AccessNow emails fail to send

AccessNow uses the Gallagher email service. If the service is operating normally, the likely cause is the embedded customer logo's size. Large logos embedded in emails as base64 may prevent emails from being sent. To troubleshoot, remove the logo and send the email through the workflow again.