> 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/command-centre-client/configuring-command-centre/configuring-licensable-features/data-map/quick-tips-for-working-with-data-maps.md).

# Quick Tips for working with Data Maps

* Before creating a Data Map, you need to ensure the:
  * Scanner software (that provides the DLL's required as a prerequisite to setting up Data mapping items) is installed, and
  * Personal Data Fields (that will be used by the scanner) are created and added to the appropriate Access Groups (Visitor Types) and the Selected Fields grid on the Visitor Fields tab of the Visitor Management Division Configuration.
* Data Maps with unsaved changes display in the Navigation Panel in **bold** and have a \* at the end of their name.
* When adding field mappings to a Data Map (on the **Mappings** tab), if the Source and Destination are of incompatible types you will need to add a Transformation.


---

# 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/command-centre-client/configuring-command-centre/configuring-licensable-features/data-map/quick-tips-for-working-with-data-maps.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.
