> 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/monitoring-and-reports/create-and-share-okr-views.md). # Create and share OKR views A view is a saved set of filters and display settings for your OKRs. Open **Views** in the left sidebar (under **More** in the Workspace section unless you have reordered your sidebar) to see every view you can access, create new ones and share them. The tabs at the top of the **OKRs** page are views too: they are the ones a Rhythms Admin has pinned for the whole workspace. ## Where views live The **OKRs** page shows pinned views as tabs. Everyone in the workspace sees the same tabs, in the order the views were created. Clicking a tab opens that view with its saved filters and display type. The **Views** page is the full library. It has three tabs, **All**, **Created by me** and **Shared with me**, a search box, and filters for **Creator**, **Label** and **Type**. Each row shows the view name, who created it and its labels, with a **⋯** actions menu at the end. Views also appear in the sidebar. Views you favourite appear in the **Favorites** section, and each team in **Your teams** has its own OKRs, Initiatives and Reports views. ## Views Rhythms creates for you Every workspace starts with a set of system views. Three are pinned as tabs on the OKRs page: **My OKRs** (OKRs you own), your company view, named after your workspace (for example *Contoso's OKRs*), and **All OKRs**, grouped by time period. If Initiatives are enabled, **My Initiatives**, your company's Initiatives and **All Initiatives** are pinned on the Initiatives page. The rest are in the Views library but not pinned: **My Key Results**, your company's Key Results, **All Key Results**, **My Check-ins** (OKRs you are responsible for checking in on), **On Track - Current Quarter**, **At Risk / Behind - Current Quarter**, and, when the approval workflow is enabled, **Pending Approval OKRs** (OKRs waiting for your approval). System views such as My OKRs show each person their own data. A custom view someone names "My OKRs" shows the creator's OKRs to everyone, so give shared personal views a descriptive name like "Jane's Q4 OKRs". A Rhythms Admin who has changed a system view can put it back with **⋯ → Reset to Defaults**. The option only appears when the view differs from its factory settings. ## Create a view in chat Open the chat panel and describe the view you want, for example "Create a view of all Q4 engineering objectives that are at risk, as a list grouped by owner". Rhythms creates the view with matching filters and display settings and saves it to your Views library. You can name the team, time period, owners, status, labels and object type, and say whether you want a tree, list, board, graph or strategy map. If a view is open when you ask, you can build on it: "add the Finance team to this view". ## Create a view manually 1. Open **Views** and click **New View**. 2. Add filters. Rhythms suggests a name and description from the filters you choose; edit either if you like. 3. Open **Display options** and pick Alignment tree, List, Board, Alignment graph or Strategy map, plus any grouping, sorting and columns. 4. Click **Save**. A new view is private until you share it. You can also start from any existing view: change its filters or display, then click **Save view**. On a system view, or a view you can only see, this saves your changes as a new view of your own. For every filter and grouping option, see [Filtering and grouping OKRs in views](/goals-and-okrs/monitoring-and-reports/filtering-and-grouping-okrs-in-views.md). ## Display types Every view has one display type, chosen under **Display options** in the view header. The filters stay the same whichever display you pick. ### Tree ![Tree display showing objectives expanded to their key results](https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2Fgit-blob-7a5208d47d67dee20668f71f878feb06b86c4276%2F1adaed52-d42f-4801-93ac-779571bfafa2-79b221a0-4218-49fc-a922-c88211656259.png?alt=media) Tree shows the hierarchy: expand an objective to see its key results, child objectives and initiatives. Use it for alignment reviews and planning. Press **Shift + R** to expand or collapse everything on the page. ### List ![List display showing OKRs in a flat table](https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2Fgit-blob-033b9059f5656ac6a0cd165e028c4ef625999815%2F515475ac-421b-43b1-8190-3eef11e7e62b-image.png?alt=media) List is a flat table regardless of hierarchy. Group, sort and choose columns, and drag the column pills to reorder them (Title always stays first). Use it for weekly check-in reviews and audits. ### Board ![Board display showing each objective as a card](https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2Fgit-blob-a10b07ddeadeeac00e769a74c0e9dafaa3071fd9%2Fffcbf14e-a709-4d19-bc71-e479fb3bbebd-c32815b9-ce0e-48ac-89be-769cee263298.png?alt=media) Board shows each objective as a card with progress, status and key results. Choose a **Template** of None, **MBR** or **WBR**; with no template you can turn on **Compare to past** by week or month and pick which properties each card shows. Use it for business reviews and all-hands. ### Graph Graph draws OKRs as connected cards from left to right. Expand a card to load its children, or expand upwards from a top-level card to see the objectives it aligns to, even when your filters would exclude them. Turn on **Apply filters to children** to show only matching goals in both directions. Use it to trace how a key result connects to company priorities. ## Pin a view to the OKRs page Pinning is how a Rhythms Admin decides which views appear as tabs for everyone. Open the view's **⋯** menu and choose **Pin to OKRs page**. Rhythms confirms that pinning makes the view visible to everyone in your workspace. Choose **Unpin** from the same menu to remove the tab. Only Rhythms Admins see these options, and Report views cannot be pinned. ## Favourite a view Favourites are personal. Open a view's **⋯** menu and choose **Add to favorites**; the view appears in the **Favorites** section of your sidebar, where you can drag to reorder. Choose **Remove from favorites** to take it out. Favourites do not change what anyone else sees, and there is no limit. ## Share a view New views are private to their creator. To share one, open **⋯ → Share**, add people or teams, and choose a permission level: * **Can view**: open the view and use its filters, but not change it. * **Can edit**: change filters and display settings. * **Can manage**: edit, share and delete. Sharing with a team covers everyone who is a member now or joins later. You can also let everyone in the workspace access the view with its link. The view's creator, anyone with Can manage, and Rhythms Admins can change sharing. A pinned view is automatically shared with everyone and cannot be made private while it is pinned. Sharing a view does not grant access to OKRs. Each person still sees only the OKRs they are allowed to see; see [OKR visibility](/goals-and-okrs/creating-goals/control-who-can-see-an-okr.md). ## Other actions in the ⋯ menu * **Edit** the name and description. * **Manage Labels** to tag the view; Rhythms Admins can create new labels here. * **Send Check-in Reminders** to the owners of OKRs in the view, when your workspace has manual reminders enabled. * **Create a document** from the view, using chat. * **Export to Excel**, **Export to Word** or **Export to PowerPoint**; see [Export OKRs to CSV, Word or PowerPoint](/goals-and-okrs/monitoring-and-reports/export-okrs-to-csv-word-or-powerpoint.md). * **Delete**. Deleting a view is permanent and cannot be undone. ## FAQ **Can I create a view that only I see?** Yes. Every new view is private until you share it or a Rhythms Admin pins it. **Who can pin views?** Only Rhythms Admins. Members can favourite a view for themselves or ask an admin to pin it. **Can I change a system view like My OKRs?** Open it, change the filters or display, and click Save view; Rhythms saves your version as a new view. Rhythms Admins can edit system views directly and reset them with Reset to Defaults. **Where are views shared with me?** On the Views page, open the **Shared with me** tab. **What happens to my views if I leave?** Views you created stay, and people you shared them with keep their access. Pinned views stay pinned until an admin unpins them. ## Related articles * [See how your OKRs align: Alignment graph and Strategy map](/goals-and-okrs/monitoring-and-reports/see-how-your-okrs-align-alignment-graph-and-strategy-map.md) * [Filtering and grouping OKRs in views](/goals-and-okrs/monitoring-and-reports/filtering-and-grouping-okrs-in-views.md) * [Export OKRs to CSV, Word or PowerPoint](/goals-and-okrs/monitoring-and-reports/export-okrs-to-csv-word-or-powerpoint.md) * [Monitor OKR program health with Reports](/goals-and-okrs/monitoring-and-reports/monitor-okr-program-health-with-reports.md) * [OKR visibility: who can see an OKR](/goals-and-okrs/creating-goals/control-who-can-see-an-okr.md) * [Find your way around Rhythms](/goals-and-okrs/okr-foundations-and-structure/find-your-way-around-rhythms.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/monitoring-and-reports/create-and-share-okr-views.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.