> 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/configure/configuration-scenarios/scenario-turnstile-configuration-with.md). # Configure a turnstile with one door and two outputs Use one door license and Logic Blocks to control two turnstile outputs. This pattern lets one **door licence** drive **two outputs** for a turnstile or flap barrier that needs two triggering outputs (for example, separate dry-contact relays for a "Welcome" or "Goodbye" audio response). The trick is to combine the door's unlock output with the reader's **Card Read Output** through a **logic block**, so the second output only fires on a valid access, not on any card read. ### Use case This allows the administrator to use only one door licence while providing two outputs for a turnstile or flap barrier that requires two triggering outputs (such as a dry contact or relay for a "Welcome" or "Goodbye" audio response). ### Entry reader configuration requirements **A. 2 virtual outputs** * **Item 1: Door unlock output.** A virtual output the door is configured to use as a "valid granted access". * **Item 2: Card Reader's Output control.** Reflects which reader is used on the turnstile (entry or exit) and is used as a "signal". **B. 1 logic block** * Secures the decision made from valid access granted. **C. 2 outputs (item A)** * 1 item serves as the **Entry Unlock Output** (Input 1, entry for the turnstile). * 1 item serves as the **Exit Unlock Output** (Input 2, exit for the turnstile). ### Configuration logic * The virtual output assigned to the **Card Read Output** triggers whenever a card (any card, valid or not) is read from the reader. It signals which side of the turnstile a cardholder goes through, so the system can identify whether the badge is from the entry or exit side. * The **logic block** is configured so that only valid access triggers its reflected output, which the turnstile then uses as input 1 (respectively input 2). **On a valid cardholder access:** the door's **Unlock Output** (item 1) triggers along with the entry reader's **Card Read Output** (item 2). This satisfies the logic block's rules and triggers the **Output** configured on its **Reflected Output** (item A). **On an invalid cardholder access:** the door's **Unlock Output** (item 1) does **NOT** trigger while the entry reader's **Card Read Output** (item 2) does. Since the logic block's rules are not met, the unlock output does not trigger and therefore does **NOT** trigger the turnstile. ![Entry reader turnstile configuration](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-52348fd467ddaf6d10f03bd3ac6ba195b0de694b%2FSECHUB-CCS-TURNSTILE-01-entry-reader-config.png?alt=media) > **Note:** By design, the **Card Read Output** will trigger any output or relay configured in it the moment a card is read from the reader, regardless of whether the card is valid or not. ### Exit reader configuration Configuration for the exit reader follows the same logic as the entry reader. ![Exit reader turnstile configuration](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-580487ae5fa7af7b1e6aa48bb643325d7e9cdf61%2FSECHUB-CCS-TURNSTILE-02-exit-reader-config.png?alt=media) ### Related links * [Scenario - Pulsing an output using Logic Blocks](/knowledge-hub/products/cc-software/configure/configuration-scenarios/scenario-pulsing-an-output-using-logic.md). The general logic-block mechanism used here. * [Command Centre - Access Groups](/knowledge-hub/products/cc-software/configure/command-centre-access-groups.md). Granting the access that a valid turnstile passage depends on. --- # 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/configure/configuration-scenarios/scenario-turnstile-configuration-with.md?ask=&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.