> For the complete documentation index, see [llms.txt](https://docs.diro.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.diro.app/en/operations/service-attributes.md).

# Service Attributes

Attributes are tiered labels that describe the character of a service — difficulty level, age group, intensity. On the storefront, attributes appear as **colored pills** on the service card, so customers immediately know whether the service is right for them.

Go to **Master Data → Services → select a service → Attributes tab**.

## Structure

One attribute consists of:

* **Label** — the attribute's name. Example: `Level`.
* **Description** — optional explanation.
* **Options** — a list of possible values. Each option has a label, an optional description, and a **color**.

One service can have several attributes at once.

```mermaid
flowchart LR
  S["Vinyasa Class"] --> A1["Level"]
  S --> A2["Intensity"]
  A1 --> O1["Beginner"]
  A1 --> O2["Intermediate"]
  A2 --> O3["Moderate"]
```

## Ready-made templates

Templates are available that you can simply select:

* **Level** — Beginner, Intermediate, Advanced, All Levels.
* **Age Group** — Child, Teen, Adult, Senior, All Ages.
* **Intensity** — Low, Moderate, High.

Or choose **custom** to build your own attribute.

## Examples

{% tabs %}
{% tab title="Yoga studio" %}
`Level`: Beginner (green) · Intermediate (blue) · Advanced (red)

`Intensity`: Restorative (light blue) · Moderate (orange) · Power (red)
{% endtab %}

{% tab title="Beauty clinic" %}
`Downtime`: No downtime (green) · 1–2 days (orange) · 3+ days (red)

`Skin Type`: All types · Oily · Dry · Sensitive
{% endtab %}

{% tab title="Gym" %}
`Level`: Beginner · Intermediate · Advanced

`Age Group`: Adult · All Ages
{% endtab %}
{% endtabs %}

{% hint style="warning" %}
An attribute with no options **will not be saved**. Every attribute must have at least one option.
{% endhint %}

{% hint style="info" %}
Attributes currently work as **visual explainers**, not search filters. Customers see them, but cannot yet filter the catalog by attribute. If you need groupings that can be filtered, use **Category**.
{% endhint %}

Attributes are also available for **events**, in the same form.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.diro.app/en/operations/service-attributes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.