> 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-17-2026-release-notes.md).

# April 17, 2026 Release Notes

## New Features

🆕 **Documents & Library** We've renamed Dashboards to **Documents**. You were building reports, briefs, and planning docs — not just dashboards — so the new name better fits what you're actually creating. They now live in a new **Library** page where you can browse, search, and organize everything in one place. All your existing work is still there, just under a new name.

🆕 **Admin Connector Controls** Custom MCP connectors are flexible, but not every team wants everyone adding their own. Admins can now control who's allowed to add custom connectors — restrict to admins only or open it to all users. You can also pre-configure shared OAuth credentials so other users connect with a single click instead of registering their own OAuth app. Less setup friction for the team, more control for the admin.

## Improvements

**Copy Chat Messages** — Hover over any AI response or user message and click copy. Formatting is preserved — bold, bullets, links, and structured goal data all paste cleanly into Slack, Docs, or email.

**Sharing Notifications** — Sharing permissions now apply to the whole team (e.g. sharing with the Engineering organization will update permissions to any sub-teams under Engineering).

**Smarter Atlassian Custom Fields** — Auto-update setup for Jira now better understands custom fields, making it easier to connect the right data to your Key Results.

**Connectors Reconnecting Fix** — Reconnecting a Connector now opens a reauthorization flow.


---

# 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-17-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.