Search, cited answers, and the knowledge graph¶

Outcome¶

You will be able to find synced project information, ask a grounded question, inspect the sources behind an answer, and follow relationships between items.

Before you begin¶

You need at least the Viewer role in the project.
At least one source must have completed a sync.
Select the correct project before searching. Knowledge and answers never span projects.

Find an item¶

Open Knowledge and keep the List view selected.
Enter a phrase in Search whole project and select Search.
Open a result to inspect its source, status, body, details, neighborhood, and linked items.
Use Open in source when you need to verify the original record.
Select Back to browse to return to the paginated knowledge list.

Search is semantic: a useful phrase such as decisions about pricing usually works better than an exact identifier. It searches the whole current project and returns matching entities; it does not generate an answer.

When browsing instead of searching, use the Decisions, Action items, Meetings, This week, type, or Themes filters. This week filters only the currently loaded page.

Find a document¶

Documents written in Threadory have their own list: Knowledge → Documents.

Type in Search titles and text and select Search. The search finds the words as typed (case does not matter) in a document's title, its line name and summary, and — from three characters on — in the text of its current version. A row found only by its text says Matched in text and shows the passage around the first match.
Narrow the list with the selects: type, status, Any author and Any work item. Filters combine; Clear resets them all.
Author lists everyone who created or edited a version of a document; Me (…) is you. A document counts for an author when they wrote any of its versions, not only the latest.
Work item lists the work items documents point to, by title when Threadory knows the item, otherwise by address. It keeps documents whose current version points to exactly that item.

Text you just saved is found by its title at once and by its text a few seconds later, once Threadory has indexed it.

The browser tab shows the current page or loaded item name followed by Threadory. For native documents it follows the selected version and a saved rename, making several open documents easier to distinguish.

Native documents use the available page width for reading and editing. On large monitors, tables and the editor expand with the window; on narrow screens, wide tables scroll horizontally.

Comment on a document¶

Members can select text in a native document and choose Comment. A form opens next to the selection, with its quote and section. The comment is saved against the version on screen. Choose Internal — team only to keep it off public links. You can also leave a general comment in the panel below the document. Viewers and archived documents are read-only.

The general comment keeps its own draft while you compose, send or cancel a selected-text comment. Cancel or Escape discards only the selected-text draft. If sending fails, the form keeps your text for retry. Changing versions closes the selection form but keeps the general draft; that draft will be submitted on the version currently on screen. Opening the editor discards both drafts; save your comment first.

Review every shared link¶

Members (member role and above) can see all public links to the project's documents on one page: Knowledge → Documents → Shared links.

Each link shows its document, label, whether it is Living (always the latest version sent for review or approved) or Pinned to one version, who can read it, who created it and when, its expiry, the number of views, and its state: Active, Expired or Revoked.
Active shows the links that still work; All adds revoked and expired ones.
To send an active link again, select Copy link: its address goes to the clipboard. If your browser does not allow that, the address appears in a field — select it and copy it. Every copy is recorded in the project's audit log.
To stop a link from working, select Revoke and confirm. It stops working at once for everyone who has it.

The same Copy link is next to each active link under Publications on the document itself, so closing the box that shows a new link loses nothing.

There are two reasons a link may have no Copy link:

"Copying links isn't set up on this server" above the list: your Threadory server is not configured to show a link's address again, so no link can be copied — not even a new one, whose address is then shown only once, when you create it. Ask your administrator; creating another link does not help.
"Created before copying links was available here" next to one link: copying works, but this link is older and its address was shown only once. To share that document again, open it and create a new link under Publications (and revoke the old one if nobody should use it any more).

A revoked or expired link, or a link to an archived document, has nothing to copy.

What the page of a link ends with¶

On the Free plan the public page of a link ends with “Shared with Threadory · Specs with client comments and sign-off · Start free”, and a PDF downloaded from it has “Exported from Threadory · threadory.ai” on every page. On a paid plan the page keeps only the plain “Shared with Threadory” credit and the PDF has no credit line; an owner or admin can switch the full Threadory footer on in Settings → General. The link in that line goes to the Threadory site and never contains the address of your document.

Ask a question with cited sources¶

Select the floating Ask Brain button.
Ask one focused question about the current project.
Read the answer and expand your verification to the Sources shown below it.
Open each relevant source and compare the answer with the synced item.
Ask a follow-up in the same panel when more context is needed.

Ask Brain can also be opened from an entity with Ask Brain, or from a graph with Ask Brain about this. The conversation keeps a short recent history. If the available evidence is below the answer threshold, the panel shows Limited information available instead of presenting a confident answer.

Warning

Citations are evidence links, not a substitute for checking the source before making a consequential decision.

Limit retrieval with a knowledge scope¶

Project admins can create named retrieval scopes in Settings → Advanced → Knowledge Scopes. A scope narrows retrieval by entity type, source system, labels, an entity UUID allowlist, or a combination of those restrictions.

After creating a scope, you can select it for one Ask Brain conversation, set it as a skill default, or attach it as the default for a new MCP API key. Request-level filters are intersected with the scope; they cannot broaden it. For projects indexed before knowledge scopes were introduced, ask an operator to reindex before relying on label filters.

Scoped Ask conversations use the indexed knowledge graph only. Live federated connector search is skipped because live providers do not expose a uniform label and entity-allowlist contract.

Warning

A knowledge scope guides retrieval; it is not an access-control boundary. Project roles and API-key permissions still control access. Direct MCP point and list tools remain project-scoped rather than knowledge-scoped.

Explore relationships¶

Open Knowledge and select Graph.
Search for an entity, then select it to center the graph.
Use the legend to distinguish entity types.
Select a neighboring node to make it the new center.
Select the title above the graph to open the centered entity's details.

The graph shows direct relationships in the current project, in both directions. The entity detail page provides more context:

Neighborhood is a compact visual view of nearby items.
This item links to lists outgoing relationships.
Referenced by lists incoming relationships and their human-readable relation, such as resolves.

Verify the result¶

A search result opens an entity whose source and content match your query.
A grounded answer includes relevant entries under Sources, or clearly reports that information is limited.
Selecting a graph neighbor changes the centered entity and its connection count.

Common problems¶

Symptom	Likely cause	What to do
No search matches	The source has not synced, the phrase is too narrow, or you selected another project	Check Activity, confirm the project, and try broader terms
Browse filters hide an expected item	A type, theme, or page-local This week filter is active	Select Clear and move between pages
A document is not found by a word in its text	The search is shorter than three characters, the words are not next to each other as typed, or the text was saved a moment ago	Search for one distinctive word of at least three characters, or wait a few seconds
Ask Brain reports limited information	Retrieved evidence did not meet the confidence threshold	Rephrase the question, sync the source, or inspect Knowledge directly
An answer has no useful source	The project lacks indexed evidence for that claim	Do not act on the answer; verify the original system and report the gap
Graph says there are no connections	The item exists but no relationship has been ingested or inferred	Open the entity details, check linked items, and allow the relevant sync or skill to finish
An entity is shown as deleted	The upstream record was removed	Treat it as historical context and open the source only if it still exists

Next step¶

Learn how skills produce project outcomes, or use Reports and Graph Health to find missing closed-loop links.

Returning to a list¶

Knowledge keeps the active tab, filters, tags, search text and pagination in the URL. Open a document, then use Back to Documents, the Documents breadcrumb, or your browser's Back button: the original selection is restored. The List view works the same way. Switching tabs preserves each tab's filters, and a reload keeps them too. Text typed into search but not yet submitted is preserved separately from the search that produced the results when you leave the field.

Rows are fetched again on return, so document changes are visible. Documents reloads the pages previously opened with Load more (up to 100). Scroll position is restored in the same browser tab after rows load; it can shift if rows changed. A direct document link without a list context returns to Documents. URL filters belong to the active project: opening a link for another project does not switch projects or apply that project's filters.