> 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/site-installation/server-properties/reserved-input-defaults.md).

# Reserved Input Defaults

### Introduction

This tab allows sites whose Controller 7000s are housed in cabinets to use physical tamper inputs (rather than optical tampers), and to also reserve power supply inputs and create alarms with the Controller as a source.

### Procedure

1. Open the **Command Centre Server Properties** window. [How?](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/opening-the-server-properties-window.md)
2. Click the **Reserved Input Defaults** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-fe3a004bc39d44c7a2893ff6a335c4896a957847%2Fsp_reservedinputdefaultstab.png?alt=media)
3. Select the appropriate option from the **I/O Module** drop-down list.

   The **Reserved Inputs** field becomes enabled.
4. Select from "Not Configured", "First 6 Inputs", "Last 6 Inputs" or "Custom Configuration" from the **Reserved Inputs** drop-down list.

   If "Custom Configuration" is selected, the **Custom Configuration** section becomes enabled.

   **Note:** If you tick the **Reserve inputs on creation of I/O module** checkbox, the Reserved Inputs you select here will already be configured when a plug-in module is selected on a Controller 7000 or an I/O module of the selected type is created.

   The window shows the defaults selected for each module type supporting reserved inputs.
5. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.


---

# 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/site-installation/server-properties/reserved-input-defaults.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.
