> For the complete documentation index, see [llms.txt](https://docs.adaptiva.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adaptiva.com/patch/advanced-settings/rollout-processes.md).

# Rollout Processes

Rollout Processes includes managing approvals, targeting a specific Business Unit, and initiating patch rollouts once approval is received.

Business Unit rollout processes determine which clients receive patches and control the final step before patches are delivered. For example, a rollout can deploy patches in batches of 100 clients, allowing administrators to monitor progress and address issues before continuing.

After the Patching and Deployment Channel processes define the required activity, they delegate rollout execution to each Business Unit. Each Business Unit then manages its deployment using its customized **All Clients Rollout Process** workflow.

Before creating a custom Rollout Process, enter a support ticket and request help from Customer Support [Adaptiva Customer Support](https://adaptiva.com/support)

### Including Rollouts in Business Units

The Rollout Process uses information from a Business Unit template, such as Approval Chains, Notification Chains, and Related Business Units, to control patch approval and deployment. It also performs the actual client deployment for the Business Unit.

New child Business Units automatically inherit the parent’s Rollout Process, which is typically the **All Clients Rollout Process**. If a Rollout Process is inherited, you must disable inheritance before making changes.