> 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/licensing/manage-your-licenses/find-and-add-license-keys-to-command.md).

# Find and Add License Keys

When you add new products to Verkada Command, you **must** also claim your license key so those products can continue using Command and remain in compliance.

If you don’t claim your licenses when adding new devices or products - or renew your licenses when they expire, you will lose access to most of your Command functionality after a 30-day grace period.

***

## Find your license key

You can find the license key in your Verkada order email.

<div align="left" data-with-frame="true"><img src="/files/6Gzq8IZPHnOiEby1Ab2W" alt="" width="375"></div>

***

## Claim your license key

{% hint style="danger" %}
You need [Org Admin](/command/users-and-permissions/roles-and-permissions-for-command.md) permission to claim a license key in Command.
{% endhint %}

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

{% step %}
**Under Admin, select Licenses & Renewals.**
{% endstep %}

{% step %}
**Select License Keys.**

1. At the top right, click **Claim.**
2. Enter the license key.

{% hint style="info" %}
License keys typically start with “CAP,” “RNW,” or “LAR.”
{% endhint %}

3. Review the license key details, then click **Proceed.**
4. Click **Claim Licenses** to complete.

<div align="left" data-with-frame="true"><img src="/files/uBMPpZ2YQwOcODDqr5qx" alt="" width="540"></div>
{% endstep %}

{% step %}
&#x20;**license key  typically starting with 'CAP’, ‘RNW’, or ‘LAR’)**
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Contact [Verkada Support](/command/need-help/contact-verkada-support.md) or <licensing@verkada.com> for assistance if you need to change how you claimed your licenses.
{% endhint %}

***

## FAQ

<details>

<summary>What if I did not receive an order email?</summary>

If you did not receive an order email from Verkada with the license key, we recommend that you:

* Check your spam folder: Sometimes, the order email might be sent to your spam folder.
* Ask the person who ordered the cameras: If the order was placed by someone else in your organization, they might have received the order email.
* Ask your Verkada reseller: If your Verkada reseller handled the order, they might have received the order email.

</details>

<details>

<summary>What do I do if I am unable to locate the order email?</summary>

If you or your reseller are unable to locate the order email, contact [Verkada Support](/command/need-help/contact-verkada-support.md).

**What happens if I don’t claim my license?**

If you don’t claim your license after adding new products to Command, you’ll see a banner reminding you to claim your license key. All organization admins will also receive an email reminder to claim the license key after 5 days. If you don’t claim your license keys within 36 days of adding the new products, you’ll lose access to Command.

</details>

***

{% hint style="info" %}
**Prefer to see it in action?** Check out the [video tutorial](https://www.youtube.com/watch?v=uzn7B9k2qpU).
{% endhint %}


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.verkada.com/command/licensing/manage-your-licenses/find-and-add-license-keys-to-command.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.