Skip to main content

Managing and Updating Saved Views

Edit, rename, reorder, and delete your saved views.

Wes Byrne avatar
Written by Wes Byrne
Updated today

As your Library evolves, you may need to update your saved views to reflect new workflows, renamed custom fields, or changing needs.

Admins and Content Managers can manage saved views.

Editing a saved view

To update the filters in a saved view:

  1. Select the saved view to update

  2. Modify the filters

  3. Click Save View (or the save/update option)

  4. Choose to update the existing view

Note: Saved views only save filters. Any search query or sort order you've applied is not saved as part of the view.

Renaming a saved view

  1. Find the view in the saved views list

  2. Click the menu icon (•••) next to the view name

  3. Select Rename

  4. Enter the new name

  5. Confirm the change

Note that you can not rename built-in views like "All Assets" or "Recently Added."

Reordering saved views

Custom views cannot be reordered manually at this time. They are always listed alphabetically after the built-in views.

Deleting a saved view

To remove a saved view you no longer need:

  1. Find the view in the saved views list

  2. Click the menu icon (•••) next to the view name

  3. Select Delete

  4. Confirm the deletion

Deleting a view doesn't affect the Assets themselves—it just removes the saved filter combination.

Note that deleting a view will also delete any dynamic galleries that rely on that view.

When to update views

Consider updating saved views when:

  • Custom fields change: If you rename or modify a custom field, views using it may need updates

  • Tag naming changes: Updated tag names may require view adjustments

  • Workflows evolve: New approval stages or categories might call for new views

  • Views become cluttered: Remove outdated views to keep the list manageable

Shared visibility

Saved views are available to all team members with Library access. When you create or update a view, others can use it too. Coordinate with your team to avoid duplicates and maintain consistent naming.

Learn more

Did this answer your question?