> 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/creating-goals/control-who-can-see-an-okr.md). # Control who can see an OKR Every Objective, Key Result and Initiative is either visible to **Everyone at your workspace** (the default) or **Limited** to the users and teams you list. Visibility controls who can see a goal, not who can edit it. Change it from the goal's **More → Limit visibility** menu, or by clicking the **Limited** pill once it is restricted. Rhythms Admins can always see every goal. ## Who can see a Limited goal * Its **owners** and **delegates**, automatically. Adding an owner or delegate to a Limited goal grants them access, and Rhythms asks you to confirm. * The **users** you list, and every member of the **teams** you list (including sub-team members). * **Rhythms Admins**. For everyone else the goal is hidden from lists, views, search, documents, reports and chat answers, and its link opens nothing. Guests follow the same rule: they see public goals and any Limited goal they are listed on. ## Limit who can see a goal 1. Open the goal. Under the title pills, click **More → Limit visibility**. (This item appears only while the goal is public.) 2. In the **Who can view this Objective** dialog, choose **Limited**. The owners appear under **Users and Teams** marked "Assigned to this Objective"; delegates are marked "Delegate for this Objective". 3. Click **Add** and pick users and teams. Remove an entry with the × next to it (owners and delegates cannot be removed here). 4. Click **Save**. The change applies immediately. ![Who can view this Objective dialog with Everyone at the workspace, Limited, and a Users and Teams list](https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2Fgit-blob-4d04c0f6f4144ad7dfc0fc830598b4dd7b90098d%2F1b827bd9-d4aa-40ef-8593-f3486b35c62f-AD_4nXchZlgSld6ZqpLvPvBdnr_AqBLHV-XF176r0B1mR2ywzfdL8-nZgQQCyX4XwaIWwFDxGxKBV07B79o.png?alt=media) To edit the list later, click the **Limited** pill on the goal, which opens the same dialog. To open the goal up again, choose **Everyone at ‹workspace›** and save. ## Who can change visibility Anyone who can edit the goal: by default its owners, their managers, its delegates and Rhythms Admins. Visibility is an ordinary edit field, so it does not need the higher manage permission that owners and delegates require. If you cannot see **Limit visibility**, either the goal is already Limited (use the **Limited** pill) or you do not have edit access to it. ## Children and parents Visibility is set per goal and is not inherited when you change it: restricting an Objective does not restrict its existing Key Results, Initiatives or child Objectives, and each must be changed individually. Two things do carry visibility across: * When you add a child from the parent's **⋯** menu or the create form, the new child starts with the parent's visibility and list, and each inherited entry is marked "Included because parent OKR is shared with this team/user". You can edit the list before saving. * Children created through chat, the bulk importer or the API do not copy the parent's list; they use the workspace default (public) unless a visibility is given. Visibility also affects rollup: a Limited child under a public parent, or a Limited child that some of a Limited parent's viewers cannot see, stops contributing to the parent's progress (its weight is set to 0) until its visibility is widened; see [Understanding OKR Automatic Rollup](/goals-and-okrs/managing-and-tracking-goals/how-parent-okr-progress-and-status-roll-up.md). ## Drafts and team defaults Draft goals are Limited to their creator, owners and owning teams until published, whatever visibility they will have afterwards. A Rhythms Admin can also set team-level OKRs to be viewable by team members only in the OKR permission settings; new team goals then start Limited to their team and creator, and you can widen them per goal. ## Frequently asked questions **Does visibility give edit access?** No. Who can edit is decided by ownership, delegation and the OKR permission settings; see [Rhythms OKR Roles and Permissions](/workspace-settings-and-administration/team-users-and-access/okr-roles-and-permissions.md). **Can guests see Limited goals?** Only if they are listed as a user or belong to a listed team. See [Guest Users in Rhythms](/workspace-settings-and-administration/team-users-and-access/guest-users-read-only-access.md). **Do Slack and chat respect visibility?** Yes. Search, chat answers and Slack messages only include goals the asking user can see. **I can't find a goal I was told about.** Ask the owner to add you (or your team) under **Users and Teams**, or ask a Rhythms Admin to check. If you were just added, refresh the page. **What should be Limited?** Company and team OKRs work best public, since alignment depends on people seeing them. Reserve Limited for genuinely sensitive goals (M\&A, compensation, security, pre-launch), and review the lists at the start of each period and after team changes. ## Related articles * [Rhythms OKR Roles and Permissions](/workspace-settings-and-administration/team-users-and-access/okr-roles-and-permissions.md) * [OKR roles and permissions](/workspace-settings-and-administration/team-users-and-access/okr-roles-and-permissions.md) * [Assign delegates to an OKR](/goals-and-okrs/creating-goals/assign-delegates-to-an-okr.md) * [Guest Users in Rhythms](/workspace-settings-and-administration/team-users-and-access/guest-users-read-only-access.md) * [Edit and update OKRs](/goals-and-okrs/managing-and-tracking-goals/edit-and-update-okrs.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 dynamically 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/creating-goals/control-who-can-see-an-okr.md?ask=&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 `build a script that syncs our docs to a CMS` 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.