> For the complete documentation index, see [llms.txt](https://docs.euno.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.euno.ai/support-resources/release-note/april-2026.md).

# April 2026

## Euno Release Notes — April 2026

### New Features

[Data Glossary](/using-euno/data-glossary.md) Enhancements — create terms directly from the resource sidepanel markdown descriptions, redesigned glossary term sidepane

[MCP OAuth](/ai/mcp-setup.md) — OAuth authentication and workspace selection for MCP connections

BI Certification — certified and endorsed badges now collected from Looker, Tableau, and Sigma into a normalized `meta.bi_certified` property

### Integration Improvements

[Sigma](/sources/business-intelligence/sigma-integration.md)

* New impressions integration via Audit Log export
* Snowflake usage: "used" relationships on workbooks, elements, and data models
* Formula lineage for warehouse table elements

[Power BI](/sources/business-intelligence/powerbi-integration.md)

* Dataflow support with intra-semantic-model table dependencies extracted from M/Power Query expressions
* Power BI Links support

[Tableau](/sources/business-intelligence/tableau-integration.md)

* Support for more upstream dataset technologies

[Omni](/sources/business-intelligence/omni-integration.md)

* Label tag support

Various bug fixes and performance improvements across integrations.

### AI Assistant

* Glossary term support in assistant and MCP
* `verify_eql` tool added to assistant
* [Impact Analysis](https://docs.euno.ai/using-euno/impact-analysis) improvements


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.euno.ai/support-resources/release-note/april-2026.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.