# Changing the active version for a private blueprint

## Introduction

The [active](/product-documentation/blueprints/working-with-private-blueprints/about-blueprint-versions.md#the-active-version) version of a blueprint is the version to be used whenever someone chooses to [install this blueprint from your private marketplace](/product-documentation/blueprints/working-with-private-blueprints/installing-a-private-blueprint.md). By default, the initial version of a blueprint becomes `active` when a blueprint is created. For example: &#x20;

<div align="left"><figure><img src="/files/38NMmLFxc3hLs7Xzo1ID" alt="" width="295"><figcaption></figcaption></figure></div>

Each time you [publish an update](/product-documentation/blueprints/working-with-private-blueprints/updating-a-private-blueprint.md) for an existing blueprint, a new version is generated. At this point, you can choose which version should be `active`.&#x20;

{% hint style="info" %}
If you have updated an existing blueprint, we recommend promoting it to a test company/environment before it is set to `active`. Please refer to [Updating a private blueprint](/product-documentation/blueprints/working-with-private-blueprints/updating-a-private-blueprint.md#suggested-workflow-for-updating-blueprints) for a suggested update workflow.&#x20;
{% endhint %}

## Need to know

When an [updated version](/product-documentation/blueprints/working-with-private-blueprints/updating-a-private-blueprint.md) is set to `active`, two things happen:

* This becomes the version used when someone chooses to [install this blueprint from your private marketplace](/product-documentation/blueprints/working-with-private-blueprints/installing-a-private-blueprint.md).
* An `update available` indicator is added to this blueprint in the private marketplace for any 'child' company profiles where it's installed. You can apply these updates in a [bulk operation](/product-documentation/blueprints/working-with-private-blueprints/rolling-out-blueprint-updates/bulk-blueprint-updates-force.md) or [individually](/product-documentation/blueprints/working-with-private-blueprints/rolling-out-blueprint-updates/accepting-a-blueprint-update-manually.md).

## The steps

{% stepper %}
{% step %}
**Log in to your own company profile**

Log in to the dashboard and (if you're managing multiple company profiles) ensure that you've [switched to your own profile](/product-documentation/company-management/multi-company-profiles/switching-in-and-out-of-a-linked-company.md).
{% endstep %}

{% step %}
**Access private blueprints**

Select `marketplace` from the left-hand navigation menu, then select `blueprints` and `private` tabs. Here you will see any blueprints that have been built by users associated with your company profile.
{% endstep %}

{% step %}
**Access the manifest for the required blueprint**

Click the blueprint tile that you want to manage. For example:

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

The [blueprint manifest](/product-documentation/blueprints/working-with-private-blueprints/building-a-private-blueprint.md) is displayed with the currently `active` version is displayed by default - for example:

<figure><img src="/files/hydzaRA0bwgKOvaK7AKL" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Switch to the version you want to make active**

Click in the version field and select the version that you want to make `active`. For example:

<div align="left"><figure><img src="/files/ch6r8oRUJXn0phSAJjVb" alt="" width="371"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Select the set active option**

Click the ellipsis icon at the top of the page:

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

Then select the `set active` option:

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

The selected version becomes `active` immediately.
{% endstep %}
{% endstepper %}


---

# 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/changing-the-active-version-for-a-private-blueprint.md?ask=<question>
```

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.
