OKR restrictions (per-OKR)

Owned by Derya Özdemir
Last updated: Sept 11, 2024 by Derya Özdemir
3 min read

This page is about OKR for Jira Cloud. Using Data Center? Click here.

OKR restrictions provide an additional layer of control for individual Objectives and Key Results (OKRs). This feature allows users to manage who can view and edit specific OKRs. There are two types of restrictions available:

  1. Visibility Restriction: Limits the visibility of an OKR to a designated group of users and teams.

  2. Editing Restriction: Restricts editing capabilities, including the creation of sub-items and linking Jira issues, to a chosen group of users and teams.

It's important to note that restrictions applied to specific OKRs take precedence over general permissions, ensuring a more granular level of access control.

Setting OKR Restrictions

Who can apply restrictions?

OKR restrictions can be applied by individuals with the appropriate permissions. The permission configuration can be set on the Settings > Permissions page, providing flexibility based on organizational needs:

  • Full access: Anyone can apply OKR restrictions.

  • Global settings control: Designated users can toggle the feature on/off, others can apply restrictions.

  • Editing control: Anyone can toggle the feature, selected users can apply restrictions.

  • Global settings and editing control: Selected users can toggle the feature or apply restrictions.

  • Advanced setup: Users in roles with this permission can apply OKR restrictions.

When should you restrict OKRs?

Use restrictions sparingly – OKRs are meant to be transparent. Apply them only for OKRs containing sensitive data unsuitable for company-wide sharing.

Enabling the feature

  1. Navigate to Settings > General.

    image-20240911-120100.png

  2. Turn on the toggle for Allow restricting OKRs.

  3. You can choose to completely hide or partially show restricted OKRs. In both instances, their progress will contribute to the parent OKR's advancement. Therefore, the partial visibility enables a double-check to ensure that the progress of all top-level elements is coherent.

When enabled, a lock icon appears on each OKR detail page for configuration. To disable it, you can turn off the toggle, and this will remove all restrictions.

The setup you had will not be stored on our side, meaning that if you decide to turn the feature on again in the future, no restrictions will be reapplied the way they were when the feature was turned on for the last time.

Using the feature

On every OKR detail page, you'll find a padlock icon. Clicking it will reveal a dialog showing the configuration of permissions.

image-20240326-190839.png
Click the padlock icon to reveal the permission options.
Screenshot 2024-03-26 at 22.03.07.png

Your options are:

  • Anyone can view and edit – Every OKR is set to this option by default (while respecting other applied permissions).

  • Anyone can view, specific people or teams can edit – This option will allow restricting editing of a chosen OKR to a group of users and teams.

  • Only specific people or teams can view or edit – This option allows you to separately define the people who can view and who can edit the OKR.

Restrictions are applied immediately after saving.