> For the complete documentation index, see [llms.txt](https://docs.qubitro.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qubitro.com/platform/monitoring/blueprints/setup-and-configuration.md).

# Setup & Configuration

Learn how to create blueprints, add widgets, and organize them.

Blueprints are reusable dashboard layouts that can be applied across multiple devices or projects. They help maintain consistency across internal teams or customer-facing dashboards.

Blueprints are located under the **Monitoring** section of the Qubitro homepage. To view and manage them, select the **Blueprints** tab.

{% hint style="warning" %}
Blueprints are only available to **Organizations** on the Enterprise plan.
{% endhint %}

### Creating a Blueprint

{% stepper %}
{% step %}
**Select a dashboard layout**

Click **New Blueprint** from the Blueprints view and choose an existing dashboard to use as the starting layout. This layout will be saved for reuse.

<figure><img src="https://3109056034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfQfo4zX1x0hfOimS9E2u%2Fuploads%2FjnNQvhRiohF4HE6pChun%2FCleanShot%202025-04-07%20at%2017.54.07%402x.png?alt=media&amp;token=8621f8e8-8de8-4353-996a-5804108db985" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Name your blueprint**

Enter a name for the blueprint. You can also add tags to help organize or filter it later.

<figure><img src="https://3109056034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfQfo4zX1x0hfOimS9E2u%2Fuploads%2F227EXproGhPxuggni96K%2FCleanShot%202025-04-07%20at%2017.54.47%402x.png?alt=media&amp;token=78c90f69-70f4-4928-b892-6bef9d64b7c4" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Modify the layout**

After creating the blueprint, it opens in the dashboard editor. You can add or remove widgets, choose data points from devices or templates, and customize the layout just like any dashboard.

{% hint style="warning" %}
Choosing a project and device while editing a blueprint is only for preview and configuration purposes. Blueprints save the selected data points, not fixed device or project IDs. These will be applied automatically based on the selected device or template during dashboard creation.
{% endhint %}
{% endstep %}

{% step %}
**Save**

Click **Save** to store your changes. The blueprint is now ready to be applied when creating new dashboards.
{% endstep %}
{% endstepper %}

### Using Blueprints

Once created, blueprints can be applied to new dashboards during the dashboard creation process.

{% hint style="success" %}
Blueprints help speed up dashboard creation across multiple devices by reusing a saved layout with predefined widgets and configuration.
{% endhint %}

{% content-ref url="/pages/5iks6Kv9e9nSU7kwCrui" %}
[Setup & Configuration](/platform/monitoring/dashboards/setup-and-configuration.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.qubitro.com/platform/monitoring/blueprints/setup-and-configuration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
