Use saved view when users persist a named presentation of a dataset, saved search for reusable query criteria, saved filter for reusable filter values, and table for the current row-and-column display itself.
Use saved view when users persist a named presentation of a dataset, saved search for reusable query criteria, saved filter for reusable filter values, and table for the current row-and-column display itself.
Practice the judgment: Imagine this situation: A user tweaks a shared operational view and overwrites the team default instead of saving a private copy. Write the person's goal, choose one of these patterns, and show the state that helps the person continue. Use the decision rules and source trail below to explain your choice.
Review the underlying principle →| Dimension | Saved view | Saved search | Saved filter | Table |
|---|---|---|---|---|
| UI or UX | UI + UX - Persisted named presentation state for a data workspace | UI + UX - Persisted named search criteria for rerunning a dynamic result set | UI + UX - Persisted named filter criteria applied to a list, table, board, or dashboard | UI + UX - Semantic row-and-column data comparison surface |
| UI guidance | Render saved views as named, selectable workspace presentations with visible owner or visibility, active state, saved layout mode, columns or fields, grouping, sort, filters, and last-updated metadata. | Render Save search near the active query and result summary, and show exactly which query text, filters, scope, and sort will be stored. | Place Save filter close to the active filter controls and show a criteria preview that names every stored field, operator, and value before users commit it. | Render a table with a specific caption or heading, visible column headers, optional row headers, aligned values, consistent row actions, and enough spacing for scanability. |
| UX guidance | Use saved view when users need to return to a complete operational presentation of a changing dataset rather than rebuilding columns, layout, grouping, filters, and sort every session. | Preserve the distinction between running a saved search temporarily and updating the saved criteria, especially when a saved search is shared or subscribed to. | Use saved filter when users repeatedly apply the same filter values to a changing list and need to reuse those criteria across sessions or teams. | Use tables when aligned columns help users compare records, find exceptions, audit values, or triage work faster than opening each item. |
| Good UI | A support queue has saved views named My urgent tickets, Team backlog, and SLA breach risk, each showing columns, sort, filters, owner, and private or team visibility before users apply it. | A search results page shows Save search beside the result count, opens a naming dialog, and previews query, filters, scope, and sort before saving. | A case queue exposes saved filters named High priority benefits and My review queue, each with status, team, priority, and date chips before users apply them. | A payment review table has the caption June vendor payments, headers Vendor, Status, Due date, Amount, and Action, right-aligned amounts, and row actions labelled by vendor. |
| Bad UI | A saved view list mixes saved filters, saved searches, static exports, bookmarks, and recent pages under one generic Saved label. | Saved searches, recently searched terms, browser bookmarks, and saved filters are mixed in one list called Saved. | A list called Saved mixes saved filters, saved searches, recent views, pinned tabs, and browser bookmarks. | Mobile stacking removes headers and turns rows into unlabeled paragraphs. |
| Good UX | A manager opens SLA breach risk, sees the board layout, grouped Status lanes, five saved columns, and current result count, then changes density and saves a private copy instead of overwriting the team view. | A user saves a search for Open renewal risks, returns next week, reruns it, and sees newly matching cases included. | A benefits worker applies High priority benefits to the current appeal search; the query stays appeal while status, team, and priority filters change. | A user sorts by Amount descending, filters to Pending, moves to page 2, and the table keeps its caption, active sort, active filter, row count, and selected payment context. |
| Bad UX | A user changes one column while reviewing a team queue and accidentally updates the shared default for everyone. | Saving search stores only the current three results, so future matching records are missing. | A private preset and a team preset have the same label, causing users to overwrite the shared operational queue. | Mobile stacking removes headers and turns rows into unlabeled paragraphs. |
| Best fit | Users repeatedly return to a specific presentation of a changing data set. | Users repeat the same search criteria across sessions or operational cycles. | Users repeatedly need the same filter criteria on a list, table, board, queue, base view, or dashboard. | Records share comparable attributes that users need to scan in aligned columns. |
| Avoid when | Only one current-session filter or sort choice needs to be changed. | The list is small enough that recent searches, bookmarks, or manual scanning solve the problem. | Users only need to adjust filters for the current session. | The task depends on rich previews, imagery, or uneven metadata. |
| Required state | Saved view list with active, private, team, shared, pinned, default, owner, last-updated, and result-count states. | Unsaved current search with Save search available only when criteria are meaningful. | Saved filter list with active, private, team, global, owner, and last-updated states. | Default table state with caption, visible headers, row values, and result count or context. |
| Accessibility burden | Use labelled controls for view name, visibility, layout, columns, grouping, filters, sort, density, and sharing settings. | Use labelled form fields for saved-search name, description, visibility, and subscription settings. | Use labelled controls for saved-filter name, visibility, owner, criteria fields, operators, and values. | Use native table semantics for tabular data rather than div-only rows. |
| Common misuse | Saving current rows instead of presentation settings and dynamic criteria. | Saving static result IDs instead of reusable criteria. | Treating the visible table rows as the saved object instead of storing field, operator, and value conditions. | Using table markup to create page columns or layout spacing. |