# Patching Processes

It queues patches for processing and, based on the configured schedule, activates patch deployment in groups to reduce impact on endpoints and end users.

Patching Processes define the logic of a Patching Strategy and carry out key actions such as:

* Approval processes for patches
* User notifications
* Pre-staging content
* Deploying to test labs before production
* Routing patches to appropriate deployment channels, or directly routing them to business units for deployment

Overall, the Patching Process is a critical component in ensuring the smooth deployment of Patches across an organization. It defines **how** patches will move through the deployment process.

## Default patching processes

OneSite Patch offers several pre-built Patching Process Workflows. If creating a Legacy Patching Strategy we recommend using these first.

If you want to create your own Patching Processes, enter a support ticket and request help from [Adaptiva Customer Support](https://adaptiva.com/support).

![](/files/2Bt9bMFoRb3DXPbvWNnt)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.adaptiva.com/patch/advanced-settings/patch-processes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.