> 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-2-2025-release-notes.md). # October 2, 2025 Release Notes ## **Enhanced Delegate Permissions** [Watch the video](https://www.loom.com/embed/4cfe8f36dba5448bbdb5492a32c34dfe) Executives and managers can now fully delegate OKR management to their team members without creating workflow bottlenecks. When you assign a delegate, they gain the ability to edit titles, descriptions, key results, targets, alignments, and time periods—essentially managing the entire objective on your behalf. This is particularly valuable for senior leaders who need to ensure their OKRs stay current while focusing on strategic priorities. Your delegates can make quick corrections, adjust metrics as business conditions change, and keep check-ins flowing smoothly. The system maintains appropriate guardrails: delegates cannot transfer ownership, modify delegate assignments, or delete objectives, ensuring accountability remains clear while enabling efficient collaboration across your organization. The full Help Center article is available [here](/goals-and-okrs/creating-goals/assign-delegates-to-an-okr.md). *** ## Improvements * **Delegation Notifications**: Notifications now clearly communicate the full scope of what delegates can do, helping team members understand that delegates can manage entire objectives including editing details and handling updates, making it easier to delegate with confidence. * **Time Period Selection**: You can now view both Annual and Current Quarter OKRs simultaneously in the default time period filter, enabling you to see the full strategic context without manually switching between timeframes. * **System Performance**: AI-powered features now respond faster through intelligent prompt caching that reduces processing overhead by up to 10x, helping you get insights more quickly. ## Fixes * **Navigation & Display**: Improved how objectives open from external sources like Slack and chat, now displaying them in full page view for easier reading and interaction. Enhanced navigation for users across multiple workspaces, ensuring notifications route you to the correct workspace context. * **Data Quality & Security**: Progress rollups now respect visibility settings more carefully, ensuring information only flows up the hierarchy when all viewers have appropriate access. Improved filtering accuracy for child items in tree and board views when using label filters. * **System Reliability**: Authentication now handles token refresh more smoothly without displaying unnecessary error messages, helping you stay focused on your work. --- # 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-2-2025-release-notes.md?ask=&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.