> 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/naming-conventions/modify.md).
# Modify Naming Conventions in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
Once you have created naming conventions in Patch My PC (PMPC) Cloud, you can modify them as required.
{% hint style="danger" %}
**Important**
Once you’ve saved any changes to your existing Naming Conventions, these changes will apply to all deployments created from this point forward.
Any existing deployments are not automatically updated until the next sync happens, which by default is daily at 2 AM local time, based on the country you selected when you onboarded to Patch My PC (PMPC) Cloud.
If you want to apply the changes to any existing deployments before the next sync runs, you can either [Edit a Deployment](/patch-my-pc-cloud/deployments/manage-deployments/edit.md) or [Recreate a Deployment](/patch-my-pc-cloud/deployments/manage-deployments/recreate.md). Either of these actions will apply the new naming conventions to the deployment.
{% endhint %}
To modify Naming Conventions:
1. Navigate to **Settings | Naming**.
2. Click on the relevant tab for the type of apps whose naming convention you want to modify.
3. Configure the options as required.
4. Click **Save** to save your changes.
5. Click **Submit** to save your changes on the **Are you sure** popup.
The **Success – Naming Conventions saved** notification is displayed.
---
# 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/naming-conventions/modify.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)
