> 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/command-centre-client/configuring-command-centre/administration/access-groups/configuring-access-groups-for-test-modes.md).

# Configuring Access Groups for Test Modes

It is possible to configure groups of staff members with the Alarm Zones they are allowed to disarm and the period of time they can disarm them for. This procedure describes how to configure the Access Groups you require for testing via Terminals.

1. Click on the Access Group you want to configure test modes for, from the list in Viewer Navigation Panel.
2. Click the **Alarm Zone** tab, if not already displayed.
3. Check the **Change to the Disarmed state** checkbox in the "Alarm Zone Privileges" section.
4. If cardholders are required to arm Alarm Zones associated with any Access Zone associated with this Access Group, check the **Change to the Armed state** checkbox.
5. If cardholders are required to select an Alarm Zone to test on the Terminal, check the **Prompt for alarm zone selection** checkbox.
6. Select the appropriate "Cardholder Access Schedule" to control when the Cardholder can access the Terminal, as follows:
   1. Click the **Schedule** button (this appears as **--None Selected --** by default) in the "Terminal Access" section.

      A browse tool displays.

      ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-c042aa7101dd14a23a2514e7fb62623c464cad97%2Fselectchaccessschedule_popup.png?alt=media)
   2. Select the appropriate Schedule from the browse tool.
   3. Click the **OK** button.

      The pop-up closes and the button changes to the name of the Schedule you selected.
7. Check the **Override Alarm Zone unset time** checkbox and enter the period of time you require the Alarm Zones to be unset. (Default = 60 minutes).

   This time will override the Alarm Zone unset time for all Alarm Zones associated with this Access Group, when unset from the Terminal only.

   **Note:** If an Alarm Zone unset time is greater than the configured override unset time, the Alarm Zone will be reset at the time specified by the override.
8. Check the **User can initiate input test mode** checkbox.

   Cardholders belonging to this Access Group will be able to perform input tests.
9. Select the Alarm Zones that the members of this Access Group are authorised to test in the Alarm Zones section, as follows:
   1. Click the **Add Alarm Zones** button.

      A browse tool displays.

      ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-6573eff6259e65b2cc0c6ac613a5546bc3fca0f9%2Fag_addalmzones_popup.png?alt=media)
   2. If necessary, search for the Alarm Zone(s) you want by entering characters in the **Search** field and/or refining the search mode and filters.

      The grid becomes populated with Alarm Zones that match the search criteria.
   3. Check the Alarm Zone(s) you want the group to have access to, and click the **Add Selection** button.

      The browse tool closes, and the selected Alarm Zone(s) appear in the Alarm Zones grid.
10. Click the **Save** button.


---

# 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/command-centre-client/configuring-command-centre/administration/access-groups/configuring-access-groups-for-test-modes.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.
