> 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.md).

# Working with private blueprints

## Introduction

The most typical use case for a private blueprint is if you manage multiple company profiles and need to share a collection of process flows between them. 

Having built and tested the required process flows in the 'parent' company, you can add them to a blueprint. When a process flow is added to a blueprint, all associated resources are included - i.e. [connectors](/product-documentation/connectors-and-instances/connectors-and-instances-introduction.md), [scripts](/product-documentation/developer-hub/custom-scripting.md), [caches](/product-documentation/process-flows/building-process-flows/process-flow-shapes/advanced-shapes/cache/cache-maintenance.md), [cross-reference lookups](/product-documentation/process-flows/cross-reference-lookups.md), and [data pools](/product-documentation/process-flows/building-process-flows/process-flow-shapes/advanced-shapes/de-dupe-shape/working-with-data-pools.md). 

Having [built and published](/product-documentation/blueprints/working-with-private-blueprints/building-a-private-blueprint.md) a blueprint, it is added to your [private marketplace](/product-documentation/marketplace/private-marketplaces.md), where it can be [installed](/product-documentation/blueprints/working-with-private-blueprints/installing-a-private-blueprint.md) by any 'child' companies. 

If you need to [update an existing blueprint](/product-documentation/blueprints/working-with-private-blueprints/updating-a-private-blueprint.md), you can make the required changes and publish a new version. Depending how you need to work, this update can be [accepted by each child company individually](/product-documentation/blueprints/working-with-private-blueprints/rolling-out-blueprint-updates/accepting-a-blueprint-update-manually.md), or you can [force a bulk update to selected child companies](/product-documentation/blueprints/working-with-private-blueprints/rolling-out-blueprint-updates/bulk-blueprint-updates-force.md).

## More information

* [Building a private blueprint](/product-documentation/blueprints/working-with-private-blueprints/building-a-private-blueprint.md)
* [Installing a private blueprint](/product-documentation/blueprints/working-with-private-blueprints/installing-a-private-blueprint.md)
* [Updating an existing blueprint](/product-documentation/blueprints/working-with-private-blueprints/updating-a-private-blueprint.md)
* [Changing the active version of a blueprint](/product-documentation/blueprints/working-with-private-blueprints/changing-the-active-version-for-a-private-blueprint.md)
* [Rolling out blueprint updates](/product-documentation/blueprints/working-with-private-blueprints/rolling-out-blueprint-updates.md)