> 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/command/need-help/site-planner-homepage-overview/verkada-best-practice-partner-installation-guide.md).

# Best Practice Guide for Verkada Partners

{% hint style="success" %}
End of Life Notice: Partner Tools within Verkada Command will reach end of life (EoL) on August 1, 2026. To maintain uninterrupted service and access to enhanced renewal insights, transition to the new [Partner Management Tool](https://partners.verkada.com/login) within Verkada's Partner Portal. The updated interface allows customers to control data sharing in detail and gives partners direct visibility into relevant renewal timelines.
{% endhint %}

This document offers best practice recommendations for partners setting up organizations for their customers. It should be considered a guide rather than an all-inclusive list, as each organization’s needs differ.

***

## Best practice considerations

### Stage devices and sites

* You can [add devices](/command/organization-settings/add-a-device-to-your-command-organization.md) to an organization before they are physically on-site once you have the order number. This stages all devices from the order in the unassigned sites section for setup and configuration.
* If you have the floorplans and information planned out, you do have the ability to create sites and subsites and assign the devices to the sites so the installer only has to physically install and wire up the device [Manage Your Sites and Subsites | Verkada Help Center](/verkada-cameras/configuration/manage-sites-and-subsites.md)

### Access for installers

* You should add the installer to the customer Command organization before they go onsite to install the devices. We recommend adding installers as [temporary users](/command/users-and-permissions/manage-users-in-your-organization/manage-temporary-users.md) and setting an expiration date for their account access.
* Installers should plug-in devices in a staging environment before final installation to verify they come online, register, and check for firmware updates. This ensures quick installation in cases involving ladders, lifts, or other challenging scenarios.
* Installers should download the Command mobile app to assist with viewing cameras during installation. The app eliminates the need for a laptop or repeatedly climbing a ladder to check the camera angle on a desktop.

### Security and safety for customer organizations

* All users in the organization should [verify their email address and phone number.](/command/security/authentication-overview/verify-your-verkada-command-account.md)
* [2FA](/command/security/authentication-overview/two-factor-authentication.md) should be enabled for users with Org Admins permissions.
* Add at least two Org Admins to your partner organization.
* Avoid using shared accounts.

### Post-installation considerations

* Confirm with the customer if they want to keep the partner accounts as admins, reduce access permissions, or remove the accounts altogether. See [Manage Users in Your Organization](/command/users-and-permissions/manage-users-in-your-organization.md) for more information.
* Verkada uses [API keys](https://apidocs.verkada.com/reference/introduction) to allow customers to extract data for further analysis. Discuss with the customer if there are any managed services for alerting or reporting they would like integrated with Command.


---

# 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/command/need-help/site-planner-homepage-overview/verkada-best-practice-partner-installation-guide.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.