> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/install-connect-and-integrate/multi-device-site-management-overview.md).
# Multi-Device Site Management Overview
Locations with more than one **Solink Recording Device (SRD)** appear in the Solink platform as one location. Previously, multiple SRDs at the same address appeared as separate locations in Solink—each with its own cameras, alarms, and permissions. This made setup repetitive and time-consuming.
As of September 2025, all SRDs and cameras at the same address **are grouped under one location**, with configurations applied once and reflected across all devices.
All cameras for a site now appear together under a single site view.
Multi-device sites provide:
* **Centralized Alarm Management**: Configure alarm contacts and schedules once, and they’ll apply across all devices.
* **Simplified permissions**: Grant access at the location level—no more managing permissions device by device.
* **Unified Event History**: Events are consolidated at the location level for a complete picture without switching between devices.
* **Multi-Device Clip Saving**: Save clips across multiple devices at a location.
---
# 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.solink.com/docs/install-connect-and-integrate/multi-device-site-management-overview.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.