Who maintains which layer

Optional index paths: inject that article only when it matches a file path in the user’s attachment or message. Applies to all three layers. See Three layers and System knowledge i

Source help/en/knowledge-layers/who-maintains.md

Layer	Usually maintained by	User-facing entry	After the body changes
System	Platform admin	Admin console System knowledge base	Admin console Rebuild index with AI
Workspace	Workspace creator or authorized admin	Workspace collaboration → Manage workspace knowledge base	Knowledge page Generate index with AI
Personal (knowledge base)	Agent owner	My agents → an instance → Knowledge base	Same as above
Personal (memory)	Agent owner	My agents → Memory, or Messages Remember	Next round after save; auto-extract after each Q&A

Optional index paths: inject that article only when it matches a file path in the user’s attachment or message. Applies to all three layers. See Three layers and System knowledge index.

Who to ask for common problems

Help agent answers are stale, or platform-wide notes are wrong → contact a platform admin to update system knowledge and rebuild the index.
Team-shared notes are wrong (policy, process, project background) → ask the workspace creator (or whoever maintains team knowledge) to update the workspace knowledge base.
One assistant’s metrics are wrong → that assistant’s creator maintains its personal knowledge base; check whether it should move to the workspace layer (team-shared) instead of personal.
The assistant does not remember your preferences → confirm it is a workspace agent, not the help agent; check entries on the Memory page, or see Agent memory.

Permissions (short)

With no workspace selected, you only get system-layer help plus creating/switching workspaces.
After you enter a workspace, whether you can edit workspace knowledge depends on being the creator or later finer roles (current environment).
Personal-layer knowledge only affects that agent instance; back up important Markdown before deleting an agent.