> 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/visitor-management/command-centre-site-configuration/using-image-capture-devices.md).

# Using Image Capture Devices

It is possible to capture multiple images for visitors, (e.g. a photo of the visitor, the visitor's business card, a letter of recommendation, etc.). Sites have the ability to configure the type of device to be used for capturing images, and visitor details can be captured by scanning a business card.

The following APIs are supported for image capture:

* Direct Show
* TWAIN
* Cardscan (

  **Note:** This option will not be available if your site has installed/upgraded with `NPSA=1` in the licence file.)
* Acuant SDK (for ScanShell 800NR)

Not all devices work with these APIs, therefore a modification may be required to get a particular device to work. As a result the devices supported are:

* Plustek OptiCard 821 (Business Card scanner based on the TWAIN API)
* Avision AVA6 (An A6 sized scanner based on the TWAIN API)
* CardScan 800C (Business Card scanner using the CardScan API)
* ScanShell 800NR (Business Card scanner using the Acuant SDK)

**Notes:**

* Other devices than those listed above may also work (using these APIs), but there is no guarantee of how well.
* It is recommended that sites have no more than five capture devices connected.


---

# 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/visitor-management/command-centre-site-configuration/using-image-capture-devices.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.
