Note: Knowledge bases are deployed via Vault, so only users with Vault access can view or query them.
Overview
Knowledge bases allow workspaces to store, organize, and share internal knowledge seamlessly. By housing key resources such as documents, templates, playbooks and more, teams can quickly access and query them through Assistant.
Knowledge Bases are designed for seamless collaboration. Here’s how they differ from regular Vault projects:
Visibility: Knowledge bases can be published workspace-wide, ensuring every professional has access. Regular projects, on the other hand, are limited to specific users or shareable links.
Query Storage: Knowledge bases store only files—queries are saved exclusively in each user’s History. In contrast, regular projects retain queries, making them accessible to all authorized users.
Create a Vault Knowledge Base
Note: Knowledge Bases can be created and published to end users that have access to Vault.
Standard Vault project limits (number of files, file size, etc) apply to knowledge bases. See here for more.
To set up a new knowledge base:
Click on ‘Create knowledge base’ from the Vault page.
Enter a knowledge base name.
Select documents you wish to upload via the file uploader or supported integrations.
All files must be placed inside of a folder. We highly recommend creating an organized set of (nested) folders to allow users to easily filter their queries to only relevant documents.
Click ‘Create knowledge base.’
To share the knowledge base:
Click on ‘Share’ on the top right of the knowledge base.
Select “Everyone at... ” or individual users.
Users with access to Vault will see the knowledge base appear in Vault and Assistant.
To query the knowledge base:
Open Assistant and click ‘Choose from Vault’.
Select the desired knowledge base, which should be sorted to the top of the list.
Select one or more folders to query.
Note that files are not displayed when querying knowledge bases, as it may be difficult for users to navigate and select thousands of files. Only folders are displayed for ease of selection.
Input your prompt and click ‘Ask Harvey’ to submit.
FAQs
Q: Can I use DMS integrations or Vault upload API to create a Vault Knowledge Base?
Yes, uploading to knowledge bases is the same as standard Vault projects.
Q: Can admins create multiple knowledge bases within the same workspace?
Yes, we support an unlimited number.
Q: How are knowledge bases represented in Usage and History?
Queries from a knowledge base are labeled with “Knowledge Base” as the source.
Q: How should admins organize a knowledge base with all of their organization’s documents?
We’ve seen customers set up folders based on…
Practice area
Jurisdiction
Document type or intended use of document (e.g. precedents)
We recommend using only 2-3 levels of nested folders to keep the knowledge base easy to navigate for end users.
Q: Can threads based on knowledge bases be shared with other users?
Not at this time; however, we are interested in supporting this in the future. Please reach out to us if this is a feature you are interested in.
Q: Are knowledge bases subject to data retention?
No, knowledge bases (and the files contained within) are retained indefinitely until the creator or another admin deletes it. Any queries that a user makes in Assistant using the knowledge base are subject to the Assistant query retention policy (if configured).
For further assistance, please contact [email protected]