> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/it/concepts/advanced-concepts/check-out-approvals.md).

# Approvazioni di check-out

Le approvazioni di check-out in Devolutions Server richiedono che approvatori designati autorizzino le richieste di account privilegiati in Devolutions PAM prima del check-out.

Le approvazioni di check-out in Devolutions Server con Devolutions PAM aggiungono un ulteriore passaggio di autorizzazione prima che un account privilegiato possa essere utilizzato. Quando un utente richiede il check-out di una credenziale PAM, la richiesta viene indirizzata agli approvatori designati, che possono approvarla o negarla indicando un motivo e un limite di tempo, e ogni decisione viene interamente registrata.

I team utilizzano tipicamente le approvazioni di check-out per gli account ad alto rischio, come gli amministratori di dominio, dove sono richiesti un numero di ticket e l'approvazione di un responsabile prima che Remote Desktop Manager o Devolutions Gateway aprano la sessione, contribuendo ad allineare gli accessi privilegiati ai controlli interni.

#### Argomenti correlati

* [Approvazioni di check-out](https://docs.devolutions.net/pam/it/concepts/check-out-approvals)
* [Processo di check-out](https://docs.devolutions.net/pam/it/pam-with-devolutions-server/checkout-process)
* [Accesso temporaneo in Devolutions Server](/server/it/web-interface/temporary-access-in-devolutions-server.md)


---

# 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.devolutions.net/server/it/concepts/advanced-concepts/check-out-approvals.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.