> 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/lists.md).

# Lists

The system uses the following list types for workflow configuration: Command Centre imported lists and custom AccessNow lists.

## Lists Imported from Command Centre

Command Centre imported lists allow you to move information from Command Centre into AccessNow. You can use items like Access Groups, Personal Data Fields (PDFs), and Card Types to configure workflows.

* [**Access Groups List**](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/lists/command-centre-lists/access-groups-list.md): The Command Centre Access Group list includes all Access Groups imported from Command Centre. Occupants can select a specific location for access by choosing the relevant Access Group.
* [**PDFs List**](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/lists/command-centre-lists/pdf-list.md): This feature lets you import the list of Personal Data Fields used in Command Centre. It helps display relevant cardholder information in workflow requests or to approvers. You can choose which information stored in the PDFs is visible to users when accessing or approving a request. Examples include the requester’s role, department, and contact details. Any information stored in Command Centre as a PDF can be used or displayed in AccessNow.
* [**Card Types List**](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/lists/command-centre-lists/card-type-list.md): The card type list is a configurable list used in the credential workflow. It defines the different credential types available for assignment to users, such as a staff card, student card, cleaner card, or mobile credential. It allows users to select the appropriate card type during the credential request process, ensuring the workflow can handle multiple card types.

## Custom AccessNow Lists

* [**Custom Lists**](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/lists/custom-lists.md): Custom lists are also used for workflow configuration, but they can be created in AccessNow either manually or by importing a CSV file. They are used to create drop-down menus or search lists in workflow forms, such as lists of request reasons or pickup locations.


---

# 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/lists.md?ask=<question>&goal=<user_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.
