> For the complete documentation index, see [llms.txt](https://docs.roboflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roboflow.com/deployment/self-hosted/enterprise/deployment-manager/making-changes/api-keys-for-device-manager.md).

# API Keys for Deployment Manager

How device API keys are generated, scoped, viewed, and revoked when you add or remove a device.

When you add a device to Deployment Manager, an API key will be automatically generated. This API key is bound to the device and has permissions to access your Workflows and models. It cannot manage other devices, or list or create devices in your Workspace. The API key can be used by your device to access the Roboflow services required to set up and manage your device.

Use each device key only on its own device. For other uses (ex: uploading data to Roboflow or running inference on a test machine), create a separate API key.

You can see automatically generated API keys on the "API Keys" page in your Workspace Settings:

<figure><img src="https://1583372177-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoksNmwps1HmYr8TqHDnX%2Fuploads%2Fgit-blob-2a544632301135b6c11b97bd198288d3e01bb697%2Fenterprise-api-keys.png?alt=media" alt="Private API Keys list with masked keys and View Device links"><figcaption></figcaption></figure>

Automatically generated API keys use the device name when supplied. Otherwise, they have the format:

```
Device: [device ID]
```

Device keys are managed by their device, so their rows have no edit, roll, or revoke actions. Click "View Device" to open the device associated with the key.

When you [delete the device](/deployment/self-hosted/enterprise/deployment-manager/making-changes/delete-a-device.md) from Deployment Manager, its keys are revoked automatically. [Redeploying the device](/deployment/self-hosted/enterprise/deployment-manager/making-changes/redeploy-deployment-manager.md) keeps its key.