# 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](https://doc.wearepatchworks.com/product-documentation/connectors-and-instances), [scripts](https://doc.wearepatchworks.com/product-documentation/developer-hub/custom-scripting), [caches](https://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/process-flow-shapes/advanced-shapes/cache/cache-maintenance), [cross-reference lookups](https://doc.wearepatchworks.com/product-documentation/process-flows/cross-reference-lookups), and [data pools](https://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/process-flow-shapes/advanced-shapes/de-dupe-shape/working-with-data-pools). Having [built and published](https://doc.wearepatchworks.com/product-documentation/blueprints/working-with-private-blueprints/building-a-private-blueprint) a blueprint, it is added to your [private marketplace](https://doc.wearepatchworks.com/product-documentation/marketplace/private-marketplaces), where it can be [installed](https://doc.wearepatchworks.com/product-documentation/blueprints/working-with-private-blueprints/installing-a-private-blueprint) by any 'child' companies. If you need to [update an existing blueprint](https://doc.wearepatchworks.com/product-documentation/blueprints/working-with-private-blueprints/updating-a-private-blueprint), 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](https://doc.wearepatchworks.com/product-documentation/blueprints/working-with-private-blueprints/rolling-out-blueprint-updates/accepting-a-blueprint-update-manually), or you can [force a bulk update to selected child companies](https://doc.wearepatchworks.com/product-documentation/blueprints/working-with-private-blueprints/rolling-out-blueprint-updates/bulk-blueprint-updates-force). ## More information * [Building a private blueprint](https://doc.wearepatchworks.com/product-documentation/blueprints/working-with-private-blueprints/building-a-private-blueprint) * [Installing a private blueprint](https://doc.wearepatchworks.com/product-documentation/blueprints/working-with-private-blueprints/installing-a-private-blueprint) * [Updating an existing blueprint](https://doc.wearepatchworks.com/product-documentation/blueprints/working-with-private-blueprints/updating-a-private-blueprint) * [Changing the active version of a blueprint](https://doc.wearepatchworks.com/product-documentation/blueprints/working-with-private-blueprints/changing-the-active-version-for-a-private-blueprint) * [Rolling out blueprint updates](https://doc.wearepatchworks.com/product-documentation/blueprints/working-with-private-blueprints/rolling-out-blueprint-updates) --- # 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://doc.wearepatchworks.com/product-documentation/blueprints/working-with-private-blueprints.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.