> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/sso-connect-cloud/device-approvals/admin-approval.md).

# Admin Approval

Admins can approve end-user SSO Cloud devices

## Admin Approval Method via Admin Console

Selecting "Admin Approval" will send the request to the Keeper Administrator with the "Approve Devices" permission. The Admin can perform the approval through the Admin Console "Approval Queue" screen or by being logged into the Admin Console at the time of the request.

**(1)** User selects "Admin Approval"

![Admin Approval](https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MB_i6vKdtG6Z2n6zWgJ%2F-MFwDuzj2wC0I9f0NVNS%2F-MFwQxGaAoNYk2aUHQt1%2FScreen%20Shot%202020-08-29%20at%202.14.10%20PM.png?alt=media\&token=64a07c39-691c-40f4-8ef4-b66002b93033)

**(2)** User waits for approval or comes back later

![Admin Approval](https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MB_i6vKdtG6Z2n6zWgJ%2F-MFwDuzj2wC0I9f0NVNS%2F-MFwF2LGnMLu3I3uIQ-Q%2FScreen%20Shot%202020-08-29%20at%202.15.14%20PM.png?alt=media\&token=949be312-0ec1-4747-9729-3842cf3328f1)

**(3)** Administrator logs into the Admin Console and visits the Approval Queue

![Approval Queue](https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MB_i6vKdtG6Z2n6zWgJ%2F-MFwDuzj2wC0I9f0NVNS%2F-MFwF99SkAAm_0XcLE_n%2FScreen%20Shot%202020-08-29%20at%202.27.19%20PM.png?alt=media\&token=ba11cfa1-19b0-4279-8c7e-44a050035bd8)

**(4)** Admin reviews the information and approves the device

![Device Approval Screen](https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MB_i6vKdtG6Z2n6zWgJ%2F-MFwDuzj2wC0I9f0NVNS%2F-MFwFDcoQ4YqOLyfAiVK%2FScreen%20Shot%202020-08-29%20at%202.29.02%20PM.png?alt=media\&token=94ec403b-5544-4797-b565-9733e0bc342b)

Select the device to approve and then click "Approve". If the user is waiting, they will be instantly permitted to login. Otherwise, the user can login at a later time without any approval (as long as they don't clear out their web browser cache or reset the app).

## Approve Devices Role Permission

A special role permission called "Approve Devices" provides a Keeper Administrator the ability to approve a device.

**(1)** Go to Roles within the root node or the SSO node

![](https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MB_i6vKdtG6Z2n6zWgJ%2F-MHcMt4yCpJDrY69rV1B%2F-MHc_AiwACaIgql0P26E%2FScreen%20Shot%202020-09-19%20at%203.50.35%20PM.png?alt=media\&token=a500c5da-22a6-4e48-b278-e673ff80b1a9)

**(2)** Select the gear icon to control the Admin Permissions for the selected role.

![](https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MB_i6vKdtG6Z2n6zWgJ%2F-MHcMt4yCpJDrY69rV1B%2F-MHc_PrfvKIcKT0hbc9r%2FScreen%20Shot%202020-09-19%20at%203.50.21%20PM.png?alt=media\&token=788c7842-0a34-45f6-b833-ea93a32ba859)

**(3)** Assign "Approve Devices" permission

![](https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MB_i6vKdtG6Z2n6zWgJ%2F-MHcMt4yCpJDrY69rV1B%2F-MHc_5SR8tTH5h9ZcePk%2FScreen%20Shot%202020-09-19%20at%203.51.33%20PM.png?alt=media\&token=2fdc6834-5eaf-4d7a-8f7b-059a84ba2ed9)

Now, any user added to this role is able to login to the Admin Console to perform device approvals.

{% hint style="info" %}
As with any administrative permission, ensure least privilege
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.keeper.io/sso-connect-cloud/device-approvals/admin-approval.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.