> 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/owners-delegates-and-contributors.md).

# Owners, delegates and contributors

Each Objective, Key Result and Initiative in Rhythms can have three types of people assigned to it: owners, delegates and contributors. Assigning the right role ensures that accountability is clear, progress is kept current, and the people doing the work can report on it.

This article explains what each role is for, when to use it, and how the role affects permissions and check-in reminders.

## Overview of roles

| Role        | Purpose                                                                                       | Typical assignee                                    |
| ----------- | --------------------------------------------------------------------------------------------- | --------------------------------------------------- |
| Owner       | Accountable for the outcome. Has full control of the OKR, including its people and lifecycle. | The leader answerable for the result                |
| Delegate    | Maintains the OKR on the owner's behalf. Receives check-in reminders in place of the owner.   | Chief of staff, analyst, program or product manager |
| Contributor | Helps deliver the outcome and reports progress through check-ins. Cannot change the OKR.      | Team members doing the work                         |

To decide which role to assign, consider who is accountable for the result, who maintains the OKR, and who contributes to the work. In many cases a single owner is sufficient. Add delegates and contributors when these responsibilities are held by different people.

Contributors are on by default. Workspace admins can turn off new contributor assignments in **Settings › OKRs › Model customization**; existing contributors keep their access and check-ins.

## When to assign each role

### Assign an owner when

* The person is answerable for whether the OKR is achieved, for example in business reviews or reporting to leadership.
* The person needs to manage who works on the OKR, change its check-in reminders, or archive or delete it.

Assign ownership based on accountability, not on who updates the OKR. Owners have full control of the OKR and appear as the accountable party in views and reports.

Rhythms supports more than one owner per OKR. We recommend a single owner for each Key Result so that accountability for the result is unambiguous. Reserve multiple owners for Objectives or Initiatives that are formally co-led.

### Assign a delegate when

* The owner remains accountable but another person is responsible for keeping the OKR current.
* Check-in reminders should go to someone other than the owner.
* The person also needs to maintain the OKR's details, such as its title, dates, metric or alignment.

{% hint style="warning" %}
Important: When an OKR has at least one delegate, check-in reminders go to the delegates and no longer go to any of the owners. If the owner should continue to receive reminders, assign the other person as a contributor instead.
{% endhint %}

### Assign a contributor when

* The person contributes to the outcome and should report progress through check-ins.
* The person needs access to an OKR with limited visibility without permission to edit it.
* You want the people involved in the work to be visible on the OKR and in My OKRs.

Contributors do not receive check-in reminders and are not counted as overdue. If a person must be reminded to check in, assign them as the owner or a delegate.

### Recommended practices

* Assign one accountable owner. Avoid assigning ownership to a group or a committee. Name the individual responsible for driving decisions and resolving blockers.
* Separate accountability from maintenance. For senior leaders' OKRs, keep the leader as owner and assign a delegate to maintain the OKR and complete check-ins.
* Assign contributors deliberately. Add the people who do the work, rather than everyone with an interest in the OKR. To give others visibility, share the OKR instead.
* Keep the delegate list short. Assign only the people who will update the OKR. When several delegates share an OKR, agree who is responsible for which updates.
* Assign roles during planning. Confirm owners, delegates and contributors before the period starts so that reminders reach the right people from the first check-in.
* Review roles when responsibilities change. Changing the owner does not change the delegates or contributors. Update them when people change roles or leave the team.

## Assign people to an OKR

You need manage permission on the OKR to add or remove owners, delegates and contributors.

1. Open the Objective, Key Result or Initiative.
2. Select the Owner, Delegate or Contributors property. If the OKR has no delegates or contributors yet, select **More**, then **Delegate** or **Contributors**.
3. Select the people to assign, then close the picker to save your changes.

You can also assign people when you create an OKR, or ask Rhythms in chat. For example: “Add Sarah Chen as a delegate and Maria Gonzalez and David Kim as contributors on the Q1 Revenue OKR.”

For detailed instructions, see [Assign delegates to an OKR](https://help.rhythms.ai/goals-and-okrs/creating-goals/assign-delegates-to-an-okr.md) and [Contributors for Objectives, Key Results, and Initiatives](https://help.rhythms.ai/goals-and-okrs/managing-and-tracking-goals/contributors.md).

## Key differences

|                                  | Owner                          | Delegate | Contributor |
| -------------------------------- | ------------------------------ | -------- | ----------- |
| Accountable for the result       | Yes                            | No       | No          |
| Edit the OKR                     | Yes                            | Yes      | No          |
| Submit check-ins                 | Yes                            | Yes      | Yes         |
| Manage people, archive or delete | Yes                            | No       | No          |
| Receives check-in reminders      | Only if there are no delegates | Yes      | No          |

Permissions can vary with your workspace settings. For full details, see [OKR roles and permissions](https://help.rhythms.ai/workspace-settings-and-administration/team-users-and-access/okr-roles-and-permissions.md).

## Check-in reminders

Check-in reminders are sent on the OKR's check-in rhythm. Who receives them depends on whether the OKR has delegates.

| If the OKR has                             | Reminders are sent to |
| ------------------------------------------ | --------------------- |
| Owners only                                | Owners                |
| Owners and one or more delegates           | Delegates only        |
| Owners and contributors, with no delegates | Owners only           |

Contributors never receive check-in reminders.

Example: Priya Shah owns the Key Result “Reach $5M ARR.” She assigns her analyst, Sam Lee, as a delegate and three account executives as contributors. Sam receives the weekly check-in reminder and Priya does not. The account executives can submit check-ins, but they are not reminded and are not counted as overdue.

To change how often reminders are sent, see [Set a check-in rhythm for one goal](https://help.rhythms.ai/workspace-settings-and-administration/customize-rhythms-settings/set-a-check-in-rhythm-for-one-goal.md).

## Recommended configurations

| Scenario                       | Owner                  | Delegate                                   | Contributors                                    |
| ------------------------------ | ---------------------- | ------------------------------------------ | ----------------------------------------------- |
| Individual OKR                 | The individual         | None                                       | None                                            |
| Team Key Result                | Team lead              | None                                       | Team members doing the work                     |
| Executive or company Objective | The executive          | Chief of staff, analyst or program manager | As needed                                       |
| Cross-functional Initiative    | The accountable lead   | Program manager, if needed                 | Members of each participating team              |
| OKR with limited visibility    | The accountable leader | As needed                                  | People who need access and must report progress |
| Owner on extended leave        | Unchanged              | The person covering updates                | Unchanged                                       |

## Frequently asked questions

**Should I make my manager an owner so they can see or update my OKR?**

No. With the default permission settings, your direct manager can already edit, manage and approve your OKRs. This applies to your direct manager only, not to managers further up the reporting line. If your OKR has limited visibility, share it with your manager so they can see it.

**Why did I stop receiving check-in reminders after adding a delegate?**

When an OKR has at least one delegate, reminders go to the delegates instead of the owners. This is expected behavior.

**Does owning a child OKR make me a contributor to its parent?**

No. Alignment and role assignments are independent. Contributors must be added explicitly.

**Can different delegates have different permissions?**

No. All delegates on an OKR have the same permissions. To give someone full control, make them an owner.

**How many people can be assigned to an OKR?**

An OKR can have multiple owners, any number of delegates, and up to 100 contributors.

**Can guest users be assigned a role?**

No. Guest users can't be added as owners, delegates or contributors.

## Related articles

* [Assign delegates to an OKR](https://help.rhythms.ai/goals-and-okrs/creating-goals/assign-delegates-to-an-okr.md)
* [Contributors for Objectives, Key Results, and Initiatives](https://help.rhythms.ai/goals-and-okrs/managing-and-tracking-goals/contributors.md)
* [OKR roles and permissions](https://help.rhythms.ai/workspace-settings-and-administration/team-users-and-access/okr-roles-and-permissions.md)
* [Control who can see an OKR](https://help.rhythms.ai/goals-and-okrs/creating-goals/control-who-can-see-an-okr.md)
* [Write and submit check-ins](https://help.rhythms.ai/goals-and-okrs/managing-and-tracking-goals/write-and-submit-check-ins.md)
* [Set a check-in rhythm for one goal](https://help.rhythms.ai/workspace-settings-and-administration/customize-rhythms-settings/set-a-check-in-rhythm-for-one-goal.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/owners-delegates-and-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.
