# Team memories Source: https://www.hyperagent.com/docs/concepts/teams/team-memories > For AI agents: the documentation index is at https://www.hyperagent.com/llms.txt and the complete documentation in one file at https://www.hyperagent.com/llms-full.txt. Any docs page is also served as Markdown by appending `.md` to its URL. How a team agent's learning becomes shared context During a thread, a team agent learns that enterprise refunds require Finance approval. Once saved, that correction can guide the agent's future runs. It doesn't become guidance for every team agent until an Owner or Editor reviews and promotes it. An observation can help the agent that made it immediately. It becomes team guidance only after an Owner or Editor reviews and promotes it. **Team memories** are the reviewed policies, decisions, conventions, and facts that team-owned agents can use across their work. ## Agent memory or team memory [#agent-memory-or-team-memory] A team-owned agent can draw from its own memories and the team's shared context. Keep learning with one agent when it belongs to that role; promote it when other team agents should rely on the same guidance. Reviewed context that team-owned agents can retrieve according to their knowledge settings. Context that belongs to one team agent. It can help that role without changing what the rest of the team relies on. ## Manage shared context [#manage-shared-context] Team memories live on the team's **Workspace memories** page. The list groups memories by owner and can be filtered by category, agent, audience, pinned, or archived. Every team role can read shared memories. Owners and Editors add, edit, archive, and organize them; only Owners delete them permanently. See [Team roles](https://www.hyperagent.com/docs/concepts/teams/members) for the complete permissions matrix. ## How learning becomes shared [#how-learning-becomes-shared] ### The agent saves what it learned [#the-agent-saves-what-it-learned] Learning from a team agent starts in that agent's own memories. The new context can help the same role again without changing guidance for the rest of the team. ### An Owner or Editor reviews it [#an-owner-or-editor-reviews-it] They confirm that the memory is accurate, durable, and useful beyond the agent that learned it. ### They promote it to Team memories [#they-promote-it-to-team-memories] The same memory moves into the team's shared context. The originating agent can still use it, and promotion doesn't create a duplicate. When the team already knows a policy or decision, an Owner or Editor can add it directly with **+ New workspace memory** instead of waiting for an agent to surface it. ## Promote or move a memory [#promote-or-move-a-memory] Use the memory's actions menu to change who owns it. Both actions stay inside the team workspace. Move an agent-owned memory into shared context after it has been reviewed. The originating agent keeps access through the team memory. Give a team memory to one agent when the context no longer belongs in shared guidance. Earlier agent links are cleared. Neither action creates a copy or moves context into someone's personal library. A team-owned agent uses the team's context and its own memories, not the personal memories of whoever starts the run. A personal agent shared with the team keeps the same knowledge access it already had; sharing it doesn't open the team's memories or another person's private context. Version history records edits to a memory's content. It doesn't record ownership changes such as Promote to Team memories or Move to an agent. Check the memory's current location to see who can use it now. ## Related guides [#related-guides] * [Memories](https://www.hyperagent.com/docs/concepts/memories) explains memory fields, retrieval, editing, archiving, and the full ownership model. * [Knowledge access](https://www.hyperagent.com/docs/concepts/agents/knowledge-access) controls which memories an agent can retrieve and where it saves new knowledge. * [Manage learning behavior](https://www.hyperagent.com/docs/learning/manage-learning-behavior) controls when an agent may suggest or save new memories. ## FAQs [#faqs] Because learning starts narrow on purpose. A team agent's new memory belongs to that agent until an Owner or Editor promotes it, so one agent's learning doesn't become shared guidance before review. No. Promotion broadens who can use the same memory. The agent that learned it keeps access, and there is only one record to maintain. No. **Promote to Team memories** and **Move to an agent** both stay inside the team workspace. Neither action pulls from a personal library or pushes into one. No. A team-owned agent uses the team's memories and its own, regardless of who starts the run. A personal agent shared with the team keeps the knowledge access it already had. Not from version history. It records changes to a memory's content rather than moves between owners. Check the memory's current location to see who can use it now.