> 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-30-2026-release-notes.md).

# September 30, 2026 Release Notes

*This release:* It is now easier to bring the right people into work and manage contribution weights with Rhythms Chat, and directory-driven profile updates are more reliable.

## New Features

### 🖥️ Contextual Invitations and Team Creation

Invite people or create teams directly from the flow where you are assigning owners, delegates, teams, or membership. When an email address is not yet recognized, you can invite that person by email, including inviting multiple people at once. When a team search has no exact match, you can create the team without leaving your current task. This keeps assignment and membership work moving without extra navigation.

*Try it:* Start assigning an owner, delegate, team, or member, then invite a new person or create a team when it is not already available.

### 🖥️ Set Contribution Weights with Rhythms Chat

Use Rhythms Chat to set how much each child contributes to a roll-up parent. You can also distribute contribution percentages equally across contributing children. This reduces the manual effort of reweighting parents with many child key results. It makes contribution management faster and less error-prone.

*Try it:* Ask Rhythms Chat to set contribution percentages for a roll-up parent or divide them equally across its children.

## Key Improvements

* **More reliable SCIM profile updates.** Directory sync now uses a stable identity-provider ID to match people, so existing Rhythms users are updated when their email address or display name changes. This helps prevent duplicate accounts after routine identity-provider updates.


---

# 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 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-30-2026-release-notes.md?ask=<question>&goal=<user_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 `automate deployments from our CI pipeline` 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.
