Global Search

Search across people, projects, docs, records, and product context from one universal search experience. The screen connects All results and People so product teams can find the “Save search” action while checking results and sources.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Enterprise permissions rollout and Billing migration plan, rather than an empty visual shell.

Use this template in Figr

Template facts

Screen

Primary action

Save search

Pattern

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

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

Key elements

Primary action: Save search is clearly available where the task happens.
Main view: All results keeps the starting point obvious.
Connected view: People supplies nearby context.
Metric: Results is visible with a meaningful value.
Another signal: Sources helps people judge what to do next.
Representative record: Enterprise permissions rollout makes the example specific.
Second record: Billing migration plan shows the pattern works beyond one item.

States worth designing

No matching records; show what people can do instead of leaving a blank panel.
Loading all results without changing the layout unexpectedly.
Search or filter request failed; explain the problem and preserve work.
Permission denied for people; clarify who can continue.
Success after choosing Save search; confirm the result and the next step.
Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

All results → People → Save search → Review outcome

Patterns used

Search, All results, People, Projects, accessible states, contextual actions

Why these choices work

Preserve the query and chosen filters as people inspect results. Make no-results recovery useful instead of a dead end.

In this design, people should be able to compare Enterprise permissions rollout with Billing migration plan. Make results clear, then use sources 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 “Save search” action. The happy path alone is not enough.

Related UI examples: Advanced Search Filters, Saved Searches, Command Palette.

Start from this in Figr

Design a global search screen for our existing software product. Use our real design-system tokens, components and product language. Show All results and People, include believable records such as Enterprise permissions rollout, and make save search easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr