> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/patch-my-pc-cloud/manage/settings/users/access-requests/approve-access-request.md).
# Approve an Access Request in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
To accept a user’s access request in Patch My PC (PMPC) Cloud:
1. Click the green tick in the **Action** column.
2. On the **Which role would you like to assign to “<*****user\_name*****>”** dialog box, select the relevant role to assign this user, then click **Confirm**.
{% hint style="success" %}
**Tip**
Hover over the “**i**” beside each role to see more information, or see [User Roles](/patch-my-pc-cloud/manage/settings/users/user-roles-reference.md) for more information.
{% endhint %}
The portal auto-refreshes and switches to the **Active** tab to show the user has been added. At the same time, the **User approved** notification is shown.
The user will receive an email from the mailbox with the subject **Access Granted “<*****company\_name*****>”**.
{% hint style="info" %}
**Note**
See [Example Access Approved Email](/patch-my-pc-cloud/technical-references/cloud-email-reference/example-cloud-access-approved-email.md) for an example of the email.
{% 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.patchmypc.com/patch-my-pc-cloud/manage/settings/users/access-requests/approve-access-request.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.
.png?alt=media)
.png?alt=media)
.png?alt=media)