> 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/goals-and-okrs/managing-and-tracking-goals/contributors.md).

# Contributors for Objectives, Key Results, and Initiatives

Contributors are people who actively help deliver an Objective, Key Result, or Initiative. They can view, comment, and make permitted check-ins without taking control of the goal definition or sharing.

Simple rule: add an owner for responsibility, add a contributor for active participation, and use **My OKRs** to see your owned, contributed, and delegated work together.

## Understand roles

**Owner:** Responsible for the goal. A goal can have multiple owners, subject to goal and workspace permissions.

**Contributor:** A named participant who can view, comment, and make permitted check-ins. There are no contributor permission tiers to configure.

**Delegate:** A delegate keeps their own role. Being a delegate does not make someone a contributor, and adding a contributor does not change delegation. See [Assign delegates to an OKR](https://help.rhythms.ai/goals-and-okrs/creating-goals/assign-delegates-to-an-okr.md).

Creating or approving a goal does not make you an owner or contributor, and does not add it to My OKRs. A person can hold several roles, so adding Alex as a contributor does not remove Alex as an owner or delegate.

## Add contributors

### From the goal page

1. Open the Objective, Key Result, or Initiative.
2. Open **More** and select **Contributors** when the list is empty. If the goal already has contributors, select the **Contributors** property.
3. Select or unselect people in the picker. You can select several people at once.
4. Close the picker to save all changes together. If you end with the same people you started with, nothing is saved.

You can add active workspace users with a standard license, up to 100 contributors per goal. Guest users cannot be contributors. If someone is not in your workspace, use the normal invite flow if you are authorized. Contributors have no percentage allocations or acceptance requests. A contributor can carry a short optional description of their contribution through chat or the API, but the picker does not show or edit it.

<figure><img src="https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2F6vzi6U0x10DitjxGfA93%2Fcontributors-picker-20261103.png?alt=media" alt="The Contributors picker on an Objective, with four people selected at the top of the list" width="420"><figcaption></figcaption></figure>

### From the check-in dialog

If a goal has no contributors yet and you can manage its people, open **More options** in the check-in dialog and select **Assign contributor**. This opens the same picker.

### During goal creation

In the creation form, choose owners and optional contributors for each goal. Drafts can include contributors. A contributor can view the draft but cannot publish it or check in until it is published.

### With chat

You can ask chat to create a draft with owners and contributors, add a contributor while keeping existing owners, or show the OKRs you contribute to this quarter. For example: "Create a draft objective for Q4 2026 called Improve player onboarding, with Lisa Wong and Rachel Davis as owners and Maria Gonzalez and David Kim as contributors."

<figure><img src="https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2Fri9d7nVokbyHccEzvoLM%2Fcontributors-chat-draft-20261103.png?alt=media" alt="A draft Objective created in chat, showing 2 owners and 2 contributors in its properties" width="640"><figcaption></figcaption></figure>

Chat follows the same permission rules as the app. If a name is ambiguous, chat asks you to clarify. For multi-item requests, it reports which items succeeded.

## What contributors can and cannot do

With no other role, contributors can read and comment when visibility and lifecycle allow it. They can check in on published, active goals. They can edit or delete only their own previous check-ins, and only while they still have check-in permission. On a rollup or integration goal, that covers only note-and-health check-ins with no numeric value.

For a manual metric, a contributor can enter a numeric value, note, and health. For example, Brina can record 18 completed interviews and add a note.

For a rollup or integration goal, a contributor can add a note and health but cannot overwrite calculated or integrated progress. For example, Brina can add a note about a launch blocker and update health while child-derived progress stays unchanged.

Contributors cannot edit a goal definition, configure its metric or data source, change alignment, manage people or sharing, approve, publish, close, archive, or delete it.

## Find the work you contribute to

### Use My OKRs

The **My OKRs** preset shows OKRs you own, contribute to, or are delegated. A goal appears once even if you have several roles. Leading a team, creating a goal, or approving it alone does not qualify.

<figure><img src="https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2FzhHkqYPbt9Yk04nmK3Hx%2Fcontributors-my-okrs-preset-20261103.png?alt=media" alt="The My OKRs preset chip and its explanation: OKRs you own, contribute to, or are delegated" width="360"><figcaption></figcaption></figure>

You can narrow the view with filters such as Time Period. An Owner = Current user filter limits results to ownership only. Remove it to see owned, contributed, and delegated work together.

### Use the Contributor filter

Add **Contributor** under **OKR Roles**. You can filter by a named person or Current user, switch on **Include your direct reports** or **Include all your reports**, or choose **Unassigned** to find goals with no contributors. Separate filter chips combine with AND, so Owner = Alex and Contributor = Sam finds goals where Alex is an owner and Sam is a contributor.

<figure><img src="https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2FeYBWjI5dBV0jVsSFvpDh%2Fcontributors-filter-20261103.png?alt=media" alt="The Add Filter list with Contributor under OKR Roles" width="240"><figcaption></figcaption></figure>

### In Reports

Reports also offer a **Contributor** filter next to Delegate. It accepts named people and Current user, but not Unassigned or the reporting shortcuts.

### Show the Contributor column

Open **Display › Customize alignment tree › Columns shown** and turn on the optional **Contributor** column. It is off in existing views by default. Goals without contributors show None.

<figure><img src="https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2Fdi6zqgiyQpTaWLRMT2uo%2Fcontributors-column-20261103.png?alt=media" alt="An OKR table with the Owner and Contributor columns side by side; goals without contributors show None"><figcaption></figcaption></figure>

## Viewing and access

Contributors can view a goal only when its visibility and lifecycle allow it. They do not see private child goals just because they can see the parent.

The **Who can view** dialog lists each person once and shows their roles together, such as Owner · Contributor. Role labels are read-only.

<figure><img src="https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2FcumGwIPNiSxtyBTy8deI%2Fcontributors-who-can-view-20261103.png?alt=media" alt="The Who can view dialog listing each person once with combined roles such as Owner · Contributor" width="580"><figcaption></figcaption></figure>

Removing a direct sharing grant does not remove contributor membership. Removing contribution also does not remove ownership, delegation, or another source of access. Use the Contributors control to manage contributor membership. See [Control who can see an OKR](https://help.rhythms.ai/goals-and-okrs/creating-goals/control-who-can-see-an-okr.md).

## Remove a contributor or leave

To remove someone else, open **Contributors**, unselect the person, and close the picker. No extra confirmation is needed. Their comments, check-ins, and attribution remain in history.

To leave a goal, remove only yourself. If you have other access, you keep it with no warning. If contribution was your only access, you see a warning that you will lose access. Confirm to leave or cancel to keep your membership. If Rhythms cannot confirm what access you would keep, you see the message "Could not check your remaining access. No changes were saved. Try again."

Archived goals are read-only, including leaving. Being the author of a check-in does not let you keep editing it after you lose check-in permission.

## Across the goal lifecycle

* **Draft:** Contributors can be selected and can view, but cannot publish or check in.
* **Published and active:** Contributors can comment and check in. Numeric updates depend on the update mode.
* **Closed or postponed:** Membership remains and contributors can still comment, but contributor check-ins are unavailable.
* **Archived:** Membership and history remain, but the goal is read-only.
* **Reopened or unarchived:** People who are still contributors can comment and check in again. Anyone removed earlier is not added back.
* **Clone or rollover:** The clone form preselects the original contributors, like owners. Change or clear the selection before you confirm. The selection applies only to the copied goal itself. Child goals copied along with it start with no contributors, so add them on each copy if you need them.

If a user is deactivated, they are removed as a contributor from every goal, as with delegates. Reactivating them does not restore those memberships. Their check-ins and activity history remain.

## Notifications

Adding or removing contributors is recorded in activity. People who are added or removed are notified through your existing channels. If someone is switched between owner and contributor in one change, they are notified of the role change. When a contributor leaves, the goal's owners are notified. Whoever made the change is not notified. Contributors are notified when a goal is archived or unarchived.

Adding a contributor does not subscribe them to every update. It does not broadcast every edit or check-in, automatically follow the goal, or assign overdue reminders.

## Frequently asked questions

**Does aligning a child goal make me a contributor?** No. Owning a child Objective aligned to another Objective does not automatically make you a contributor. Add contributors explicitly.

**Is this the same as contribution weights?** No. Metric contribution, such as rollup weights, and people contribution are separate concepts.

**Does adding a contributor subscribe them to every update?** No. Contributors are not automatically subscribed to every update.

## Related articles

* [Edit and update OKRs](https://help.rhythms.ai/goals-and-okrs/managing-and-tracking-goals/edit-and-update-okrs.md)
* [Assign delegates to an OKR](https://help.rhythms.ai/goals-and-okrs/creating-goals/assign-delegates-to-an-okr.md)
* [Control who can see an OKR](https://help.rhythms.ai/goals-and-okrs/creating-goals/control-who-can-see-an-okr.md)
* [OKR roles and permissions](https://help.rhythms.ai/workspace-settings-and-administration/team-users-and-access/okr-roles-and-permissions.md)


---

# 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/goals-and-okrs/managing-and-tracking-goals/contributors.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.
