Lorixen.
EN

Saved views and filters in an internal tool: a worked example

Short answer: If staff rebuild the same filters in your internal tool every morning, saved views are the fix: a named combination of filters, sorting and visible columns that anyone can open with one click. Build them in layers: good filters first, then put the filter state in the URL so it can be bookmarked and shared, then add named personal and team views with sensible defaults. The worked example below shows how a small operations team might get there.

Internal tools grow one table at a time: orders, jobs, customers, tickets. Each table gets a few filters, and soon everyone has their own ritual of clicks to find "my open jobs this week" or "unpaid invoices over 30 days". It's slow, error-prone and invisible to whoever built the tool. This article follows a hypothetical business through the changes, step by step.

The example business (hypothetical)

A regional moving company in Ohio (illustrative, not a real client) runs an internal web app for bookings. Its Bookings table has about 30 columns and a few thousand rows. Four roles use it:

  • Dispatchers want tomorrow's moves by crew.
  • Sales want quotes not yet confirmed, newest first.
  • Accounts want completed moves not yet invoiced.
  • The owner wants this week's revenue by status.

Today, each person opens the table, clicks four or five filters, sorts, hides columns they don't need, and does it all again after every page refresh.

Step 1: Fix the filters before saving them

Saved views only help if the underlying filters are good. The team reviews the table and makes three changes:

  1. Filter by the fields people actually think in: move date (with "today", "tomorrow", "this week" shortcuts), status, crew, salesperson, invoice status.
  2. Show active filters as removable chips above the table, so it's always clear what's applied.
  3. Make the result count visible: "47 bookings match". It reassures people the filter worked, and makes an unexpected zero obvious.

Step 2: Put the view state in the URL

Next, every filter, sort order and page number is reflected in the page address, for example:

/bookings?status=confirmed&date=tomorrow&crew=2&sort=start_time

This one change delivers a lot:

  • refreshing the page keeps the filters;
  • people can bookmark a filtered view;
  • a dispatcher can paste a link into chat and the colleague sees exactly the same list;
  • the browser back button works as expected.

On the technical side, browsers have long offered what's needed. MDN describes URLSearchParams as an interface with utility methods for working with a URL's query string, widely available across browsers, and the History API's replaceState() as a way to update the URL of the current history entry in response to user actions without reloading. Developers often use replaceState for each filter tweak so the back button isn't flooded with tiny steps, and push a new history entry only for larger changes.

The developer also sets a rule: unknown or outdated parameters in a URL are ignored gracefully, so old bookmarks don't break the page.

Step 3: Named personal views

With state in the URL, saving a view is mostly storing that state with a name. The team adds:

  • a "Save view" button that asks for a name, such as "Tomorrow – Crew 2";
  • a views menu next to the table title listing the user's saved views;
  • options to rename, update or delete a view;
  • the ability to set one view as my default, so the table opens the way each person needs.

Views store filters, sort order, visible columns and column order. They don't store the data itself, so they always show current records.

Step 4: Shared team views

Some views are useful to everyone. The team adds shared views, visible to all users or to a role:

  • "Unconfirmed quotes (newest first)" for sales;
  • "Completed, not invoiced" for accounts;
  • "This week by status" for the owner.

Only admins, or the view's creator, can edit a shared view, which prevents one person's tweak from changing everyone's list. Personal views stay private.

Step 5: Sensible defaults by role

New users shouldn't face a raw 30-column table. Each role gets a default view:

  • dispatchers open on "Tomorrow by crew";
  • sales open on "Unconfirmed quotes";
  • accounts open on "Completed, not invoiced".

Users can still change their own default.

Step 6: Details that make it pleasant

  • Indicate unsaved changes: if someone adjusts a saved view, show "Modified" with options to save, save as new, or reset.
  • Counts on views: showing the number of matching rows next to each view name ("Completed, not invoiced (12)") turns views into a light to-do list. Compute counts efficiently or refresh them periodically so the menu stays fast.
  • Export respects the view: CSV exports include only the filtered rows and visible columns.
  • Permissions still apply: a shared view never shows rows a user isn't allowed to see.

What changed (in the example)

In this illustrative scenario, the daily filter ritual disappears: each role opens the tool on its own default, links in chat land on the right list, and the accounts team's "not invoiced" count becomes a daily check. We're not claiming time savings; the point is fewer repeated clicks and fewer missed bookings from wrong filters.

Common pitfalls

  • Saving views before fixing confusing filters.
  • Storing views as fixed lists of row IDs instead of filter criteria.
  • Letting anyone edit shared views.
  • Long, unreadable URLs: keep parameter names short and stable.
  • Dates saved as fixed values ("2026-11-05") when people meant relative ones ("tomorrow").

FAQ

Do we need saved views if we only have a few users?

If those users repeat the same filters daily, yes. Even URL-based filters alone save time.

Should views be stored in the browser or the database?

Store them in the database if you want them available on every device and shareable with colleagues.

Can saved views include charts or totals?

They can, but start with filters, sorting and columns. Add summaries once the basics are used.

What about mobile?

Keep the views menu reachable and default to a compact set of columns on small screens.

If your team rebuilds the same filters every morning, tell us which tables they live in and we'll suggest the views worth building first.

Sources

WhatsAppLet’s talk