> 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/march-25-2026-release-notes.md).

# March 25, 2026 Release Notes

## New Features

🆕 **Progress Plans**\
Goals don’t move in straight lines — so why should status calculations assume they do? Set milestone targets at specific dates, and Rhythms measures progress against the nearest milestone instead of a linear projection. A sales goal that’s flat in January and spikes in March will finally show the right status throughout.

[Watch the video](https://www.loom.com/embed/2ba3db02baeb4031a8173074f408c75b)

🆕 **Check-In Queue**\
When multiple goals are due for a check-in, Rhythms lines them up and walks you through them one by one. Each form is pre-drafted — value, status, and note — so you review, adjust if needed, and move to the next. It auto-advances when you submit. What used to be a tab-juggling chore is now a focused five-minute ritual.

## Improvements

* **Starred dashboards** — Star any dashboard to pin it to your sidebar for quick access. Or duplicate one with “Make a Copy” to use it as a starting point for something new.
* **Bulk sharing** — Add multiple users or teams at once when sharing OKRs, views, or dashboards. No more sharing one person at a time.


---

# 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/march-25-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.