> 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/concepts.md).

# Concepts

The core building blocks you will see everywhere in Datalogz Control Tower.

### Assets

An **asset** is any resource in your BI environment: reports, dashboards, datasets and semantic models, dataflows, workbooks, apps, and more. Control Tower keeps a unified inventory of every asset across all your connected BI platforms, enriched with ownership, usage, lineage, and health information.

**What you do:** browse the inventory to see what exists, who owns it, and how it is used. Star the assets you care about, save filtered views for your team, and export lists when you need them.

### Platform Context

Every BI tool organizes content differently: Power BI uses workspaces, Tableau uses projects, Qlik Sense uses streams. **Platform Context** is the single term Control Tower uses for all of these, so you can work consistently across tools without translating each platform's vocabulary.

### Connectors

A **connector** links Control Tower to one of your BI platforms, such as Power BI, Tableau, or Qlik Sense. Using credentials you provide, it reads metadata from that platform on a schedule, so your inventory, monitors, and alerts stay current.

{% hint style="info" %}
Datalogz only reads **metadata**: titles, descriptions, configuration, lineage, usage patterns, refresh durations, and governance attributes. It never queries or accesses the data inside your reports. This can be described as read-only access to metadata only.
{% endhint %}

**What you do:** an admin sets up each connector once and keeps credentials current. Syncing happens automatically from there. Read more in [Datalogz Security](/guides/datalogz-security.md).

### Monitors

A **monitor** is a continuous check on your BI environment. Each monitor watches for a specific condition, such as a stale dataset, an unused report, or an unusual access pattern, and is tagged with the pillar it protects and a recommended fix. **Default monitors** are curated by Datalogz and work out of the box. **My Monitors** are your own: duplicate a default monitor and tailor its criteria to your organization's needs.

**What you do:** enable the monitors you need from the Monitor Catalog, set who gets notified, and adjust schedules if needed.

### Alerts

An **alert** is created when an asset breaches a monitor's rule. Each alert tells you the affected asset, what went wrong, who owns it, and what to do about it. Alerts have a status (to do, in progress, resolved) and a priority, and every change is recorded in an audit trail.

**What you do:** triage alerts from the Alerts page: assign them to team members, set priority, comment, and resolve. Bulk actions let you handle many alerts at once, and alerts close automatically when the underlying issue no longer exists.

### Teams

A **team** groups people who work with the same BI content, typically by department or function. Teams scope which connectors, views, and alerts members see, so everyone works on the content they are responsible for.

**What you do:** organize users into teams so access stays clean and alerts route to the people who own the affected content.

### Home dashboard

The **Home dashboard** is your team's daily starting point. It summarizes alerts by pillar, priority, and status, with a view of everything or just the items assigned to you.

**What you do:** check Home to see what needs attention today and jump straight into triage.

### BI360

**BI360** is the executive view of your entire analytics estate: inventory growth, adoption and engagement, license utilization, department health, and trends over time, across all connected BI tools.

**What you do:** use BI360 to track the health of your analytics estate over time and report progress to leadership.


---

# 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:

```
GET https://docs.datalogz.io/guides/datalogz-framework/concepts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.