Company knowledge
Knowledge that stays connected to its evidence.
Preserve operating knowledge with source evidence, revisions and review, in the folders where it applies.
CCompany knowledgeOperations folder
Operating policy
Orders above the agreed threshold require manager review.
- Scope
- Operations folder
- Source
- Operating policy · Revision 2
- Status
- Proposed · Needs review
Illustrative example · Company knowledgeFrom context to outcome
01 / Company knowledge
Separate knowledge from conversation
A useful message can inform a proposal. It does not become accepted company knowledge on its own.
In your workflowEvidence becomes knowledge.
- 01Separate knowledge from conversation
- 02Keep the source close
- 03Learn within boundaries
Open workspace ↗ 02 / Company knowledge
Keep the source close
Attach evidence and revision context so a reviewer can understand why knowledge exists.
In your workflowEvidence becomes knowledge.
- 01Separate knowledge from conversation
- 02Keep the source close
- 03Learn within boundaries
Open workspace ↗ 03 / Company knowledge
Learn within boundaries
Knowledge follows live folder permissions, including when it is used by an agent.
In your workflowEvidence becomes knowledge.
- 01Separate knowledge from conversation
- 02Keep the source close
- 03Learn within boundaries
Open workspace ↗ Context with clear boundaries
Work within the folders and permissions available to your account. Review sensitive actions before they continue.
Explore access controls →Questions, answered.
Who can use this feature?+
Access depends on your workspace membership, folder permissions and configured capabilities.
How does it work with the rest of CoFolders?+
Use related resources in the same business context. A link between resources provides context and does not grant additional access.
Connected to the rest of your work.