> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/concepts/foundations/activation.md).

# Activation

Building a data product is the starting line, not the finish. Activation is how you make it operational, discoverable, consumable, and ready to power real business experiences across your teams and tools.

## What is activation

**From built to useful. That's the gap activation closes.**

A data product sitting in a catalog is like a finished product locked in a warehouse. Activation is the distribution layer. It takes your semantic models, quality checks, and governed data and makes them live and reachable for every team and tool in your organisation.

#### The three pillars

{% hint style="success" %}
**Operational**

Your data product is running, monitored, and ready to serve queries. Health, freshness, and quality checks pass before any consumer touches it.
{% endhint %}

{% hint style="info" %}
**Consumable**

Every dimension, measure, and join is exposed through a consistent interface: REST, SQL, or a BI connector. Consumers don't write ETL; they write questions.
{% endhint %}

{% hint style="success" %}
**Buildable**

Teams can create dashboards, applications, and pipelines directly on top of the product. The product becomes a platform, not just a dataset.
{% endhint %}

### Activation channels

**Multiple ways to reach your data.**

Pick the channel that fits your consumer. Analysts, developers, and applications all have a path in. From a Data Product, the **Activate** menu surfaces these channels: MCP, BI Tools, APIs, and Database Client.

<figure><img src="/files/MtxbcmQ3VzVoryWOyfOI" alt=""><figcaption><p>Every channel a consumer might use, BI, SQL client, API, or AI, is one click away on the product itself. No separate setup, no second system to find.</p></figcaption></figure>

<table data-view="cards"><thead><tr><th>Channel</th><th data-card-target data-type="content-ref">Open</th></tr></thead><tbody><tr><td><strong>BI tools</strong><br>Connect BI tools directly to your semantic layer.</td><td><a href="/pages/xn81dssSa4QJelN6j4Yn">/pages/xn81dssSa4QJelN6j4Yn</a></td></tr><tr><td><strong>Database clients</strong><br>Query semantic models from any MySQL-compatible client.</td><td><a href="/pages/hfhrjHto0deTXixAR71P">/pages/hfhrjHto0deTXixAR71P</a></td></tr><tr><td><strong>Data Product API</strong><br>Query, inspect, and build on data products through REST APIs.</td><td><a href="/pages/eHl8Fw78AESzYrS1gSkV">/pages/eHl8Fw78AESzYrS1gSkV</a></td></tr><tr><td><strong>Build Experiences</strong><br>Build apps and pipelines on top of semantic models.</td><td><a href="/pages/bvIua9WYTpiCk1HCXkSv">/pages/bvIua9WYTpiCk1HCXkSv</a></td></tr><tr><td><strong>AI Activation</strong><br>Expose data products to AI clients through MCP.</td><td><a href="/pages/dZ7lI6MBu1cHurZ4AQAi">/pages/dZ7lI6MBu1cHurZ4AQAi</a></td></tr></tbody></table>

### Choose your activation path

**Where do you want to start?**

Pick the path that matches your goal: quick connection or full understanding.

{% tabs %}
{% tab title="Get started: Activate in minutes" %}
Step-by-step setup guides for each channel. These live in the Consume section. Follow one from prerequisites to your first result.

<table data-view="cards"><thead><tr><th>Guide</th><th data-card-target data-type="content-ref">Open</th></tr></thead><tbody><tr><td><strong>Power BI Desktop</strong><br>Install the connector and build your first report.</td><td><a href="/pages/UqD6JwbNI9bTdUm5xK9L">/pages/UqD6JwbNI9bTdUm5xK9L</a></td></tr><tr><td><strong>Power BI Service</strong><br>Publish via on-premises gateway.</td><td><a href="/pages/euZelJX7xGsDFXoEgSGJ">/pages/euZelJX7xGsDFXoEgSGJ</a></td></tr><tr><td><strong>Tableau</strong><br>Connect Tableau Desktop to a data product.</td><td><a href="/pages/gMgoEJhBslH5lPxbqWOv">/pages/gMgoEJhBslH5lPxbqWOv</a></td></tr><tr><td><strong>MySQL Client</strong><br>Connect from the command line.</td><td><a href="https://github.com/moderndatacompany/dataos/blob/main/documentation/consume/activate/mysql-clients/mysql/README.md">https://github.com/moderndatacompany/dataos/blob/main/documentation/consume/activate/mysql-clients/mysql/README.md</a></td></tr><tr><td><strong>DBeaver</strong><br>Connect from a visual SQL client.</td><td><a href="https://github.com/moderndatacompany/dataos/blob/main/documentation/consume/activate/mysql-clients/dbeaver.md">https://github.com/moderndatacompany/dataos/blob/main/documentation/consume/activate/mysql-clients/dbeaver.md</a></td></tr><tr><td><strong>APIs</strong><br>Authenticate and make your first API call.</td><td><a href="/pages/eHl8Fw78AESzYrS1gSkV">/pages/eHl8Fw78AESzYrS1gSkV</a></td></tr><tr><td><strong>AI Activation</strong><br>Connect an AI client to the Data Product MCP server.</td><td><a href="/pages/dZ7lI6MBu1cHurZ4AQAi">/pages/dZ7lI6MBu1cHurZ4AQAi</a></td></tr></tbody></table>
{% endtab %}

{% tab title="Deep dive: Reference" %}
In-depth reference for each channel: full API specs, field definitions, patterns, and build guides.

<table data-view="cards"><thead><tr><th>Reference</th><th data-card-target data-type="content-ref">Open</th></tr></thead><tbody><tr><td><strong>Data Product API</strong><br>Full endpoint reference with request and response details.</td><td><a href="/pages/eHl8Fw78AESzYrS1gSkV">/pages/eHl8Fw78AESzYrS1gSkV</a></td></tr><tr><td><strong>Build Experiences</strong><br>Deploy or link a data application on top of a data product.</td><td><a href="/pages/bvIua9WYTpiCk1HCXkSv">/pages/bvIua9WYTpiCk1HCXkSv</a></td></tr><tr><td><strong>AI Activation</strong><br>How Data Product MCP works and what trust boundaries apply.</td><td><a href="/pages/dZ7lI6MBu1cHurZ4AQAi">/pages/dZ7lI6MBu1cHurZ4AQAi</a></td></tr><tr><td><strong>BI tools</strong><br>Power BI and Tableau reference guides.</td><td><a href="/pages/xn81dssSa4QJelN6j4Yn">/pages/xn81dssSa4QJelN6j4Yn</a></td></tr></tbody></table>
{% endtab %}
{% endtabs %}


---

# 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://v2.dataos.info/concepts/foundations/activation.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.