> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/documentation/portfolio-management/service-portfolio/how-to-use-blueprints.md).

# How to Use Blueprints

Blueprints in equipme allow you to create reusable templates for services or products that can be used within your own tenant or shared with connected partners. This article explains how Blueprints work, where to find them, and how to turn them into usable offers.

To access Blueprints shared by other companies, a partner connection must be established via **Partner Connect**. Once connected, shared Blueprints from those partners will be visible in your system. 

Click here to learn more about Partner Connect:

{% content-ref url="/pages/Gwrqpj3NDfLCLuy6s4Ks" %}
[Partner Connect](/documentation/portfolio-management/partner-connect.md)
{% endcontent-ref %}

<figure><img src="/files/1wxez3aUk4mOdchIv9GZ" alt=""><figcaption></figcaption></figure>

### How to Use Blueprints in Equipme <a href="#ispasted" id="ispasted"></a>

Blueprints in Equipme are reusable templates for services or products. They help standardize recurring offers, reduce manual work, and can be shared internally or with connected partners. This article explains how to create a Blueprint, how to use one, and what to consider when managing services created from them.

**Creating a Blueprint**

Blueprints are managed in the **Blueprints** tab within the **Service Portfolio**.

To create a new Blueprint:

1. Go to **Portfolio Management → Service Portfolio → Blueprints**
2. Click **Add → Create Blueprint**
3. Fill out the required fields such as:
   * Name
   * Category
   * Description, pricing, and images if needed
4. Decide on visibility:
   * **Internal**: Only visible to you
   * **Shared with all partners**: Available to all connected companies
   * **Shared with specific partners**: Select who should access it

These settings control who can see and use the Blueprint to create services in their own tenant. A partner connection via **Partner Connect** is required for sharing.

Blueprints are never directly visible to end customers - they serve as internal templates, not market-ready services.

**Using a Blueprint**

To create a service or product based on a Blueprint:

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

* Go to the **Services** tab within the **Service Portfolio**
* Click **Add → From Blueprint**
* Select a Blueprint from the list (your own or one shared by a partner)

You’ll be taken into a familiar configuration flow where you can customize the service:

* Adjust the name, descriptions, or category
* Modify pricing, including one-time and monthly charges
* Apply markups or discounts
* Set runtime behavior and activation

You can also enter an **internal comment**. This field helps track the origin or purpose of the service (e.g. “Imported from Blueprint on 21.08.2025”). It is only visible internally and is automatically pre-filled, but editable.

A **created** column also tracks when the service was added to your portfolio. Both fields are hidden by default in the table view but can be enabled through the column settings for better filtering or review.

> **Important:** When a service is created from a Blueprint, it becomes a fully independent copy. \
> There is **no ongoing link** between the service and the Blueprint it was created from.\
> This means:

**Important Details**

* A service created from a Blueprint is a **copy** — it has no live link to the original Blueprint
* Changes made to the original Blueprint do **not** affect already created services
* Blueprints are helpful for both external collaboration and internal standardization

This makes them a useful tool for managing large portfolios and scaling recurring service structures consistently across teams or with partner companies.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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://hub.equipme.io/documentation/portfolio-management/service-portfolio/how-to-use-blueprints.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.