> 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/msp-app-sets/edit-an-msp-app-set.md).
# Edit an MSP App Set
*Applies to: Patch My PC Cloud*
To edit an MSP App Set in Patch My PC (PMPC) Cloud :
{% hint style="info" %}
**Note**
You can only edit App Sets that have been created successfully. You will be unable to edit it if it is in any other state (e.g., **Failed**, **In Progress**, **Deleting**, etc.).
{% endhint %}
1. Navigate to **App Sets**
2. Click the ellipsis (**⋮**) beside the App Set you want to edit and select **Edit**
3. Make any required changes such as:
1. Editing the name of the App Set
2. Editing or deleting apps and assignments
3. Adding new apps and assignments (including adding additional companies to deploy this App Set to).
4. Modifying the update rings (enabling, disabling, adding rings, removing rings, changing delays for rings, etc.).
4. Once you have finished making your changes, click **Deploy**
{% hint style="info" %}
**Note**
Adding either a new customer or a new app to an App Set triggers a new deployment of the relevant apps to the relevant customers. During this time, the App Set and any relevant deployments will have a **Status** of **In Progress**.
Also, deleting a company from an App Set removes all of the deployments for the apps within that App Set from the relevant company.
{% 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/managed-service-provider-feature/msp-app-sets/edit-an-msp-app-set.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.
