> 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/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/generating-source-data/importing-cardholder-images.md).

# Importing cardholder images

### Introduction

Cardholder images can be imported into Gallagher Command Centre via the Cardholder Interface only. A cardholder's image could be a photograph or scanned signature, etc.

### Process

Enterprise Data Interface imports cardholder images by matching the image name in the source field with the image name in the image folder. If a match is successful the image is imported.

When importing from a source file, the imported images are moved from the image folder to the completed folder. When moved to the completed folder, if the image already exists, it will be overwritten.

When importing from a database, the imported images are moved from the image folder to the processed folder. The processed folder resides in the image folder directory. If not already present, the processed folder is automatically created when the interface is run.

If the source field specifies an image and the image is not in the image folder, the cardholder will be updated, but not the image. An alarm is raised to show that the interface "processed with failures". The alarm details will show the import statistics, (e.g. 5 images failed to load). The log file will specify the image name that cannot be found.

**Notes:**

* You will need to ensure the image name defined in the source field includes the file name extension.
* If you wish to update a cardholder's image, (e.g. supply a new image), you will need to supply the new image to the image folder. It is recommended that you supply only new images to this folder, not all cardholder images. This will save modifying cardholders unnecessarily.
* When an image is imported it may be re-sized to the dimensions specified by the image Personal Data Field. The default dimensions for the image Personal Data Field are: Width=160 pixels, Height=240 pixels.
* The same image cannot be added to all cardholders, unless a new copy is renamed for each cardholder.
* If a cardholder image is imported into Command Centre. A cardholder modified event is raised in Command Centre. This event is raised, even if the image imported was the same image as previously assigned to the cardholder.


---

# 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/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/generating-source-data/importing-cardholder-images.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.
