> For the complete documentation index, see [llms.txt](https://doc.wearepatchworks.com/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.wearepatchworks.com/product-documentation/blueprints/working-with-private-blueprints/rolling-out-blueprint-updates.md).

# Rolling out blueprint updates

## Introduction

There are two approaches for rolling out blueprint updates to child company profiles that you manage:

* [Bulk updates (force)](/product-documentation/blueprints/working-with-private-blueprints/rolling-out-blueprint-updates/bulk-blueprint-updates-force.md). If you manage blueprint installations on behalf of your child companies, you can use the [installs page](/product-documentation/blueprints/working-with-private-blueprints/rolling-out-blueprint-updates/viewing-current-blueprint-installations.md) to roll out an update (forcibly) to selected companies.
* [Manual update acceptance](/product-documentation/blueprints/working-with-private-blueprints/rolling-out-blueprint-updates/accepting-a-blueprint-update-manually.md). As the blueprint owner, you can make updates available, but the child company decides when to accept/apply them. This ensures that updates are applied at a convenient time, maintains transparency, and avoids unexpected changes to live integrations.

## Pages in this section

* [Viewing current blueprint installations](/product-documentation/blueprints/working-with-private-blueprints/rolling-out-blueprint-updates/viewing-current-blueprint-installations.md)
* [Bulk blueprint updates (force)](/product-documentation/blueprints/working-with-private-blueprints/rolling-out-blueprint-updates/bulk-blueprint-updates-force.md)
* [Accepting a blueprint update manually](/product-documentation/blueprints/working-with-private-blueprints/rolling-out-blueprint-updates/accepting-a-blueprint-update-manually.md)