> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/command-centre/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/command-centre/accessnow-user-guide/help-resources/accessnow-technical-requirements.md). # AccessNow Technical Requirements ## **AccessNow Initial Release Requirements** While new features are constantly being added, it is important for customers to be aware of the essential requirements and constraints for a successful setup and implementation of AccessNow. Adhering to these prerequisites is crucial for an efficient setup. {% hint style="warning" %} Any customer requirement that is not inline with the below requirements will likely require additional development effort. {% endhint %} ## Deployment: Cloud Service AccessNow is a cloud-based SaaS service and currently **does not plan to support a customer-hosted version**. However, it might be considered in the future. \ It's not installed as part of any Command Centre version and can be set up, managed, and updated independently of Command Centre. ### Network requirements Whitelisting the AccessNow Auth and Application endpoints. ## Command Centre #### Command Centre version Customers must use Command Centre v. 9.10 or later. #### Command Centre Cardholder Creation For security reasons, it is recommended that cardholders be registered in Command Centre before making requests. #### Single Command Centre Server Currently, each AccessNow tenancy supports only one Command Centre server and a Single Sign-On provider, but we are working on enabling a more flexible account structure in the future. #### Access Group List All Access Groups from Command Centre appear as a **flat list** in AccessNow. You can hide or rename them. Evaluate the usability of your Access Group list to ensure it allows end users to easily select the areas they need access to. ## Authentication: Single-Sign-On is Required AccessNow can authenticate users with existing OpenID Connect or SAML 2.0 Identity Providers * To make requests AccessNow users need to authorise via SSO. * Unauthorised users are not able to make any requests. ## I**nterface Language Support** The core AccessNow interface—such as menus and navigation—is currently available only in English. However, translated text can be used when configuring workflows. This allows most requester-facing content to be presented in the user's native language, enhancing accessibility and user experience. ## **Supported Device Types** AccessNow currently supports both desktop devices and mobile phones. While tablet access is available, the interface may require additional optimisation and might not deliver a fully seamless experience. ## Workflow ### Supported workflows Please refer to the list of supported [workflow examples](/command-centre/accessnow-user-guide/workflow-creation/workflow-examples.md). ### Workflow visibility All requester see the same list of workflows. At the moment there is **no** function allowing to assign workflows to an identity type e.g. employee or student. ### Approval types The following types of approvals are available: * Group Approval: Any person from the group can approve the request * Multi-level approval through having separate steps in a workflow going to different groups for Credential requests * Multi-level within a group; defined in the workflow * Manager Approval * Auto-approval ## Auditing & Reporting The following auditing and reporting functions are available in **AccessNow**: * The **per user** request and approval history. * **Access Group members** audit and removal. **Command Centre** reporting: * The Command Centre's reports can be generated as usual. However, AccessNow related actions, such as access provisioning, are currently processed by the "AccessNow Operator." As a result, details of individuals who approved access provisioning are not visible in the Command Centre. \ An update that includes these details will be available in an upcoming Command Centre version. ## Email Service The AccessNow service uses Gallagher's email service to send out system notifications. Currently, we are unable to use the customer's email service, but support for it is planned to be released soon. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.security.gallagher.com/command-centre/accessnow-user-guide/help-resources/accessnow-technical-requirements.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.