> 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/november-20-2025-release-notes.md). # November 20, 2025 Release Notes This week brings a significant advancement in how Rhythms automatically determines OKR status across your organization, along with important improvements to permissions management, key result editing, and system reliability. ## Automatic Status Rollup Now Available to All Users Rhythms now automatically calculates status for parent objectives and key results based on their children's progress, making this capability available to every user by default. When your team checks in on their key results, parent objectives immediately reflect updated status calculations—eliminating manual status updates and ensuring leadership always sees accurate, real-time progress across the organization. This automated status computation works alongside progress rollups to give you a complete, always-current picture of how work is tracking. The system intelligently determines which children contribute to status calculations and handles complex hierarchies where objectives roll up to parent key results. Read [How parent OKR progress and status roll up](/goals-and-okrs/managing-and-tracking-goals/how-parent-okr-progress-and-status-roll-up.md) to learn more. *** ## Improvements * **View Sharing Permissions**: Share views with granular permission levels (View, Edit, Manage) using the same unified sharing interface available for dashboards, making it easier to control who can see and modify your custom OKR views * **Closed Key Results Editing**: Edit current values and reopen closed Key Results when corrections are needed, allowing you to fix data entry mistakes or reactivate work that was prematurely marked complete * **Postponed Status Handling**: Key Results marked as "postponed" now automatically become non-contributing (weight = 0) and are excluded from parent rollup calculations, helping you accurately reflect which work is actively contributing to goals * **Excel Integration for Large Files**: Work with large Excel files (56MB+) and successfully select sheets when setting up auto-updates, enabling automatic progress tracking from complex spreadsheets * **Enhanced Check-in Experience**: The check-in form now automatically focuses on the input field when opened, metric switching properly clears default values with appropriate placeholder examples, and you can properly unpin views without accidentally deleting them * **AI Report Summaries**: AI-generated report summaries no longer include technical identifiers, making them more readable and professional for sharing with stakeholders ## Fixes * **Data Synchronization**: Improved reliability when handling OKR deletions, comment thread processing, and default view preservation during tenant data operations * **Integration Accuracy**: Resolved Jira progress calculation issues for users with connections in multiple environments * **Navigation**: Fixed page navigation in Team Reports view and addressed display flickering during scrolling --- # 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/november-20-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.