Skip to main content
Global Search is the current desktop quick-jump control for finding supported records without opening each feature first.

Current search behavior

Start typing in the desktop search field. Search begins after:
  • At least 2 characters.
  • A short debounce of approximately 300 ms after typing stops.
The request is authenticated and, when a valid active workspace is supplied, verifies workspace membership before returning workspace-scoped results. If the supplied workspace cannot be verified, the backend falls back to the caller-scoped records allowed by the current search function rather than granting cross-workspace access.

What it searches

The current global search function returns four groups: Matching is case-insensitive and uses partial text containment.

Result limits

The backend checks a bounded set of recent workspace records and returns up to 5 matches per category in the global dropdown. Global Search is therefore designed for navigation, not for exhaustive reporting across every historical record. If you need deeper filtering, open the relevant feature page and use that surface’s own filters/search where available.

Workspace scope

When Global Search is called with the active workspace, the backend verifies that the signed-in user is allowed to search that workspace before using the workspace-wide record set. This means a search result should not be treated as a way to discover another customer’s campaigns, posts, media, or social accounts. Switch to the intended workspace before searching when you manage more than one.

No separate search index

The current implementation does not maintain a separate user-facing search index that has to “catch up” after every content change. The search function reads the relevant current records, applies text matching, and returns the bounded matches. If a newly created item does not appear, check:
  • The active workspace.
  • The exact field being searched.
  • Whether it is inside the bounded record set used by global search.
  • Whether the item actually contains the query text.

Desktop and mobile

The current GlobalSearchBar is part of the desktop application layout. The current five-tab mobile shell does not expose the same global-search icon/control in its header, so this page does not describe a mobile global-search workflow that is not presently there. On mobile, open the relevant destination such as Campaigns, Schedule, Connections, or Media Library and use the controls available on that surface.

Search examples

Find a campaign

Search a distinctive word from the campaign name or description and open the Campaign result.

Find a post

Search text from the caption/message. Selecting the result opens the Schedule route with the post reference.

Find media

Search part of the filename, a stored tag, or supported caption text. Selecting the asset opens the Media Library with the filename search prefilled.

Find a connected account

Search the profile name or username and open Connections to inspect the current connection state.

What Global Search does not search today

The current backend function does not return dedicated result groups for:
  • Notification text.
  • Activity-log entries.
  • Support cases.
  • Chat conversation history.
  • Approval notes as their own result type.
  • Billing records.
  • Arbitrary provider-side content that has not been represented in the searched Socializioz records.
Use the feature that owns that data instead.

Troubleshooting

Last modified on August 16, 2026