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

# April 1, 2026 Release Notes

## New Features

**🆕 Presentation Editor** Turn any dashboard into a slide deck without touching PowerPoint. Generate editable slides directly from your dashboard, then refine them — edit text inline, drag elements to reposition, resize with handles. Download as a PowerPoint file when you’re done. Your board deck, QBR, or all-hands presentation starts from live data, not a copy-paste job.

🆕 **Asana Integration**\
Your team tracks work in Asana — now that work can drive your OKRs. Connect Asana and your Key Results update automatically as tasks are completed. No manual counting, no end-of-week scramble to update progress.

🆕 **Excel Online Integration**\
If your numbers live in a spreadsheet, they can now live in your OKRs too. Connect an Excel Online workbook and Rhythms pulls the latest values daily — so your finance, ops, or planning metrics are always current in your goals.

🆕 **Short Goal IDs**\
Reference any goal with a human-readable ID — OBJ-42, KR-123, INIT-7 — instead of a long URL. Use them in Slack, Linear, Jira, PRs, or meeting notes. Prefixes are customizable per goal type in your settings.

## Improvements

* **Web search in chat** — The AI can now search the web during a conversation to pull in live data — market benchmarks, competitor info, industry context — without you leaving Rhythms.
* **Azure DevOps PAT authentication** — Connect Azure DevOps using a Personal Access Token alongside the existing OAuth option, for teams that need more control over their integration setup.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://help.rhythms.ai/release-notes/april-1-2026-release-notes.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 `build a script that syncs our docs to a CMS` 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.
