How to create and manage views
Use saved views to store a named configuration of filters, layout, sort order, and columns in a library or journey. This guide covers how to create, edit, share, and manage them.
Before you start
To create, save, or publish views, you need the Manage views permission. Without it, you can still view and interact with any published views — you just won't be able to create new ones or overwrite existing shared views. If you don't see the option to save a view, check with your workspace admin.
Create a saved view
- Go to a library (e.g., Opportunities) or open a journey.
- Apply your filters, choose a layout, and configure columns, sort order, or matrix axes.
- Click the + button in the view tab bar.
- Choose a layout type or start from a template.
- Optionally apply your current filters to the new view.
- Name the view and save it.
The view appears as a new tab at the top of the library or journey.
Save changes to an existing view
When you change filters or settings on a published view, your edits stay as a personal draft — other users still see the original. To apply your changes:
- Save view — overwrites the published view for everyone.
- Save as new view — creates a separate view, keeping the original untouched.
Manage saved views
- Rename — open the view's action menu and select Rename.
- Duplicate — clone an existing view as a starting point for a new one.
- Reorder — drag tabs or use the action menu to move views left or right.
- Delete — remove a view you no longer need from the action menu.
Share a saved view
- Open the view you want to share.
- Click Share link in the view's action menu.
- Copy the URL and send it to your team or stakeholders.
The link includes a view ID, so anyone who opens it lands in the same configuration with live data.
Tips
- Name views by audience and purpose — for example, "Exec – Q2" or "Opps – Prioritization".
- Use Favorite to pin views you return to often.
- If you have many views, overflow tabs collapse into a +N more menu — you can reorder to keep your most-used views visible.
- For a curated stakeholder package that bundles journeys, views, and documents together, use Collections instead of saved views.