> 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/products/cc-software/operate/dual-authorisation-enhancement.md).

# Dual authorisation

The Dual Authorisation Enhancement is a more flexible, granular **Dual Authorisation** solution for doors requiring two-card badging. It replaces the Access Zone's Dual Authorisation properties page with an enhanced one that lets you pick the Card Type for each badge (Biometric selectable) and enforce same-cardholder or different-cardholders rules.

## Options

* Select the **Card Type** that must be acknowledged for a valid **first** card badge (a Biometric Card Type can be selected).
* Select the **Card Type** for a valid **second** card badge (Biometric also selectable).
* **"Not Enforced":** the first and second badges can be the same or different cardholders. Same cardholder increases the zone count by **+1**; different cardholders by **+2**.
* **"Different Cardholders":** enforces that the two badges must be **different** cardholders; zone count **+2**.
* **"Same Cardholder":** enforces that the two badges must be the **same** cardholder; zone count **+1** only.
* The **Access Group** selected for the second badge must **match** the Access Group selected for the first badge.

**Versions supported:** v7.90 to v8.90+ (**merged into core from vEL8.90**; previously a licensed feature).

***

🔗 **Related**

* [Dynamic Exit Zoning](/knowledge-hub/products/cc-software/operate/dynamic-exit-zoning.md). Another Access Management Solutions feature.
* [Locker Management Solution](/knowledge-hub/products/cc-software/operate/locker-management-solution.md). Another Access Management Solutions feature.


---

# 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/products/cc-software/operate/dual-authorisation-enhancement.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.