Saved views should preserve a defined set of filters, sorting and display choices without freezing record access or silently sharing private data. Distinguish saving a query from exporting a snapshot. Users opening the same view may legitimately see different records because their current permissions differ.
Let’s plan your saved views.
Bring your workflow, constraints and open questions. We’ll help you define the requirements and work through a practical next step.
Define what the view contains
List stored settings: query, filters, columns, sort order and perhaps grouping. Decide whether relative dates such as Last seven days remain relative when reopened. An absolute date range has a different meaning.
For a hypothetical service queue, a manager's My team's open cases view may depend on current team membership. Specify that relationship rather than storing an unexplained list of people forever.
Use a view lifecycle matrix
| Event | Rule to specify | Failure to test |
|---|---|---|
| Save | Name, ownership and stored settings | Hidden default filter omitted |
| Reopen | Apply current data and access | Old permission context reused |
| Share | Who may discover and use the definition? | Sensitive title or filter value exposed |
| Edit | Change personal or shared view? | One user surprises every colleague |
| Owner leaves | Transfer or retirement process | Shared operational view becomes unmaintained |
| Field removed | Explain incompatible settings | Empty result appears as valid zero |
The saved definition can itself contain sensitive information, such as a restricted customer name in a filter. Apply appropriate visibility to the view, not only its resulting rows.
Keep defaults understandable
Show which view is active and how it differs from a standard view. Give users a clear route to reset filters. A persistent hidden setting can make expected records seem missing for weeks.
Avoid overwriting a shared view automatically when a user makes a temporary adjustment. Distinguish unsaved changes, a personal copy and a deliberate shared update.
Test changed authority and data
Open a shared view with two synthetic roles, revoke access and reopen it. Change a relevant field definition and verify the product explains the effect.
Confirm direct links preserve the intended view without bypassing authentication or record-level checks. A shared URL should not become an accidental access token.
Saved-view questions
Should a saved view always show the same rows?
Not if it represents a live query. Use an explicitly defined snapshot or export for a fixed population.
Can every user edit team views?
Define ownership and editing authority according to the operating model, with a useful history or recovery route.
Pair views with search and filter recovery, and discuss sharing rules with Drema's UI/UX team.