> For the complete documentation index, see [llms.txt](https://docs.bluefletch.com/bluefletch-enterprise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/portal/admin/key-management/device-keys.md).

# Device Keys

## User Guide: Admin Tab <a href="#user-guide-admin-tab" id="user-guide-admin-tab"></a>

### Device Keys <a href="#device-keys" id="device-keys"></a>

The ***Admin - Device Keys*** page in BlueFletch Portal handles the generation and revocation of device keys for an organization. Click here to access the page in your organization's Portal.

Device keys are encrypted tokens that verify that API service calls coming from device applications are valid requests. Device key settings - specifically timeframes for key expiration, key rotation, and access token expiration - can be configured in the ***Admin - Organization*** [settings](/bluefletch-enterprise/product-guides/portal/admin/organization.md#key-management-options).

To configure devices to support key management, see the [***Key Management***](/bluefletch-enterprise/product-guides/bluefletch-launcher/launcher3/security-and-safety/key-management.md) Launcher feature documentation.

#### Generate Keys <a href="#generate-keys" id="generate-keys"></a>

1. On the ***Device Keys*** page, press the **Generate New Key** button in the upper right corner, which simultaneously opens the ***Generate Device Key*** dialog box and adds the new device key to the ***Device Keys*** list.
2. The dialog informs the user that the key was created successfully and lists the key's expiration date/time (based on the **Device Key Expiration Days** integer in the **Admin** - ***Organization*** page's settings) and version number.

<figure><img src="/files/GJVQmb320ySEL4IKkTmi" alt="" width="563"><figcaption></figcaption></figure>

3. Press **Close** to terminate the dialog. All device keys are listed by expiration date in descending order, including revoked keys.

#### Revoke Keys <a href="#revoke-keys" id="revoke-keys"></a>

1. On the ***Device Keys*** page, select **Revoke Key** within the options menu.
2. An alert box will display prompting the user to confirm the intention to revoke the key.

<figure><img src="/files/JbIAVL0uCta54HelYGNC" alt="" width="563"><figcaption></figcaption></figure>

3. Press **Revoke** to confirm. On the ***Device Keys*** list, a *Revoked On* date and time will be displayed for the key.

> **Note:** In order to revoke a key, there must be at least one other key already active. Attempting to revoke the last active key will produce an error alert box preventing the action and suggesting the creation of another key.


---

# 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://docs.bluefletch.com/bluefletch-enterprise/product-guides/portal/admin/key-management/device-keys.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.