> 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/february-5-2026-release-notes.md). # February 5, 2026 Release Notes This week brings enhanced permission controls for OKR management, giving your organization fine-grained control over who can edit versus manage objectives and key results at every level. *** ## OKR Permissions: Granular Edit and Manage Controls ![image.png](https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2Fgit-blob-2554f3fb8ceb93214dc046c7c2874206fd0afb11%2F1770678588821-image.png?alt=media) Control exactly who can edit versus manage OKRs across your organization with separate permission settings. Edit permissions govern who can modify content, update progress, and submit check-ins, while manage permissions control administrative actions like deleting OKRs, transferring ownership, and changing delegates. These permissions can be configured at the organization level (affecting all OKRs), team level (affecting team-specific OKRs), and individual level (affecting personal OKRs). This separation gives administrators precise control over user capabilities, allowing team members to collaborate on OKR content while restricting sensitive administrative actions to designated leaders. Navigate to Settings › OKRs › Permissions to configure permissions for your organization. Learn more: [📄 Rhythms OKR Roles and Permissions](/workspace-settings-and-administration/team-users-and-access/okr-roles-and-permissions.md) *** ## Improvements * **Tenant Switching**: Switch between organizations more smoothly with improved loading states and streamlined authentication, making it easier to manage multiple workspaces * **Impersonation (Admin)**: Enhanced security and compatibility when support staff impersonate users to troubleshoot issues, enabling better assistance across Microsoft Teams and other environments * **API Performance**: Objective API endpoints now return optimized responses with reduced payload sizes, enabling faster page loads and smoother navigation ## Fixes * **Time Period Management**: Time periods now delete smoothly regardless of associated compliance data, resolving database constraint issues that previously blocked deletion --- # 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/february-5-2026-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.