Create a Knowledge collection
Creating a collection
Section titled “Creating a collection”- Go to Console → Knowledge
- Click New collection
- Give it a name (e.g., “Product Docs”, “Company Handbook”) and, if you like, a description, then click Continue
- Choose where the content comes from: Files, Website, GitHub, Google Drive, Confluence, Notion, Library folder or ServiceNow
- Set up the source and click Create collection
Auteryn begins syncing and indexing your content. Small file uploads take a few seconds; a large Confluence space or website can take a few minutes.
To add another source to a collection later, open it and click Add source.
Upload files directly
Section titled “Upload files directly”Supported formats: PDF, DOC, DOCX, TXT
- Choose Files as the source
- Click to add files
- Each file can be up to 10 MB; your plan sets the total storage
- Click Create collection. The files are indexed straight away
Files you upload on the Files tab of the Knowledge page can be sorted into folders. The Library folder source adds a whole folder to a collection.
Connect a data source
Section titled “Connect a data source”For content that changes regularly (Notion pages, a Confluence space), connect a live source so your knowledge stays up to date automatically.
See Connect Data Sources → for the setup of each source.
Attaching a collection to an agent
Section titled “Attaching a collection to an agent”- Open the agent in the Console
- Go to the Knowledge section
- Click Attach knowledge and pick the collection this agent should search. An agent has one Knowledge attachment.
Preview answers on the attached collection shows which passages a question would retrieve.
Best practices
Section titled “Best practices”- Name knowledge collections descriptively — “Q4 2025 Product Changelog” is better than “KB-3”
- Keep content focused — one knowledge per topic or team is easier to manage
- Test after syncing — ask the agent a question you know is answered in the content, and verify it finds the right answer
- Remove stale content — if your docs change significantly, re-sync to avoid the agent surfacing outdated information

