> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/connectivity/readme.md).

# Connectivity

Deploy Verkada products anywhere with cell signal or Wi-Fi

**Overview**\
Verkada Connectivity uses gateways to provide network and power to Verkada devices in locations where traditional wiring is difficult. Gateways support cellular or WiFi connections and can deliver PoE to connected devices, which makes it possible to place cameras and other Verkada hardware in remote or outdoor areas.

This collection provides guidance on choosing a gateway, installing it, configuring connectivity, and maintaining reliable operation. It helps you extend your Verkada deployment to sites that need flexible power and network options.

Check out these links to get started:

<table data-view="cards"><thead><tr><th></th><th data-type="content-ref"></th></tr></thead><tbody><tr><td></td><td><a href="/connectivity/getting-started/get-started-with-the-cellular-gateway.md">Get Started with the Cellular Gateway</a></td></tr><tr><td></td><td><a href="/connectivity/getting-started/roles-and-permissions-for-gateway.md">Roles and Permissions for Gateway</a></td></tr><tr><td></td><td><a href="/connectivity/getting-started/gateways-network-settings.md">Gateways Network Settings</a></td></tr></tbody></table>


---

# 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.verkada.com/connectivity/readme.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.