> 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/bi-360/set-up-department-insights.md).

# Set up department insights

Department insights slice BI 360 by team, function, or business unit (for example Marketing, Finance, Sales, or R\&D), so you see adoption, license use, and content ownership per department instead of only tenant-wide.

Once department data is connected, BI 360 adds:

* **Department User Breakdown**: adoption and activity per team.
* **License Utilization by Department**: allocated vs. active licenses per team.
* **Department Dashboard Ownership**: content ownership and inactivity per team.
* **Department BI Health Snapshot**: top active and at-risk departments on the Executive Summary.

### Set up via Entra ID (automated)

Datalogz joins the department field on each user account in Entra ID to the users, owners, and licenses it ingests from your BI tools.

1. Confirm Entra ID is configured for your tenant.
2. Go to **Settings > User Directory**.
3. Set up the **Entra ID** connector (see the Entra ID guide).
4. Department dimensions appear in BI 360 within one ingestion cycle.

### Set up via a mapping file (manual)

1. Go to **Settings > User Directory**.
2. Choose which tools (Power BI or Tableau) you want to map assets to departments for.
3. Create a CSV or Excel file with the columns asset\_name, asset\_id, and department. You can rename department to the language you use, for example Business Units.
4. Upload the file on the **Asset Mapping** card and click **Sync**.

{% hint style="info" %}
Without Entra ID or a mapping file, the rest of BI 360 works as normal. The department breakdowns are simply hidden from the Organizational, Data and Reporting tabs and from the Executive Summary.
{% endhint %}


---

# 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/bi-360/set-up-department-insights.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.