# Rolling out blueprint updates

## Introduction

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

* [Bulk updates (force)](https://doc.wearepatchworks.com/product-documentation/blueprints/working-with-private-blueprints/rolling-out-blueprint-updates/bulk-blueprint-updates-force). If you manage blueprint installations on behalf of your child companies, you can use the [installs page](https://doc.wearepatchworks.com/product-documentation/blueprints/working-with-private-blueprints/rolling-out-blueprint-updates/viewing-current-blueprint-installations) to roll out an update (forcibly) to selected companies. 
* [Manual update acceptance](https://doc.wearepatchworks.com/product-documentation/blueprints/working-with-private-blueprints/rolling-out-blueprint-updates/accepting-a-blueprint-update-manually). 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](https://doc.wearepatchworks.com/product-documentation/blueprints/working-with-private-blueprints/rolling-out-blueprint-updates/viewing-current-blueprint-installations)
* [Bulk blueprint updates (force)](https://doc.wearepatchworks.com/product-documentation/blueprints/working-with-private-blueprints/rolling-out-blueprint-updates/bulk-blueprint-updates-force)
* [Accepting a blueprint update manually](https://doc.wearepatchworks.com/product-documentation/blueprints/working-with-private-blueprints/rolling-out-blueprint-updates/accepting-a-blueprint-update-manually)