OKR Approval Workflow (Beta)

Last updated: August 20, 2026

Use the OKR approval workflow to require a designated approver before draft OKRs become visible across your organization.

This feature is in beta. It is not enabled by default, and there is no self-serve toggle in workspace settings. To turn it on for your workspace, contact the Rhythms team.

What the approval workflow does

When the workflow is enabled, new OKRs stay in Draft until someone with approve permission publishes them.

People who can edit an OKR but cannot approve it use Request Approval. That moves the OKR to Pending approval and notifies the configured approvers. An approver then reviews the OKR and clicks Publish.

Publishing makes the OKR live (status Not started) and sets its visibility to public so the rest of the organization can see it.

Publishing is a go-live step, not a lock. After an OKR is published, people with edit permission can still change the title, targets, and other details, and they can still check in. To limit who can change live OKRs, tighten Edit and Manage in Admin > OKRs > Permissions. See Rhythms OKR Roles and Permissions.

Enable the workflow

Follow these steps to get the beta workflow turned on and configured:

  1. Contact the Rhythms team and ask them to enable the OKR approval workflow for your workspace.

  2. After it is enabled, a default Pending approval view is created so approvers can find OKRs waiting on them.

  3. An Approve permission row appears in Admin > OKRs > Permissions for organization, team, and individual OKRs.

Until the Rhythms team enables the workflow, anyone with edit or manage permission can publish drafts themselves. There is no request/approve step.

Configure who can approve

Rhythms Platform Administrators set approve permission separately for organization, team, and individual OKRs.

Go to Admin > OKRs > Permissions, then choose the Organization, Team, or Individual tab.

The Approve row controls who can publish draft and pending-approval OKRs. Options depend on the OKR level:

Organization-level OKRs

  • Admins only

  • OKR owners and their managers (default)

  • Anyone in the organization

Team-level OKRs

  • Admins only

  • OKR team owners

  • OKR owners and their managers (default)

  • OKR team members

  • Anyone in the organization

Individual OKRs

  • OKR owners and their managers (default)

  • Anyone in the organization

OKR owners, creators, and Rhythms Platform Administrators retain access to OKRs they own or created, consistent with other OKR permissions.

Request approval for a draft OKR

Use this when you can edit the OKR but do not have approve permission.

  1. Open the draft OKR.

  2. Click Request Approval.

  3. Confirm the request.

The OKR moves to Pending approval, and configured approvers are notified. You can request approval again after you make changes.

You can also request approval for several OKRs at once from views and bulk actions where that option is available.

Publish (approve) an OKR

Use this when you have approve permission.

  1. Open the draft or pending-approval OKR, or find it in the Pending approval view.

  2. Click Publish.

  3. Optionally include immediate children or the entire hierarchy, including any OKRs still pending approval.

  4. Confirm.

Publishing a parent does not automatically publish every child unless you choose those options. Select the children or hierarchy you want to publish together.

After publish, the OKR is live and public. Check-in becomes the primary action instead of Publish or Request Approval.

Frequently Asked Questions

How do I turn this on?

Contact the Rhythms team. The approval workflow is a beta feature and is not available as a self-serve setting.

Does publishing lock the OKR so nobody can edit it?

No. Publishing makes the OKR live and visible. People with edit permission can still update content and check in. Use Edit and Manage permissions if you want fewer people changing OKRs after they go live.

What is the difference between Request Approval and Publish?

Request Approval asks someone else to review and publish. It sets the status to Pending approval and notifies approvers. It does not make the OKR live.

Publish is the approval action. Only users with approve permission can publish. That is what makes the OKR live.

Who gets notified when I request approval?

The people allowed to approve that OKR, based on Admin > OKRs > Permissions for that OKR level. The person who requested approval is not notified of their own request.

What if I can already publish?

If you have approve permission, use Publish directly. You do not need to request approval first.

What happens to drafts if the workflow is not enabled?

OKRs still start as drafts. People with edit or manage permission can publish them without an approval step.

Related Articles