> 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/transportation/configuration/add-a-transportation-gateway-to-command.md).

# Add a Transportation Gateway to Command

Add your Transportation Gateway to your Verkada Command organization

You need to add your gateway to Command before you can access data and manage settings.

{% hint style="danger" %}
You must create a [Verkada Command account](https://command.verkada.com/register) and log in with [Org Admin](/command/users-and-permissions/roles-and-permissions-for-command.md) permissions to activate and configure a gateway.
{% endhint %}

***

## Claim your gateway

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Devices.**
{% endstep %}

{% step %}
**On Devices, at the top right, click Add Devices.**
{% endstep %}

{% step %}
**Enter or scan the gateway’s serial number.**
{% endstep %}

{% step %}
**Once added, you can find the device in the Unassigned Devices site.**
{% endstep %}
{% endstepper %}

***

## Set up your gateway

### Command

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Devices.**
{% endstep %}

{% step %}
**Select your gateway.**
{% endstep %}

{% step %}
**Under General, enter:**

1. Enter a unique name.
2. Select a site.
3. Enter a location.
   {% endstep %}

{% step %}
**Click Apply.**
{% endstep %}
{% endstepper %}

### Command app

{% stepper %}
{% step %}
**Open the Command mobile app and log in to your organization.**
{% endstep %}

{% step %}
**In the top left, click Add Device.**

1. Scan the QR code or enter the serial number.
2. Click **Add Devices.**
   {% endstep %}

{% step %}
**Click Set Up Gateway.**
{% endstep %}

{% step %}
**Under General:**

1. Enter a unique name.
2. Select a site.
3. Enter a location.
   {% endstep %}

{% step %}
**Click Done.**
{% endstep %}
{% endstepper %}


---

# 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 dynamically 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/transportation/configuration/add-a-transportation-gateway-to-command.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 `build a script that syncs our docs to a CMS` 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.