FIGR / UI TEMPLATE

Saved Searches

Manage personal and shared saved searches, pinned views, owners, alerts, and recent usage. The screen connects Saved and Shared so product teams can find the “New saved search” action while checking saved searches and shared.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Renewals at risk and High-priority incidents, rather than an empty visual shell.

Saved Searches

BUILD ON THIS

Make it yours in Figr.

Explore this screen, then bring in your own product and design system to shape the next version.

Use this template ↗

At a glance

Screen

Table

Primary action

New saved search

Pattern

Table

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps with

Product teams need a clear “New saved search” action without losing sight of saved searches, shared and the affected records. Keep the decision and its outcome clear before moving to the next task.

What to look for

  • Primary action: New saved search is clearly available where the task happens.
  • Main view: Saved keeps the starting point obvious.
  • Connected view: Shared supplies nearby context.
  • Metric: Saved searches is visible with a meaningful value.
  • Another signal: Shared helps people judge what to do next.
  • Representative record: Renewals at risk makes the example specific.
  • Second record: High-priority incidents shows the pattern works beyond one item.

States to consider

  • Empty filtered view; show what people can do instead of leaving a blank panel.
  • Loading saved without changing the layout unexpectedly.
  • Bulk action partly failed; explain the problem and preserve work.
  • Permission denied for shared; clarify who can continue.
  • Success after choosing New saved search; confirm the result and the next step.
  • Network or data refresh failure; offer a retry without losing context.

Where it fits

Saved → Shared → New saved search → Review outcome

Patterns in this screen

Table, Saved, Shared, Pinned, accessible states, contextual actions

UX choices to review

Show the columns people use to act, not every field at once. Keep sort and filter state when returning from a record.

In this design, people should be able to compare Renewals at risk with High-priority incidents. Make saved searches clear, then use shared to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “New saved search” action. The happy path alone is not enough.

Related UI examples: Advanced Search Filters, Command Palette, Global Search.

Try a similar screen in Figr

Design a saved searches screen for our existing software product. Use our real design-system tokens, components and product language. Show Saved and Shared, include believable records such as Renewals at risk, and make new saved search easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr

KEEP EXPLORING

More ways to approach your next screen.

Browse other product UI examples, compare patterns, and pick the direction that suits your product.

Explore all 500 templates ↗