> 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/workflow-creation/creating-and-managing-workflows/workflow-configuration.md). # Workflow Configuration A workflow is a structured sequence of **steps** designed to automate or guide a process—such as requesting access to a secure area. Workflows are configured using the visual builder and saved as structured JSON data, which means they can be configured and changed without needing to write code. Workflows are composed of various elements, each playing a crucial role in building the processes: * **Trigger**: In case of AccessNow workflow are usually triggered by a **user initiated** request or action. * [**Global Settings**](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/global-settings.md) configuration inclue Fields and Processes. * **Fields** are the basic data elements used throughout the workflow. Think of them as the blanks in a form that need to be filled in, such as “Name”, “Email”, or “Card Number”. * **Processes** are actions that the system performs automatically. It coulod e.g. be a tasks carried out in the Command Centre, such as access provisioning or event creation, or automated actions by AccessNow, like sending an email. * [**Steps**](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/steps.md) are the stages of the workflow. Each step represents a specific action or decision point, such as collecting information, performing a check, or sending a notification. Each step is configured separately and can let you configure detailed elements like e.g. step actions and decisions, step form fields, or choose notification Email templates. * [**Approver Groups**](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/approver-groups.md) Sets of users with permissions to approve certain requests made through the workflow. Approver groups are associated with specific workflow steps or Command Centre access groups. * [**Command Centre Access Groups**](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/lists/command-centre-lists/access-groups-list.md) Each Command Centre Access Group determines access to a selected Command centre area. Refer to the Command Centre guide for detailed explanation. * [**Search and Drop-Down Lists**](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/lists/custom-lists.md) Lists of values used in the forms utilised by the workflow. * [**Email Templates**](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/email-templates.md) Predefined messages sent automatically at specific workflow stages, facilitating communication and notification. --- # 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/workflow-creation/creating-and-managing-workflows/workflow-configuration.md?ask=&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.