Press Cmd+K, or Ctrl+K on Windows, from anywhere in the app. A bare / works too when you are not already typing in a field.
What it looks at
For locations, search reads the name, the address, the tags, the description, and your operational notes. It also matches projects and script locations by name, so typing a production's name jumps you to the project rather than to its locations.
Alongside those it finds places in the app itself: settings pages, the dashboard, and help articles. So "billing" gets you to the billing settings without hunting through tabs.
Rough spelling is fine
You do not have to remember a name exactly.
A shortened word finds the full one. "lil cafe" finds Little Cafe. "sunset blvd" finds Sunset Boulevard. This is how people actually write things down in the field, and it is how they type them back later.
Typos are tolerated on names, addresses, and tags, within reason. A letter wrong or transposed still matches. Something genuinely different does not, so "warehouse" will not return Lighthouse just because the letters overlap.
Extra words are forgiven from three words up. Search "lil cafe brooklyn" and you will still find a Little Cafe whose borough lives in the address rather than the name. Those results rank below the clean matches, so you can see which ones needed the allowance. A two-word search stays strict, because "red barn" returning every barn would be useless.
The forgiveness has a floor. Two stray words out of three is not a typo, it is a different place, and you get nothing rather than a page of near-misses.
Ranking
A match on the name outranks a match buried in a description. A phrase found together outranks the same words scattered apart, so "red barn" ranks "the red barn on the hill" above "a barn beside the red gate". Exact beats partial throughout.
The practical effect is that the thing you were thinking of is usually first or second, and you can stop reading.
Narrowing the scope
The chip beside the search box sets where you are looking: everything, just locations, just projects, or inside one project, or inside a single script location within it. Searching from inside a project narrows to it automatically.
Recent searches are remembered along with the scope they were run in, so picking one back off the list puts you where you were rather than at the top of everything.
When to use filters instead
Search answers "where is the one I am thinking of". Filters answer "what do I have that fits".
Once a library is past a couple of hundred locations, filters are the better tool for the second question. Environment, category, type, features, style, rate range, and distance from the production office all narrow together, and the result is a set you can work through rather than a guess you have to phrase correctly.
Search is also only as good as what is in the record. A location with three photos and no tags is findable by name and almost nothing else. That is what the tagger is for. See AI Image Analysis.