# Settings

Blueprint settings are organized under **General** and **Configuration** tabs.

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

### General

#### Edit Tags

Use tags to organize, group, and filter your blueprints for easier access.

{% hint style="warning" %}
You can create up to three tags per blueprint. Remove an existing tag before adding a new one if the limit is reached.
{% endhint %}

#### Blueprint ID

Used when interacting with the Qubitro API (read-only).

#### Blueprint Name

Update the name to clarify the purpose or structure of the blueprint.\
\&#xNAN;*Maximum 32 characters.*

#### Created At

Shows the date and time the blueprint was created.

{% hint style="info" %}
The **Created at** timestamp reflects the time zone set in your account preferences.
{% endhint %}

#### Delete Blueprint

Permanently deletes the blueprint and removes its layout from the system.

{% hint style="danger" %}
Deleting a blueprint is irreversible. All associated layout and widget structure will be lost.
{% endhint %}

{% hint style="success" %}
Blueprints cannot be deleted if they are currently used by any dashboards. This prevents accidental deletion of active layouts.
{% endhint %}

### Configuration

#### Horizontal Scroll & Wide-View Display

Enable horizontal scrolling and wide-view support for large layouts.

#### Refresh Period

Set how often widgets within dashboards created from this blueprint should auto-refresh data.

{% hint style="info" %}
These settings define the default layout behavior for dashboards generated using the blueprint.
{% endhint %}


---

# 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://docs.qubitro.com/platform/monitoring/blueprints/settings.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.