> 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/consume/activate/overview.md).

# Overview

Activating is the final step in the consumer journey. After you discover, understand, and validate a Data Product, connect it to the tool or workflow that will use it.

Use the activation channel that matches how you want to consume governed data.

## Open the Activate menu

The Activate menu is your single starting point for every way to consume a Data Product, so you don't have to hunt for connection details per tool. From the Data Product page, select **Activate** in the Quick access bar to open it — it lists **MCP**, **BI Tools**, **APIs**, and **Database Client**.

<img src="/files/5RiRyGceBFHjUtjt0qHK" alt="" width="563">

If you prefer to browse the options in context, the Data Product's **How to activate** section surfaces the same paths as cards — Connect via MCP, Connect BI tools, Build on APIs, and Query via DB clients.

![How to activate section showing the available activation paths](/files/felpFTaoPoPZtAs9sV7y)

## Activation Channels

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Power BI</strong><br>Pick this when your deliverable is a report or dashboard — build on governed semantic models without exporting or re-modeling data.</td><td><a href="/pages/5d3ErEhlaBv5TXJCOrWJ">/pages/5d3ErEhlaBv5TXJCOrWJ</a></td></tr><tr><td><strong>DB clients</strong><br>Pick this when you'd rather explore and query in a familiar desktop SQL tool than in the browser.</td><td><a href="/pages/TUHfHehJfkTsDyv6Siee">/pages/TUHfHehJfkTsDyv6Siee</a></td></tr><tr><td><strong>APIs</strong><br>Pick this when an application, automation, or service needs governed data programmatically.</td><td><a href="/pages/LyBO1RyM3EvKbz3VR6eE">/pages/LyBO1RyM3EvKbz3VR6eE</a></td></tr><tr><td><strong>Consume with AI</strong><br>Pick this when you want AI clients or agents to discover and query data within governance.</td><td><a href="/pages/Iv7IrhZxYMLqhTFHWRF2">/pages/Iv7IrhZxYMLqhTFHWRF2</a></td></tr></tbody></table>

## Connection outcome

Connection is complete when the downstream tool can access the governed Data Product successfully and return the fields, metrics, or results you expect.

## Reference

For concepts, architecture, and full channel reference, see the [Activation section in Concepts](/concepts/foundations/activation.md).


---

# 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/consume/activate/overview.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.