> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/smb/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/smb/installing-gallagher-smb/initialize-tampers.md).

# Initialize tampers

The front optical tamper detector will sense when the cabinet door has been opened. The rear optical tamper detector will sense when the cabinet is removed from its mounting surface.

Initializing the tampers should be the **last** thing you do before you leave the site.

* If you will be completing the Installer Portal (configuration app) configuration *on-site*, initialize the tampers just before you activate the site.
* If you will be leaving the site and completing the Installer Portal configuration *off-site*, initialize the tampers now.

When you have finished wiring the devices and no longer need to access the cabinet:

1. Close and lock the cabinet door using the key provided.
2. Within the [SMB Installer Portal](https://app.halo.gallagher.com/installer/), open the site and click the Controller at the top of the hardware tree.
3. Within the Controller lightbox, select **RESTART**.


---

# 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/smb/installing-gallagher-smb/initialize-tampers.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.