> 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/release-notes/archive/2.4.0.md).

# 2.4.0

Release date: April 7th, 2025

#### 1. Overview

Release 2.4 focuses on deepening platform control, expanding monitoring capabilities, and laying the groundwork for scalable team-based functionality. Key improvements include backend support for team-specific data views, a centralized monitor summary dashboard, and enhancements to connector management—pushing forward our goal to deliver actionable, secure, and user-friendly BI operations.

***

#### 2. New and Updated Features

* **Teams Backend Views**:

  Implemented a new backend framework for generating filtered views based on `platform_context_id`, enabling precise data segregation and enhanced query performance. This improves team-level data access control and lays the groundwork for future team-based UI features.
* **Connector Settings Improvements** (related to Teams view update):
  * Initiated support for connector deletion and better backend handling.
  * Added health status tracking for connectors.
  * Introduced a connector history log for auditing changes such as credential updates and toggle modifications.

***

#### 3. Monitors

**Monitors Summary Page**:

Released a centralized dashboard to track monitor alerts across categories (e.g., security, performance, governance).

* Provides visual alert distribution by Pillar.
* Enables filtering by date range and severity.
* Supports trend analysis to help customers understand overall BI health at a glance.

***

#### 4. Fixed Issues and Bugs

* **Multiple Root Accounts** issue is fixed (Now it’s possible to have multiple Root accounts)
* **Removing the Admin User leaves the Teams created by that User useless**. That issue is fixed now by transferring the ownership to the user deleting the Admin User
* Frontend Improvements.

***

#### 5. Known Bugs and Limitations

* Admins shouldn’t see the teams which they are not a part of, in the Teams Dropdown. Since they are admins, they should have an option to request to be a part of the team to Owner. \[We can cover this in the upcoming releases]
* All root users and the user who is creating the team should be a part of the team by default.

***

#### 6. Breaking Changes

* There are no breaking changes in this release


---

# 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/release-notes/archive/2.4.0.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.
