Overview
Memory helps users work more efficiently by reducing repetition and providing continuity across conversations. The feature includes:- Saved memories: Explicit information users tell the Assistant to remember, such as role, preferences, or project context.
- Extracted memories: Insights automatically mined from user chat sessions and work activity, including response preferences, roles and responsibilities, and active projects.
Configure memory settings
You can restrict memories for your organization by disabling chat history. Doing so will prevent the Assistant from extracting memories from user chat sessions. Users will still be able to add and delete their own memories through chat commands. For more information on configuring chat history, see Chat History.Retention policies
Memory retention works as follows:| Memory type | Retention |
|---|---|
| Extracted memories | Persisted for 30 days and regenerated weekly from user activity data. |
| Saved memories | Persisted until the user deletes them. |
User controls
Users have individual controls over their memory settings:- View and delete memories: Users can view their memories organized by category and delete individual entries or all memories in a category.
- Runtime controls: Users can control memory usage during a conversation using natural language commands.
Privacy and security
Memory is designed with privacy and security as core principles:- User-level isolation: Memories are stored at the individual user level. There is no cross-user memory sharing or data leakage.
- No document access: Memory stores facts and preferences, not document content. Memory does not grant users access to documents they cannot otherwise view.
- Sensitive data handling: The system does not extract sensitive personal attributes. Memory extraction is scoped to work context and preferences.
Compliance considerations
When evaluating memory for your organization:- Data residency: Memory data is stored in accordance with your organization’s data residency configuration.
- User deletion: When a user is deleted from your organization, their memory data is also deleted.
- Audit logs: Memory operations are logged and available through your standard audit log channels.
Known limitations
Administrators and users should be aware of the following limitations:- Possible duplication: Users may see duplicate entries in memory views. These are deduplicated during the weekly update cycle.
- Deleted memories may reappear: Extracted memories may be regenerated from activity data after deletion during the weekly regeneration cycle.
- Fast Mode: Memories cannot be created or referenced when users are using Fast Mode.
- Memory edits: Users can add and delete memories through chat commands; the Settings UI supports viewing and deletion only.
- Weekly updates: Extracted memories are regenerated weekly. Changes to user context may not appear immediately.