Knowledge Base
Add organization-wide policies, standards, snippets, and FAQs used by Clearly AI reviews and chat.
The Knowledge Base is organization-wide context for Clearly AI. Use it for policies, security standards, review guidance, runbooks, approved boilerplate, and recurring questions that should inform reviews and chat.
Knowledge Base content is separate from project sources. Project sources describe the system being reviewed. Knowledge Base content describes how your organization evaluates systems.
Knowledge Base management is available to organization admins and owners. If you do not see Knowledge Base in the sidebar, ask an admin or owner to add or update content for you.
What to add
Add material that reviewers expect Clearly AI to apply repeatedly:
- Security, privacy, compliance, or AI governance policies.
- Secure development standards.
- Review procedures and escalation rules.
- Approved answers or standard language.
- Frequently asked questions with known answers.
- Internal guidance that explains how your team interprets a control.
Do not add project-specific design docs here unless they should apply across the organization. Add project-specific evidence to a project instead.
Open the Knowledge Base
- In the sidebar, open Knowledge Base.
- Use Search Knowledge Base to test retrieval.
- Use the Files, Text, and FAQs tabs to manage content.
Files
Use Files for longer reference material such as policies, standards, diagrams, exports, and runbooks.
- Open Files.
- Click Add Source.
- In Upload Files, drag files in or use Browse Files.
- Use Browse Directory when you want to upload a folder.
Each file can also have instructions. Use instructions to tell Clearly AI how that file should be used, for example:
Use this policy for production services that process customer data.
Ignore it for internal-only prototype systems.From the file list, you can download, preview, delete, and add or edit instructions for a file.
Text snippets
Use Text for short reusable context that does not need to be a file.
- Open Text.
- Click Add Snippet.
- Enter Name and Content.
- Save the snippet.
Good snippet examples:
- Standard wording for approved compensating controls.
- Short notes about how your organization classifies sensitive data.
- Review guidance that should be available without opening a full policy.
FAQs
Use FAQs for questions with stable answers.
- Open FAQs.
- Click Add FAQ.
- Enter Question and Answer.
- Save the FAQ.
FAQs are useful when reviewers or engineers repeatedly ask the same thing, such as which policy applies to a common data type or when a specific review path is required.
Search the Knowledge Base
Use Search Knowledge Base to check whether Clearly AI can retrieve the content you expect.
- Expand Search Knowledge Base.
- Enter a focused query.
- Click Search.
Results show matching text, filename, file path when available, size, modified date, and a relevance score. If a policy or snippet is hard to find through search, rename it, add clearer content, or split the document into more focused files.
How reviews use the Knowledge Base
During review generation, Clearly AI can search the Knowledge Base when a review template question needs organization-wide context. This is most useful when the question asks about policy requirements, review standards, approved patterns, or internal control interpretation.
Review Templates can also reference Knowledge Base content directly in question instructions. See Review Templates.
How chat uses the Knowledge Base
Chat can use:
- Text snippets and FAQs as general organization context.
- Search Knowledge Base to find relevant policy or guidance.
- Read document actions to inspect Knowledge Base files before answering.
Chat answers should be treated as AI-generated. Use citations and the Sources panel to verify important claims.
Good practices
- Prefer specific, current documents over large archives.
- Add instructions to files whose scope is limited by region, business unit, product type, or data type.
- Keep snippets short and named clearly.
- Use FAQs for stable answers, not evolving decisions.
- Remove outdated policy versions, or label them clearly as historical.