# 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. --- # 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/rollout-processes.md?ask= ``` 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.