> 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/september-11-2026-release-notes.md). # September 11, 2026 Release Notes ***This week:*** Upstream navigation on OKR graphs, smarter alignment suggestions, editable goal IDs, Early access controls, Ashby recruiting data in chat, and clearer Slack actions and notifications. ## New Features 🖥️ **Navigate Upstream** When you are looking at a team-filtered strategy map, it is now easier to see how the work connects to the bigger picture. Follow upstream relationships to the parent objectives and contributing teams that your current view supports, then jump into the selected OKR without losing your place. The map also keeps the context of your selection visible while you explore. *Try it: Open a strategy map, filter to a team, and select an objective to follow its upstream relationships.* 🖥️ **Smarter Alignment Suggestions** Finding the right parent for a Key Result is easier when the wording does not match exactly. Alignment suggestions now use your organization’s hierarchy and management context to surface relevant parents, rather than relying only on shared words. The picker also makes the current parent, closed candidates, and empty states clearer. *Try it: Open a Key Result with a non-obvious parent and review the suggested alignments.* 🖥️ **Editable Goal IDs** You can now give a goal a short ID that matches the code your team already uses in finance, planning, or another system. Edit it directly from the goal page or quick view; the new ID stays unique within your workspace, and existing links continue to resolve after a change. *Try it: Open any objective, Key Result, or initiative and select its short ID in the header.* 🖥️ **Early Access Controls** Workspace admins can now find eligible upcoming features in one Early access area and turn them on or off for their workspace. Each preview includes the context admins need to decide whether to enable it, while rollout controls keep eligibility and activation explicit. *Try it: Open Admin → Workspace → Early access to see whether your workspace has any previews available.* 🖥️ **Connect Ashby** Bring permitted recruiting data into the conversations where your team plans and decides. The Ashby connector is now available in the connector catalog, with setup prerequisites clearly listed before you connect. Each user can complete OAuth authorization to query only the recruiting records they are permitted to access. It is available to all tenants. *Try it: Open the connector catalog, select Ashby, and follow the setup steps to authorize your account.* ## Key Improvements * **Paginate BI exports** — Use the offset/limit pagination that BI connectors expect when reading REST API v2 list endpoints, so large extracts can move beyond the first page. * **Keep strategy maps stable** — Change team filters and graph grouping without losing the map, even when many team boxes are open. * **Refresh chat connections** — Chat V2 now refreshes connector catalogs in the background, so a recovered connection becomes available again without waiting for a new setup flow. * **Reliable default landing** — Users without a usable team now open All OKRs instead of being sent to an error page. * **Choose the current time period** — Admins can select any existing time period as current from its edit dialog, then return to automatic selection whenever they are ready. * **Show suggested reply actions** — Display the suggested action text directly on Slack quick-reply buttons, so people can choose the right response at a glance. * **Focus Slack offers** — Surface one concrete, well-grounded action tied to the conversation when Rhythms can contribute, and stay quiet when it cannot. * **Share accessible run links** — Show playbook-run notification links in Slack DMs only to recipients who can open them. --- # 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/september-11-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.