> 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/workflow-creation/what-is-a-workflow.md).

# What is a workflow?

A workflow is a different name for an **organised process**. The workflow is a structured sequence of steps designed to automate or guide the process of e.g. handling access and credential requests.&#x20;

Workflows ensure that requests are processed efficiently and securely, following the organization's policies and procedures. They can include steps such as request submission, approval by designated approvers, verification, and issuance of credentials.&#x20;

Workflows streamline the management of physical access and identities, reducing manual intervention and minimising errors.&#x20;

[Workflow Examples ](/command-centre/accessnow-user-guide/workflow-creation/workflow-examples.md)

[Workflow Mapping](/command-centre/accessnow-user-guide/workflow-creation/workflow-mapping.md)&#x20;

[Creating a Workflow in AccessNow ](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows.md)


---

# 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/workflow-creation/what-is-a-workflow.md?ask=<question>&goal=<endgoal>
```

`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.
