Search
Search is the main non-Explorer entry point.
Use it when you know roughly what you need but not where it lives.
What Search covers
- repository items by name, type, author, and folder scope
- full-text content search
- full-text result modes for documents or passages
- provider-backed mail search when your deployment exposes connected mail search
Reliable search workflow
- Start with one stable term: an exact phrase, identifier, sender, or filename fragment.
- Narrow by item type or folder scope.
- If full-text results are noisy, switch from whole documents to passages.
- Open the result and verify the folder context before editing, moving, or sharing anything.
Content query syntax
In content search, spaces mean OR: apple orange finds passages with either
word. Use apple AND orange to require both words in one passage. Put a phrase
in double quotes to require those words together and in order, such as
"red apple". Use AND NOT or - to exclude a word or phrase, and parentheses to
group alternatives: apple AND (orange OR pear).
This syntax applies to repository content search. Name search and connected mail-provider search have their own query rules.
What Search is not for
- deciding long-term ownership
- replacing the folder tree for everyday navigation
- hiding duplicate structures that governance should fix
Failure patterns
- using Search as the only way to find team work
- ignoring folder context after opening a hit
- assuming provider mail search behaves exactly like repository content search