Find work with search
Bridge’s advanced search is in beta. Start with the area where the work belongs and a short, recognizable name. Available search controls and results can differ between the web and native apps.
Choose a useful starting point
| What you know | Where to begin |
|---|---|
| A project name or associated organization | Projects |
| An item name, location, or inventory request | Inventory |
| A task title, board, or responsible person | Tasks |
| A file name or project document | Documents |
| A person’s name or profile email | People, when you have access |
Search fields on a particular screen can be limited to that view or area. Broader search is a different scope. Check the placeholder and current workspace before assuming a search covers everything.
File names and document text are different
Finding a document by name does not search the same data as the Search control inside an open document. In-document search looks through the text available to that viewer. Scans can depend on successful text recognition, and newly processed files may not yet have all expected searchable text.
If a result is missing, try a shorter name, remove restrictive view filters, check the workspace, and confirm your access. Use a record’s normal list or project location to verify it exists before creating another copy.
Search respects context
Search is not a way to gain project or workspace access. Different roles and scopes can produce different results. An unavailable result can reflect access, the selected area, processing state, or the data available to your build.
Offline search can only use information available on that device; it is not a promise that every server search or document index is downloaded. Reconnect when you need to confirm current server results.
Future AI connections
Specialized search is part of the foundation for future AI capabilities. This does not mean a general AI assistant, public application API, or MCP connection is available in the current release. See Feature availability.