Search

1. Open Search in the active workspace.
2. Type a few distinctive words into Search current Markdown.
3. Use Scope to choose the vaults to search.
4. Select a result’s path or snippet to open its page.

Results group matching sections by file and show headings, snippets, and line ranges. A conflicted page can carry a conflict label. Open the source before treating a snippet as the full answer.

​

Choose the scope deliberately

Shared vaults searches the company and team vaults you can access. Personal vaults are excluded from that default even when you own them. Select a personal vault explicitly to include it. Selecting specific vault buttons searches that selection; choose Shared vaults to return to the default shared scope. You can only search authorized material in the current workspace.

​

Write a useful query

Search is lexical: it looks for words, not conceptual similarity. Try a heading or distinctive words used in the document. A filename alone may not match unless those words also appear in the indexed content. Browse the Knowledge tree when you know a path but not the page text. Use a few plain words such as client onboarding. The web search box does not expose the integration API’s exact-phrase mode. If you get no results, use fewer terms, try the language used by the author, confirm the workspace, and check the selected vaults. If a new edit has not appeared yet, let it finish saving and try again.

​

Know what is excluded

Ordinary knowledge search covers current Markdown. It does not search deleted content, all historical revisions, the Skills library, templates, Follow-ups, or your Agent Profile. A skill copied into a vault is ordinary Markdown and can appear in knowledge search. Open the separate libraries directly. Inspect historical text through Activity. The current Search screen exposes text and vault selection. More detailed filters supported by integration interfaces are not extra controls hidden in this screen. Search on a local replica uses your editor or filesystem tools.