> 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/managed-service-provider-feature/manage-msps/manage-msp-users/user-role-reference.md).

# User Role Reference for the Managed Service Provider feature of Patch My PC Cloud

*Applies to: Patch My PC Cloud*

Once a Managed Service Provider (MSP) has created a child company, users can request access to it by attempting to sign in to the portal using an email address that matches the one used to onboard the child company.

The following table lists the levels of access MSP Customers have to objects within the PMPC Cloud Portal, depending on which role you have assigned them (either directly or through them being a member of an Entra ID Security Group assigned a role).

| Read-Only | Custom App Admin | Intune App Admin | Full Admin     | Full Admin with Access Management |
| --------- | ---------------- | ---------------- | -------------- | --------------------------------- |
| Read      | Read             | Read             | Read and Write | Read and Write                    |


---

# 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/managed-service-provider-feature/manage-msps/manage-msp-users/user-role-reference.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.
