Knowledge
Who is this for? Everyone. Knowledge is your workspace's shared library of documents, SOPs, and reference material that Adomo reads when it answers questions and runs processes.
The Knowledge section of the sidebar holds the documents your workspace has given Adomo: policies, SOPs, product docs, price lists, meeting notes, anything your team wants the AI to know. The more relevant knowledge your workspace has, the better Adomo's answers and drafts get.
How to add documents
To add a document, open a collection on the Knowledge page and click Upload. You can upload one or more files at a time (PDF, Word, PowerPoint, Excel, CSV, plain text, Markdown, and HTML; up to 50 MB per file). Each file is virus-scanned, then extracted and indexed so Adomo can use it. A document only becomes searchable once that finishes - the Knowledge page shows its status meanwhile.
When a document changes, replace the old one rather than adding a second copy. Uploading a revised file creates a new, separate document - the previous one stays in the collection and Adomo will keep drawing on both, which is the usual cause of answers quoting superseded policy. Delete the old document, or if the file name and location are unchanged, use Re-ingest on the existing document to pull in the current contents.
Files you attach in chat are available to that conversation (and to file search there), but they are not added to workspace Knowledge. To make a document part of Knowledge, upload it to a collection.
Collections
Group related documents into collections (for example, "Finance SOPs", "Sales Playbooks") so they're easy to find and share as a set.
How knowledge gets used
- In chat. When you ask a question, Adomo draws on the knowledge you have access to and answers with that context. Answers come back with the source passage attached, so you can open it and check the answer against the document it came from.
- In processes. Process steps can reference knowledge, and you can generate a whole process directly from an SOP document (see Processes (Workflows)).
- In decisions. Files produced by earlier steps of a run can be attached to an approval request so reviewers have the context in front of them. (Attaching a Knowledge document directly to a decision isn't supported yet.)
Search
The Knowledge page has a global search across every document you can access, and the recently updated list shows what's changed lately.
Sharing and access
Knowledge follows the same sharing model as processes. Each collection can be shared with individual people, groups, or the whole workspace at three levels:
- View - read the content
- Contribute - read, and take part in the collection
- Manage - edit settings, change sharing, delete
Note that uploading, and creating or deleting collections, currently requires the workspace owner or admin role regardless of the sharing level you've been given. If you need a document added and don't see an Upload button, ask an admin.
Access control carries through to the AI: chat and processes only use knowledge the requesting person is allowed to see. A document restricted to managers will never inform an answer given to someone outside that group.
FAQ
Should I put sensitive documents in Knowledge?
Knowledge respects access control, so restricted content stays restricted. That said, follow your company's data handling policy, and scope sensitive collections to the smallest group that needs them.
How current is the knowledge?
Documents are used exactly as uploaded. When a policy or SOP changes, either Re-ingest the existing document or upload the new file and delete the old one. Leaving both in place means Adomo can answer from either.
Adomo answered from an outdated document. What do I do?
Check the citation on the answer to identify which document it came from, then re-ingest or delete that document in Knowledge. If you can't (upload and delete need admin), flag it to your workspace admin.