> 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/test-and-active/activate-site.md).
# Activate site
When a site is activated, it will become operational and billing will commence. A site can be commissioned as soon as the system is operational, allowing the main contact to start using the system before the Technician has fully completed the installation. The site can be activated at the Technician's discretion.
To activate the site:
* Ensure you have [initialized the tampers](/smb/installing-gallagher-smb/initialize-tampers.md) in the SMB cabinet.
* The site can not be activated if there are Active Alarms. Use the **Alarm Count Badge** to determine if there are any Active Alarms. Investigate the individual inputs & outputs / boards / controller events and close any active alarms.
* Select the floating **ACTIVATE SITE** button. This will send an 'account activation' email to the Customer main contact.
* The Customer's main contact will need to follow the instructions in the email to download the Gallagher SMB app and accept the credentials. Refer to Onboard users.
The site has now been handed over to the customer. The SMB Installer Portal changes to ‘read-only’ for the site. If you need to make additional configuration changes, the customer must enable [Installer Mode](/smb/test-and-active/installer-mode.md) within the Settings of the SMB App.
Once the SMB system has been installed, configured & activated a new site report showing how the site has been configured is generated for Gallagher & the subscription is created based on this report for monthly or annual invoicing.
**⚠️ Important Note:**\
Emails and SMS messages are sent automatically at the time the action is performed. Gallagher SMB strongly recommends performing these actions during standard business 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/smb/test-and-active/activate-site.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.
