> 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-25-2026-release-notes.md). # February 25, 2026 Release Notes ## New Features 🆕 **Salesforce, Mixpanel & Granola Integrations** Three new integrations that connect the tools your teams already use to your OKRs. Salesforce syncs pipeline and deal data directly to Key Results — revenue goals update themselves. Mixpanel brings product analytics in — funnel completion, retention, event counts — so product goals track real usage, not estimates. Granola connects meeting notes and transcripts, so conversation context is available right in chat. All three connect through the standard integration setup. ## Improvements * **Richer activity feed** — Status changes, entity links, and rollup updates now appear as distinct, scannable entries instead of generic log lines. * **View permissions** — Control who can view, edit, and manage any saved OKR view. Restrict or open access without affecting other views. * **Drag-to-reorder goals** — Reorder top-level goals by dragging them in the grid. The order persists across sessions and is visible to everyone with access. * **Faster comments** — Comment creation is twice as fast. What took 3–4 seconds now takes under two. * **Customizable default views** — Make the "All OKRs" view your own with filters and column preferences that save per-user and persist across sessions. * **Dashboard Q\&A** — Ask questions about a dashboard in chat and get answers with citations. The assistant reads the live dashboard and references specific sections. * **@mention teams and labels** — Reference teams and labels in comments and dashboards. Mentioned teams get notified; mentions render as clickable chips. * **Dashboard labels and filters** — Organize dashboards with labels and filter by creator to quickly find the one you're looking for. * **Pylon integration** — Connect Pylon support tickets so customer issue data can inform goal progress and surface in chat. --- # 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-25-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.