The settings an owner controls
On Team and Enterprise, memory is an organization capability first and a personal setting second.
| Setting | Where | Default | What it does |
|---|---|---|---|
| Memory for the organization | Organization settings > Capabilities | On | Stops account memory; some project memory remains active; retention rules still apply |
| Memory per member | Settings > Your Claude > “Generate memory from chats” | On in organizations created on or after October 31, 2026; off in older ones until the member turns it on | Each member decides within what the organization allows |
| Sensitive topics | Organization and personal settings | Off | Enabling it for the organization does nothing until each user opts in |
| Use account memory | On each Project page | On | Off keeps that Project’s memory fully separate |
| Data export by members | “Allow members to export their own data” | Owner decides | Lets members download their own data |
Owners and Primary Owners manage the organization switch. They cannot turn memory on for one individual, and they cannot view or edit individual members’ memories.
Reasons to turn it on
- Less repeating. Memory carries who someone is, what they work on and how they like answers into new chats.
- Per-Project separation is available. Every Project has its own memory. Use one Project per client and turn off “Use account memory” for full separation.
- Members stay in control. Each person can read and edit their topics under Settings > Your Claude > Manage, pause memory, or use incognito for a single chat.
Reasons to be careful
- Client confidentiality. Inside a Project, Claude uses that Project’s memory plus account memory from chats outside Projects. If people discuss client details in ordinary chats, those can surface inside other client Projects. The fix is to turn off “Use account memory” on client Projects.
- Regulated data. Memory does not start on in HIPAA-enabled organizations, on Claude’s government platforms or for Claude for Teachers. Even with memory on, some information is never saved: government ID numbers, criminal history, financial account numbers and immigration status.
- Retention. Memory entries are included in standard data exports, and turning memory off does not remove them. With the new unified experience, a custom retention period for chats also applies to memory, except Project memory.
- Visibility. Owners cannot see what Claude remembers about members. That protects privacy but means nobody can check centrally what Claude has learned.
A sensible setup
- Leave memory on at the organization level.
- Make one Project per client or matter, and turn off “Use account memory” on each.
- Agree as a team that client details go in the client’s Project, not in loose chats.
- Tell people how to use incognito (the ghost icon) for anything that should leave no trace in memory or history.
- On Enterprise, check that audit logging covers the organization switch.
The misunderstanding: team memory
Switching memory on for the organization does not create a team memory. Each member’s memory is built from that member’s own chats, and Anthropic describes no way to pass it on. When the person who taught Claude your proposal format leaves, that knowledge leaves with them. Shared Projects are the closest thing to shared context, and they hold only what someone uploaded or wrote in the instructions. More in does Claude have memory and how to turn off, reset or delete Claude memory.
Where Bombos fits
Claude memory is a good personal feature; the open question for a team is where the shared part lives. Bombos is a plugin that gives every AI tool your team uses, Claude and Claude Code as well as ChatGPT, Copilot, Cursor and your own agents, one shared memory with team knowledge and rules learned from corrections, traceable so you see what an answer rests on, in the cloud or on your own server. One person can try it first for their own agents.
Related questions
Can an owner turn memory on for one person?
No. Owners manage the organization-wide setting and cannot turn memory on for individual users. Each member controls their own memory within what the organization allows.
If we turn memory off for the organization, is it deleted?
No. Account memory stops for everyone, but some projects keep using their own project memory. Existing entries are not deleted and remain subject to retention rules.
Are memory changes logged?
On Enterprise, audit logs record when owners change the organization-level memory setting. Individual memory edits are not logged.
Is memory available on HIPAA organizations?
Memory does not start on in HIPAA-enabled organizations, government platforms or Claude for Teachers, and the new memory experience is not available to organizations with HIPAA or public-sector agreements.
