> 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/october-16-2025-release-notes.md).

# October 16, 2025 Release Notes

## Google Sheets Integration

Track key results using data that's already in your spreadsheets. When working with Rhythms AI, you can now reference values from your Google Sheets, like revenue numbers, customer counts, or project metrics, to inform your OKR updates. Simply connect your Google Sheet, and Rhythms can pull the latest data from your sheets when you need it. This eliminates manual data entry and helps keep your goals aligned with the metrics your team already tracks in spreadsheets.

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

Learn more about setting up auto-updates with Google Sheets [Connect a tool to a Key Result for automatic updates](/connectivity/connectors/set-up-automatic-updates-from-a-connector.md)

***

## Improvements

* **Reports Status Filtering:** Filter reports by OKR status to focus on what matters. Exclude closed or postponed objectives from check-in compliance reports to see only active work in progress.
* **Contribution Visibility**: Contribution percentages now display with intuitive pie chart indicators, helping you quickly understand how aligned objectives roll up to parent goals. *Requires weighted contributions feature (available on request).*

## Fixes

* **User Lookup with Duplicate Names**: User selection now displays email addresses alongside names when multiple users share identical names, improving accuracy when assigning objectives or selecting collaborators.
* **Licensing Management**: User status labeling is now clearer with streamlined license type settings.


---

# 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/october-16-2025-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.