Share approved team knowledge
Give agents stable reference material without mixing it with ordinary uploads.
Use shared knowledge for information that should guide work repeatedly: a team brief, an approved process, or a maintained reference.
Files and knowledge are not interchangeable. Uploading a Markdown file does not automatically make it approved knowledge.
Find Team Knowledge
Open Team → Files and look for Team Knowledge. Managed knowledge and reports keep their own editing and review rules.
All current Organization members can read approved shared knowledge. Management actions depend on role and content type.
Write useful reference material
Keep one subject per document. State the owner, purpose, and current rules. Prefer concrete instructions over broad claims.
For example:
Customer updates must distinguish shipped features from planned work. Link the release note for each shipped feature. Do not include customer names without permission.
Do not place credentials or private personal records in a shared reference.
Review before approval
Owners and admins can review and manage shared knowledge through its available actions. A draft is not an approved instruction.
Check the exact saved content before approving. When a document changes, review the updated version rather than assuming an earlier approval still applies.
Use knowledge in a task
Name the relevant reference and ask the Agent to read it before applying it. If the Agent cannot access it, provide a permitted source or resolve access first.
Current approved guidance should take precedence over an old remembered rule.
Profile Reports
Managed Profile Reports can have special ownership and edit rules. A member's ability to edit the body of their own report does not grant permission to rename, move, approve, or edit everyone else's reports.
Managed folders may not allow ordinary file actions. Use their owning workflow instead of trying to bypass the restriction.