> For the complete documentation index, see [llms.txt](https://support.goodaccess.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.goodaccess.com/configuration-guides/features/zero-trust-access-control/device-approval.md).

# Device Approval

{% hint style="danger" %}
To ensure full functionality of this feature, no one with a GoodAccess application version of **4.4.0** or earlier will be able to log in!
{% endhint %}

{% hint style="info" %}
This feature is available in the **Premium plan and higher**.
{% endhint %}

You may set up Device Approval in [Control Panel > Access Control > Device Approval](< https://app.goodaccess.com/device-approval/>).

The Device Approval feature ensures that no new devices can access your secure perimeter unless manually approved by an Admin. When a new device attempts to connect, it will be placed in a pending queue. Only after Admin approval will the device gain access to the perimeter.

To set up Device Approval, check **Enable Device Approval**, and click **Save changes**.


---

# 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://support.goodaccess.com/configuration-guides/features/zero-trust-access-control/device-approval.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.