> 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-9-2025-release-notes.md).

# October 9, 2025 Release Notes

This week we enhanced our integrations ecosystem and strengthened our Viva Goals migration support with important fixes for weighted contributions and AI rollups.

## Asana Integration Enhancements

Connect your Asana workspaces to Rhythms with improved security and smoother authentication. We've updated the Asana integration to use granular permission scopes, ensuring your team only grants the specific access needed for OKR tracking. The integration now supports broader distribution across your organization with an enhanced OAuth connection flow that makes connecting workspaces more reliable. These updates directly respond to customer requests and make it easier for teams to link their project management work in Asana directly to strategic objectives in Rhythms, with appropriate security controls that align with enterprise standards.

Learn more about [enabling integrations for your workspace](/connectivity/manage-connectors-for-your-workspace.md) and setting up [auto-updates for your key results and initiatives](/connectivity/connectors/set-up-automatic-updates-from-a-connector.md).

***

## Improvements

* **AI Rollup for Weighted Contributions**: Use custom contribution weights with AI-powered progress rollup. Parent Objective progress accurately reflects each Key Result's assigned weight percentage. *Requires weighted contributions feature (available on request).*
* **Admin Access Control**: Admin users can now access all private views across the workspace, making it easier to provide support and troubleshoot view-related issues for team members.
* **OKR Co-ownership Management**: You can now add co-owners to OKRs even when inactive owners exist, removing the previous requirement to remove inactive owners (such as employees on leave) before adding new active owners.
* **View Management**: Enhanced the visibility controls for user-level pinned views, helping you manage personal view preferences more easily.

## Fixes

* **User Interface & Navigation**: Enhanced the overall user experience with multiple interface improvements. Report date ranges now display years intelligently with preset options matching common use cases, and shared dashboard links are now accessible to team members without lock icon issues.


---

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