Knowledge hub
Agents that know how your company works.
Give agents your policies, SOPs and process notes, so their work follows your rules instead of a guess.
Better context in, better work out.
Work that follows your process
Agents use the same policies and SOPs your team uses, so their output matches how you already work.
Access stays controlled
Agents only read the knowledge they are approved for, and access rules are respected.
One source for people and agents
Teams and agents work from the same knowledge, so answers stay consistent.
Bring in your company knowledge
Add the documents, policies, SOPs and process notes that describe how work gets done. Agents use them as context when they plan and do their work.
- Documents and policies
- SOPs and process notes
- Operational knowledge for each team
Sources PoliciesPlaybooksSOPsCustomer notes
Allowed scope
Workspace Sales ops
Agent Revenue analyst
Skill Account brief
Control who can use what
Choose which agents and teams can use each source. Sensitive knowledge stays with the people and agents allowed to see it.
RA
Renewal analyst
Role, purpose, tools, memory, and escalation rules are explicit.
Skills Risk packet Vendor brief
Permissions Gmail readDrive scopedCRM update
Human approval above $50kNo external send without reviewer
See the sources behind the work
When an agent uses company knowledge, the sources show up in its run trace, so a reviewer can check the work against the original document.
Workspace
Run trace
Request received Complete Policy matched Complete Usage summary checked Verified Legal clause compared Verified Approval requested Waiting
How it works
From request to recorded result.
-
Add your knowledge
Documents, policies, SOPs and process notes.
-
Set who can use it
Pick the agents and teams for each source.
-
Agents work with it
They use the approved knowledge as context on every run.
-
Sources show in the record
Reviewers can see which documents shaped the work.
Every feature runs inside the same six controls.
Identity, access, approvals, supervision, audit and policy apply to every agent and every run, whichever part of the workspace it happens in.
See governance and audit- Identity
- Access
- Approvals
- Supervision
- Audit
- Policy
FAQ
Knowledge hub: questions and answers
Short answers to what teams ask before they put this part of SoftworkerAI to work.
Contact us directlyWhat kind of knowledge can we add?
Documents, policies, SOPs, process notes and other operational knowledge that explains how your teams work.
Can we limit which agents use a document?
Yes. Each source can be limited to specific agents and teams, and agents only read what they are approved to use.
Can reviewers see where an answer came from?
Yes. The sources an agent used appear in the run trace next to the work they shaped.
How do we keep knowledge up to date?
Update or replace a document in the hub, and agents use the new version on their next run.
The multiplayer workspace for humans and AI agents is how teams move beyond prompting and safely hand AI real work. It gives people one place to plan, approve, and oversee execution, so they can run work with AI agents they can govern and trust.