Craft.io gives you a lot of flexibility when it comes to views - you can filter, group, sort, and configure them in almost any combination. That flexibility is powerful, but it can also mean starting from a blank slate.
Guru Views solve that. Instead of building a prioritization or planning view from scratch, you start from a pre-configured view that already reflects how the best product teams work. Think of them as a curated library of world-class product management methodologies - ready to add to your workflow in one click.
In this article:
What are Guru views?
A collection of preset views, each pre-configured for a specific use case - the right view type, the right fields, the right filters, already set up for you. They cover:
Prioritization - RICE, MoSCoW, SAFe® WSJF, Kano, and more
Roadmapping - release timelines, Now / Next / Later, objectives-linked layouts
Dev and bug tracking - live Jira and ADO dev statuses, open bugs
Task management - items assigned to you, your team, or a colleague
Segmentation - by region, platform, or customer type
Note, the ability to create and manage Guru views is available to Workspace and Portfolio admins only.
How to add a Guru view
There are two ways to add a Guru View, depending on where you want it to live.
To add a view to your personal views:
Click the Guru views button at the bottom left of the screen in your Workspace
Browse the library and select the view you want
Click Add View
A view you add from Guru Views starts as a personal view - visible only to you. When a view is useful for the whole team, admins can promote it to a Workspace view so everyone works from the same configuration (Actions > Save as new workspace view).
To add a view directly to a shared section:
Hover over any shared view category (for example, Planning) and click the + icon that appears.
Browse the list of relevant Guru Views for that category
Click Preview to see the view before you add it to the Workspace
Click Add View (this adds the view directly to that shared section - no extra steps needed)
Use this method when you want the view to be available to the whole team straight away, without going through personal views first.
View types and prerequisites
A few views have requirements worth knowing about upfront:
Focus area - Some views ask you to select a scope before they are added (for example, Upcoming Sprints asks you to choose which sprints to display). You can recreate these views any time the scope changes.
Integrations - Some views require an active integration to show live data. Sprint Dev Status (Jira), for example, needs a Jira connection before it will populate. The view can still be added - it just won't display data until the integration is in place.
Custom fields - Some views, like RICE Prioritization, require custom fields to calculate scores. Workspace admins are prompted to create these automatically when adding the view. If you are not an admin, ask your admin to create the fields before using it.
What comes next?
Now that you know how Guru views work, the next step is finding the views that match your team's most frequent planning conversations.
Browse the Prioritization category if your team needs a shared framework for backlog decisions
Start with Now / Next / Later or Release Timeline if stakeholder communication is the priority
Add Sprint Dev Status if you want a live view of Jira or Azure DevOps progress
Not sure which views to start with? Read The top 5 Guru Views - and how to get the most out of them for a walkthrough of the highest-value views and the best practices that make them work.
Need more guidance? 🙋 Our LIVE support team (at the bottom right corner of your screen) replies to ANY question!