Skip to main content

OKR Visibility — Who can see an OKR

How visibility settings work for Objectives and Key Results (OKRs) in Rhythms

Updated this week


What “visibility” means

Visibility controls who can see an Objective, Key Result, or Initiative. It does not change edit permissions—those are controlled separately by role/ownership.

Visibility is not inherited (i.e. changing the visibility on an Objective does not automatically change the visibility on its Child Objectives, Key Results, or Initiatives).

Admins can always view Limited Visibility OKRs


Visibility options

  • Everyone in your workspace: The OKR is discoverable in search, lists, dashboards, and links for all members of your workspace.

  • Limited (specific teams or users): Only the people and teams you specify can view the OKR. Assignees are included automatically. Use this for sensitive, in‑progress, or people‑related goals.


Set or change who can view an Objective

  1. Open the OKR detail page.

  2. Click MoreLimit Visibility.

  3. Choose Everyone or Limited.

  4. If Limited:

    • Click Add → select Teams and Users to include.

    • Confirm that Assignees are listed (they’re granted view access automatically).

5. Click Save.

Tip: You can return here anytime to update who’s included. Changes take effect immediately.


What changes when you pick Limited

  • The OKR is hidden from workspace‑wide lists and search for non‑included users.

  • Links to the OKR won’t open for people who aren’t included.

‼️ Note: Child objects do not inherit the visibility setting of their parent by default.


Examples

  • Company OKRs → set to Everyone.

  • Pre‑launch or sensitive initiatives (e.g., M&A, compensation, security) → set to Limited and include the core team only.

  • Function/team OKRsLimited to that team plus relevant partners.


FAQ

Does visibility give edit access?

No. Visibility governs who can view. Edit rights depend on ownership/roles.

Does changing the visibility of an parent OKR automatically change the visibility of its nested child objectives, key results, and initiatives?
No. Visibility is not inherited (i.e. changing the visibility on an objective does not automatically change the visibility on its child objectives, key results, or initiatives).

The user needs to change the visibility of each item individually.

Can guests see objectives?

Only if they are in your workspace and are explicitly included (or visibility is Everyone).

What about Key Results and check‑ins?

When the visibility is changed for an existing OKR, any existing children do not inherit the new visibility settings. However, all new children created after the change will have the same visibility as the parent.

Who can change visibility?

Owners of the OKR and workspace admins.


Troubleshooting

  • I can’t find an OKR → Ask the owner to add you under Limited, or request an admin to verify visibility.

  • The Everyone option is disabled → Your org may enforce restricted visibility for certain objective types; contact an admin.

  • People added can’t open the link → Have them refresh; confirm they’re part of the selected Team or listed individually under Users.


Good practices

  • Default to Everyone for company‑wide alignment. Use Limited sparingly.

  • Review visibility at the start of each quarter and after team changes.

  • When restricting, add the assignee(s) and the sponsor/DRI explicitly to avoid access gaps.

Did this answer your question?