> 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/command-centre-doors.md).

# Doors

Configure doors, readers, alarm zones, access zones, and door behaviour.

A **door** in Command Centre is any controlled access point: physical doors, turnstiles, gates, and barriers. It is the most complex configuration item in a site setup because it ties together a controller, readers, lock outputs, sensor inputs, an alarm zone, and access zones.

{% hint style="info" %}
The single most common install mistake is forgetting to attach the door to an alarm zone. Without an alarm zone, the door works but logs no events. The customer's audit trail and alarm response are silently broken.
{% endhint %}

## What a door connects

| Element                | Purpose                                                                       |
| ---------------------- | ----------------------------------------------------------------------------- |
| **Controller**         | The C7000/C6000 the door is wired to                                          |
| **Reader(s)**          | One reader for entry, optionally one for exit (required for APB)              |
| **Lock output**        | The relay that energises or de-energises the lock (mag-lock, electric strike) |
| **Door contact input** | The sensor that detects open/closed state                                     |
| **REX input**          | "Request to Exit" button (where used)                                         |
| **Alarm Zone**         | **Mandatory for events to log.** The alarm zone the door belongs to           |
| **Access Zone(s)**     | The zones the door transitions between (entry side / exit side)               |
| **Schedules**          | Optional. Auto-unlock during permitted hours                                  |

## Door creation flow

There are two paths in the current client:

**1. Door Wizard (recommended)**, a guided creation:

* Select controller, name, division.
* Assign reader(s), lock output, door contact, REX.
* Assign alarm zone.
* Assign access zones (entry side, exit side).
* Apply.

**2. Manual creation**, for power users or unusual hardware:

* More steps, exposes every config option.
* Used when the wizard does not fit (for example unusual hardware combinations).

The future Configuration Workspace consolidates these into a unified flow with better wizard guidance.

## Key configuration options

### Standard

* **Door open time**: how long the door is unlocked after a valid badge (typically 5 to 10 seconds).
* **Door open too long alarm**: fires if the door is held open beyond a threshold.
* **Door forced alarm**: fires if the door opens without a valid badge or REX.

### Accessibility

* **Extended access time**: longer unlock duration for cardholders flagged as needing accessibility (mobility, vision).
* Configured per-cardholder, applied automatically when that cardholder badges.

### Mantrap / airlock

* **Interlocking**: two (or more) doors prevented from opening simultaneously.
* Common for high-security entries. The outer door must close before the inner door unlocks.
* Requires both doors configured as interlocked, with the relationship defined explicitly.

### Schedules

* **Auto-unlock schedule**: the door unlocks during permitted hours (for example a main entrance unlocked 09:00 to 17:00).
* **Schedule overrides**: manual override of the auto-unlock from the operator console.

### Operator overrides

* **Lock / unlock / disable**: the operator can override door state in real time from the Status tile.
* Useful for emergencies, late arrivals, contractor access.

### Offline behaviour

* **Offline monitoring**: the controller continues to operate the door if the link to Command Centre is lost.
* Up to 1 million events stored locally on a C7000. Sync resumes when the link is restored.

## Most common install mistakes

**1. No alarm zone means no events logged.** Symptom: the customer's audit trail is empty for that door. Fix: every door must be attached to an alarm zone for event logging. Add an alarm zone check to commissioning checklists.

**2. Reader's alarm zone does not match the controller.** Symptom: events logged inconsistently or not at all. Fix: the reader's alarm zone should be on the same controller as the reader. Best practice is one default alarm zone per controller.

**3. APB configured on a single-reader door.** Symptom: APB does not enforce or breaks weirdly. Fix: APB requires entry and exit readers. Do not enable APB on doors that only have an entry reader.

**4. Lock output wired to the wrong relay.** Symptom: the door does not unlock, or stays unlocked. Fix: check wiring and verify the lock output configured matches the physical relay.

**5. Door open time too short.** Symptom: "Door open too long" alarm fires constantly during normal use. Fix: tune door open time to actual user behaviour (5 to 10 seconds typical, longer for high-traffic doors).

**6. Forgetting to assign access zones.** Symptom: zone counts do not update, APB does not work, mustering is broken. Fix: every door needs an entry-side access zone and an exit-side access zone defined.

## Connection to perimeter

For perimeter installs, "doors" includes:

* Vehicle gates (sliding, swing, barrier arm)
* Pedestrian gates in fence lines
* Turnstiles at site boundaries

These configure the same way as building doors, but with perimeter-specific considerations:

* Outdoor reader hardware (T-Series weatherproofed variants)
* Long cable runs (HBUS reach: 500m from C7000)
* Vehicle credentials (long-range readers, ANPR integrations)
* Higher-priority alarms (a fence breach plus a gate forced is more urgent than an office door forced)

***

🔗 **Related**

* [Command Centre - Access Zones](/knowledge-hub/products/cc-software/configure/command-centre-access-zones.md). The zones a door transitions cardholders between.
* [Command Centre - Access Groups](/knowledge-hub/products/cc-software/configure/command-centre-access-groups.md). The permission to use a door during permitted hours.


---

# 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/command-centre-doors.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.