> 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/resources/vulcan/activation.md).

# Activation

You've defined your models, validated them, and shipped a semantic layer. Now downstream tools need to read it: a dashboard in PowerBI, a notebook in Python, a customer-facing app, an analyst running ad-hoc SQL.

Activation is how each of those surfaces connects to the same governed definitions, without re-modeling the data per tool.

```mermaid
%%{init: {"theme":"base","themeVariables":{"fontFamily":"PP Neue Montreal, Inter, Helvetica Neue, Arial, sans-serif","fontSize":"14px","primaryColor":"#EDE9E5","primaryTextColor":"#242422","primaryBorderColor":"#242422","lineColor":"#242422","secondaryColor":"#D6CDC6","tertiaryColor":"#FFFFFF","clusterBkg":"#EDE9E5","clusterBorder":"#54DED1","edgeLabelBackground":"#FFFFFF"},"flowchart":{"curve":"basis","padding":12,"nodeSpacing":40,"rankSpacing":50}}}%%
graph LR
    subgraph SL ["Your Semantic Layer"]
        direction TB
        Sem["<b>Dimensions · Measures<br/>Segments · Metrics</b>"]
    end

    subgraph CH ["Activation Channels"]
        direction TB
        API["<b>REST / GraphQL API</b><br/>Apps & services"]
        BI["<b>BI tools</b><br/>PowerBI · Tableau · Superset"]
        SQL["<b>MySQL wire protocol</b><br/>IDEs · ad-hoc SQL"]
        PY["<b>Python</b><br/>Notebooks · ML training"]
    end

    subgraph OUT ["Where it lands"]
        Apps[Internal tools, customer apps]
        Dash[Dashboards, reports]
        Adhoc[Ad-hoc analysis, exports]
        Models[Trained models, features]
    end

    Sem --> API --> Apps
    Sem --> BI --> Dash
    Sem --> SQL --> Adhoc
    Sem --> PY --> Models

    classDef primary-teal fill:#54DED1,color:#202F36,stroke:#009293,stroke-width:1.5px,font-weight:600;
    classDef dark-teal    fill:#009293,color:#FFFFFF,stroke:#242422,stroke-width:1.5px,font-weight:600;
    classDef surface      fill:#FFFFFF,color:#242422,stroke:#242422,stroke-width:1px;

    class Sem dark-teal;
    class API,BI,SQL,PY primary-teal;
    class Apps,Dash,Adhoc,Models surface;
```

## What activation gives you

Your semantics are the contract. Every channel reads from the same definitions, so a metric called `total_revenue` means the same thing in PowerBI, in a Python notebook, and in a customer-facing API. No re-modeling, no drift, no "which dashboard is right?"

## Channels

**1. Build applications (API).** Hit the REST or GraphQL endpoint to pull semantic data into internal tools, customer-facing products, or workflows. The semantics handle the joins and aggregations; your app just asks for measures and dimensions. See the [Vulcan API Guide](/concepts/resources/vulcan/guides/vulcan_api_guide.md).

**2. Visualize (BI tools).** Connect PowerBI, Tableau, or Superset over the MySQL wire protocol. Your dimensions and measures show up as fields, ready for charts and drilldowns. No SQL in the dashboard, no metric definitions duplicated per workbook. See [BI tools](/concepts/resources/vulcan/activation/bi.md).

**3. Explore (MySQL).** Point any MySQL-compatible client (CLI, DBeaver, JetBrains, etc.) at the same wire protocol for ad-hoc querying or to power exports and integrations. See [MySQL](/concepts/resources/vulcan/activation/mysql.md).

**4. Train models (Python).** Pull semantic data into a notebook with the standard `mysql-connector-python` library. The features and labels you train on are the same ones your dashboards report against. See [Python](/concepts/resources/vulcan/activation/python.md).

## How it pays off

Define the metric once. Every team, tool, and use case downstream gets the same answer. That's the point of investing in the semantic layer in the first place.


---

# 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/resources/vulcan/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.