> 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/pam/pam-with-devolutions-cloud/privileged-accounts/request-access-to-a-privileged-account.md). # Request access to a privileged account Request temporary checkout access to a privileged account in Devolutions Cloud, choose an approver and duration, then check in once your task is done. {% hint style="info" %} The following topic focuses on making a check out request from the Devolutions Cloud web interface. Note that this functionality is also available in Remote Desktop Manager with Devolutions Cloud, either by accessing the privileged account entry in the PAM vault, or by connecting to a linked remote session. You can also access the privileged account in the Devolutions Cloud web interface even if you make the request in Remote Desktop Manager. {% endhint %} {% hint style="info" %} To learn how to approve or deny a request, visit [Approve access to a privileged account](/pam/pam-with-devolutions-cloud/privileged-accounts/approve-access-to-a-privileged-account.md). {% endhint %} The PAM ***Check out*** feature allows users to request temporary access to a privileged account entry in a PAM vault. The approver must then approve or deny the request. ### Privileged account check out request {% hint style="info" %} The duration of the access begins when the request is approved. {% endhint %} Follow the steps below to learn how to make a check out request: 1. In the ***Vault*** tab, select the PAM vault using the selector. 2. Select the privileged account entry you want to access, then click on ***Check out***.

Using the buttons to copy and view the password also opens the same Check out request window.

3. In the ***Check out request*** window, select the approver you want to send your request to using the drop-down list. You can also use the filter bar to refine your research. 4. Select the ***Access duration*** in the drop-down menu. 5. Write a short ***Comment*** to the approver explaining why you want access to this entry. 6. When you are done, click on ***Request check out***. You now have to wait for the approver to respond to your request. You will be notified by email whether the answer is positive or negative. The next section details what to do once you have received a response. ### Response to your request If your request is approved, your email will have a button at the bottom that will bring you directly to your entry in Devolutions Cloud. It is also possible to manually go to your entry. Once you are on the entry in the PAM vault, you will see at the top that your check out request has been approved and that the entry is already checked out by you. A check mark validates that your request was approved. Next to the check mark is the ***Time remaining*** on your request. There is also a ***View details*** option which is described in the next section. Now that you can copy and view the password of this privileged account using the corresponding icons, you can perform your tasks. ### View details and check in the privileged account entry ***View Details*** allows you to see information about your check out request as well as check in the entry. In the top section, you can view the ***Requested duration*** and the ***Time remaining*** on your access. The approver can modify your access duration if necessary when approving the request. Further down is your message and the approver's message. Finally, you can check in your privileged account entry by clicking on ***Check in*** or by using the same button you used to check it out. When you check in the entry, the privileged account password automatically resets and the old password is rendered useless. Be sure you want to do this first, since to regain access to your entry, you will need to make another request. Otherwise, your access will end within the time frame set by you and the approver. ### Checkout expiration warning As your checkout approaches its expiration time, a banner appears showing the ***Time remaining*** along with a ***Request Extension*** button. The banner is dismissible, but reappears if the page is refreshed while the checkout is still close to expiring. ### Request a checkout extension {% hint style="info" %} Checkout extensions must be enabled in the entry's checkout policy for the ***Request Extension*** button to be available. See [Checkout policies](https://github.com/Devolutions/doc-gitbook/tree/master/cloud/web-interface/administration/modules/privileged-access/checkout-policies.md). {% endhint %} 1. From the expiration warning banner, or from the check out request's ***View details*** window, click ***Request extension***. 2. Set the additional duration you need, up to the maximum allowed by the checkout policy. 3. Write a short ***Comment*** explaining why you need more time. 4. Click ***Request extension*** to submit. If the checkout policy does not require approval for extensions, the extension is granted immediately. Otherwise, the request is sent to the same approver(s) as the original checkout and appears as a pending extension in ***View details*** until it is reviewed. You can cancel a pending extension request at any time before it is approved or denied. #### See also * [Devolutions Academy – Accessing accounts with Devolutions PAM](https://academy.devolutions.net/student/page/3307651-accessing-accounts-with-devolutions-pam?sid=dcc8877b-6afc-4396-adee-0231b00e0e46\&sid_i=0) --- # 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/pam/pam-with-devolutions-cloud/privileged-accounts/request-access-to-a-privileged-account.md?ask=&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.