> For the complete documentation index, see [llms.txt](https://docs.datalogz.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datalogz.io/guides/datalogz-framework.md).

# Datalogz Framework

## Datalogz Control Tower

Every enterprise has data infrastructure. Almost none has decision infrastructure.

Decision infrastructure is the layer that makes sure every decision taken inside the company, whether it comes from a dashboard, a deck, a person, or an AI agent, is traceable, reliable, accurate, consistent, and reached by the cheapest path available. Your data catalog knows your tables. Your quality tool watches your pipelines. Neither one watches the consumption layer, where people and agents actually decide things.

Datalogz Control Tower is that layer. It reads and continuously monitors your entire analytics estate across every connected platform, and turns what it finds into work that has an owner and an end state.

These docs cover setting Control Tower up, using it day to day, and the reference material behind it.

**Connected platforms:** Power BI, Tableau, Qlik Sense, Sigma, Spotfire, SharePoint, Databricks (preview), and Entra ID for identity.

### Start here

**Setting Control Tower up for the first time**

* [Getting Started](/guides/organizational-setup/getting-started.md): who in your organization needs to be involved, and what each person does
* [Connector Onboarding](https://docs.datalogz.io/guides/pages/cNx7TJbkfacbjlF6w988#id-1.-create-a-connector): connect your first BI platform
* [User Onboarding](https://docs.datalogz.io/guides/pages/cNx7TJbkfacbjlF6w988#id-2.-invite-members): add members, set up teams, assign roles
* [Log-in Methods](/guides/log-in-methods.md) and [Single Sign-On](/guides/single-sign-on-sso.md)

**Your platforms are connected and you are looking at your estate**

* [Alerts](/guides/alerts.md): what has surfaced, and what to do with it
* [Monitors](/guides/monitors.md): what Control Tower checks, and how to change it
* [Inventory](/guides/inventory.md): every asset across every tool, with Lineage for what depends on what
* [BI Similarity](/guides/bi-similarity.md): the duplicate and conflicting reports your teams built separately and never reconciled
* Semantic Intelligence (preview): the business concepts your organization runs on, mapped across the estate, with drift caught as definitions start to split
* [BI360](/guides/bi-360.md): the executive picture of health, cost, and coverage across the whole estate
* [Workflows](/guides/workflows.md): turn a finding into a routed, tracked action

### How it works

Two ideas hold the rest together.

**Monitoring is continuous.** Monitors check your connected platforms around the clock. When something needs attention, an alert is created, routed to an owner, and tracked until it is resolved. There is nothing to configure to begin: once a platform is connected, a curated set of core monitors starts running against it. Your team reviews what surfaces, assigns owners, and acts. Scanning, detection, routing, and tracking happen without you.

**Every finding sits under one of four pillars.** Security, Cost Management, Governance (which covers quality, ownership, and compliance), and Performance. The pillar tells you why a finding matters and helps you decide what to deal with first.

### What this means for you

You don't need to configure anything to get started. Once your BI platforms are connected, Control Tower begins monitoring with a curated set of default checks. Your team's job is to review the alerts that surface, assign owners, and act on them. Everything else, including scanning, detection, and tracking, happens automatically.

To learn more about the operational discipline behind the framework, we recommend reading our[ BI Ops Whitepaper](https://docs.datalogz.io/whitepaper/).


---

# 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.datalogz.io/guides/datalogz-framework.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.