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; each is extracted and indexed so Adomo can use it. Upload a new version the same way when a document changes.
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.
- In processes. Process steps can reference knowledge, and you can generate a whole process directly from an SOP document (see Processes (Workflows)).
- In decisions. Relevant documents can be attached to approval requests so reviewers have the context in front of them.
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 - add and update documents
- Manage - edit settings, change sharing, delete
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 as uploaded. When a policy or SOP changes, upload the new version so answers stay accurate.
Adomo answered from an outdated document. What do I do?
Update or remove the stale document in Knowledge. If you can't (no manage access), flag it to the collection's owner or your admin.