# Knowledge bases (/chat/knowledge)



Ask Sim to create a knowledge base, add source documents, or search existing content. Use a knowledge base for documents retrieved by meaning, such as support policies or product guides. Access and permitted operations follow workspace and organization policy.

## Create a knowledge base [#creating-knowledge-bases]

Name the base and describe the content it should hold:

* "Create a Product Docs knowledge base for our product documentation."
* "Create a knowledge base from our sales playbook and configure the outbound workflow to search it."

## Add and process documents [#adding-documents]

Attach a supported file, paste text, or provide an accessible URL:

* "Add this PDF to Product Docs." Attach the PDF.
* "Add this text to Support KB as a new document: \[content]."
* "Fetch \[URL] and add its content to competitive intelligence."

PDFs, Markdown, plain text, and content fetched from web pages can be ingested. Sim can help process and index the documents. Content is searchable only after processing completes successfully and the document is enabled.

Ask Sim to check the documents added by the request and report processing failures. A saved document or an accepted upload does not itself prove the content is indexed. If processing fails, inspect the error and retry after fixing the cause.

Chat attachments stay with their conversation. Adding one to a knowledge base is a separate request; it does not automatically save a reusable workspace file.

## Search the content [#querying-knowledge-bases]

Specify the knowledge base and question:

* "What does Product Docs say about refunds?"
* "Search Support KB for SSO setup errors."
* "Compare Pro and Enterprise features using the product docs."

Sim retrieves matching content to answer the question. Check that the returned evidence comes from the intended documents; a partial search or no matches does not establish that the base contains no relevant information.

Chat can mask tracked secret values or omit documents, passages, and tag values it cannot safely check, even when indexing and access checks pass. Document-list counts can still describe the underlying collection. Check the knowledge base directly when expected content is unavailable to Chat.

## Keep sources updated [#connectors]

Connectors sync documents from external services on a configured schedule. Ask Sim to create or update the connection, or run a sync, using an available credential and the source you want:

* "Sync the support page tree from Notion into Support KB."
* "Connect the onboarding folder in Google Drive to the customer success knowledge base."
* "Sync this GitHub repository's documentation into Product Docs."

Supported sources also include cloud storage such as Dropbox and OneDrive, wikis and issue trackers such as Confluence and Jira, and CRM records such as HubSpot and Salesforce. See the [connector guide](/knowledgebase/connectors) for the current source list, setup requirements, and sync frequency options.

New and changed content becomes searchable after syncing and processing. Source removals are reconciled during sync; they are not guaranteed to disappear on every run. Check connector status and errors if the knowledge base appears out of date. Search remains subject to the caller's access permissions.

## Use a knowledge base in a workflow [#using-knowledge-bases-in-workflows]

Ask Sim to configure one of these retrieval paths:

1. Add **Knowledge Search** to an Agent block's tools and select the knowledge base.
2. Add a Knowledge block before the Agent, select the base, and reference the search results in the Agent's prompt.

The base must be accessible and its documents successfully indexed. Selecting a base does not grant access to documents withheld by policy.

A workflow can also add documents through **Knowledge Create Document** or **Knowledge Upsert Document**. Configure the intended base and content, then verify that processing completes before relying on retrieval.

## Manage documents and bases [#managing-knowledge-bases]

Ask Sim to inspect the inventory or remove specific content:

* "List knowledge bases in this workspace."
* "How many documents are in Support KB?"
* "Remove the outdated pricing document from Product Docs."
* "Delete the old-competitive-intel knowledge base."

Document deletion cannot be reversed by restoring the knowledge base. For connector-managed content, correct the source and sync it again rather than editing its indexed chunks.

## Private knowledge graphs [#private-knowledge-graphs]

On deployments that enable this restricted capability, eligible platform administrators with **Super admin mode** enabled can open **Knowledge graphs** in organization settings. These private Chat memory graphs are separate from the workspace knowledge bases described above.

Select **New graph**, enter a name, and choose **Create and activate**, or choose **Make active** beside an existing graph. Graph names can have 1–100 characters and cannot be `Default` in any capitalization. The **Default** graph preserves the original memory.

Each graph is private to you in that organization. The active graph is selected for new chats in the organization and its workspaces; existing chats keep their original graph. Selecting or creating a graph keeps the other graphs and does not grant access to workspace knowledge-base documents.

## Related docs [#related-docs]

* [Knowledge bases](/knowledgebase)
* [Connectors](/knowledgebase/connectors)
* [Using knowledge bases in workflows](/knowledgebase/using-in-workflows)
* [Debugging retrieval](/knowledgebase/debugging-retrieval)