> 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/the-anatomy-of-a-blueprint.md).

# The anatomy of a blueprint

## Introduction

A blueprint can include any number and combination of the following components:

| Resource                                                                                                                                          | Notes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
| ------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Process flows](/product-documentation/process-flows/about-process-flows.md)                                                                      | A blueprint will always include at least one process flow.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
| [Connectors](/product-documentation/connectors-and-instances/connectors-and-instances-introduction.md)                                            | <p>All connectors used in process flows are installed. Prior to installation, you can choose to <a href="#adding-connector-instances-prior-to-installation">add required connector instances</a> - or you can just install the connectors and add instances later.<br><br>If the blueprint includes a connector that you have already installed from the <a href="/pages/gO9cKXIn2PKE6IPQWXi3">connector marketplace</a>, a fresh copy of that connector is added alongside the existing one. You can then decide which one to use.</p> |
| [Custom scripts](/product-documentation/marketplace/marketplace-scripts.md)                                                                       | All scripts defined in process flow [script shapes](/product-documentation/process-flows/building-process-flows/process-flow-shapes/advanced-shapes/script-shape.md) and/or [map shape field transformations](/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/map-shape.md) are installed and deployed, ready for use.                                                                                                                                                                  |
| [Cross-reference lookups](/product-documentation/process-flows/cross-reference-lookups.md)                                                        | All cross-reference lookups defined as process flow [map shape field transformations](/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/map-shape.md) are installed and ready for use.                                                                                                                                                                                                                                                                                                    |
| [De-dupe data pools](/product-documentation/process-flows/building-process-flows/process-flow-shapes/advanced-shapes/de-dupe-shape.md#data-pools) | Any data pools defined in process flow [de-dupe shapes](/product-documentation/process-flows/building-process-flows/process-flow-shapes/advanced-shapes/de-dupe-shape.md) are added. These are 'clean' data pools (i.e. with no associated data), ready for use.                                                                                                                                                                                                                                                                        |
| [Caches and cache keys](/product-documentation/process-flows/building-process-flows/process-flow-shapes/advanced-shapes/cache.md)                 | Any caches and cache keys defined in process flow [add to cache shapes](/product-documentation/process-flows/building-process-flows/process-flow-shapes/advanced-shapes/cache/add-to-cache-shape.md) are added. These are 'clean' caches (i.e. with no associated data), ready for use.                                                                                                                                                                                                                                                 |

## Viewing the contents of a blueprint

Each blueprint in your marketplace is displayed with a visual summary of what's included - for example:

<div align="left"><figure><img src="/files/HP6PcYuXTnMHOGt2WX0t" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="info" %}
For more information about this summary please see [The Patchworks marketplace](/product-documentation/marketplace/marketplace-blueprints.md).
{% endhint %}

If you click on a blueprint tile, you can see a detailed breakdown of what's included:

<div align="left"><figure><img src="/files/zdBHDGFfNmr5dQcrEeya" alt=""><figcaption></figcaption></figure></div>

From here you can:

* [Add authentication credentials for connector instances (recommended)](#adding-connector-instances-prior-to-installation)
* [Install the blueprint in full (recommended)](/product-documentation/blueprints/patchworks-blueprints/installing-a-patchworks-blueprint.md)
* [Choose to exclude particular process flows](#excluding-process-flows-from-an-app-installation)

## Adding authentication credentials for connector instances&#x20;

Any connectors included with the blueprint are installed as part of the install process. To use these connectors in process flows, you must add an [instance](/product-documentation/connectors-and-instances/connectors-and-instances-introduction.md) of each - this is where you provide your authentication credentials for the associated third-party system.

If you have your credentials to hand, add them now using the **add instances** options provided - for example: &#x20;

<div align="left"><figure><img src="/files/l4GOUSOLqtamqZw5moTW" alt=""><figcaption></figcaption></figure></div>

You are prompted to choose an authentication method and then enter your credentials - for example:

<figure><img src="/files/vniOsuO8zquGD1IDHt7K" alt=""><figcaption></figcaption></figure>

When you save instance details and then [install the blueprint](/product-documentation/blueprints/patchworks-blueprints/installing-a-patchworks-blueprint.md), these instances are created as part of the installation. As a result, all connector shapes in process flows will be configured with these instances automatically.&#x20;

{% hint style="info" %}
It's not mandatory to add your instances as part of the blueprint installation. You can install the blueprint and [add instances afterwards via your manage connectors page](/product-documentation/connectors-and-instances/working-with-instances/adding-an-instance.md). If you do this, you must apply these instances to process flow connector shapes manually.
{% endhint %}

{% hint style="warning" %}
You cannot add instances that require **OAuth 2 (Client Credentials)** authentication, via the blueprint install process. If a blueprint includes connectors that require OAuth 2 (Client Credentials) authentication then you should install the blueprint and [add instances afterwards via your manage connectors page](/product-documentation/connectors-and-instances/working-with-instances/adding-an-instance.md). If you do this, you must apply these instances to process flow connector shapes manually.
{% endhint %}

## Excluding process flows from a blueprint installation

If a blueprint includes a process flow that you're sure you don't need, you can prevent it from being installed here - clicking the **install** button toggles to **don't install**:

<div align="left"><figure><img src="/files/ywLEK3WBhpth3vQTz5ou" alt="" width="375"><figcaption></figcaption></figure></div>

{% hint style="danger" %}
Typically, process flows are key to the successful implementation of blueprints. We recommend installing all included process flows unless you have a specific reason not to do so.
{% endhint %}