> ## Documentation Index > Fetch the complete documentation index at: https://atmet.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Workspace Memory: Persist Context Across Every Agent Session > Store preferences, approval rules, CRM notes, and team context in workspace memory so your Atmet agent never needs to be briefed twice. Workspace memory is a persistent knowledge store attached to your Atmet workspace. Every agent in your workspace — across all chats and automated workflows — has continuous access to this shared context. Instead of repeating your preferences, rules, and business-specific details at the start of every conversation, you store them once in memory and the agent applies them automatically from that point forward. ## What you can store in memory Workspace memory is flexible. You can store any context that the agent should consistently know and act on: Define when the agent must pause and request human sign-off before taking an action — for example, before sending any email to a customer, or before updating a financial record. Store context about key accounts, deal history, or customer relationships so the agent can reference it when drafting outreach or preparing reports. Attach documents — brand guidelines, email templates, pricing sheets — that the agent should consult when performing relevant tasks. Record standing instructions like tone of voice, formatting preferences, preferred tools, or internal escalation procedures. Set defaults for specific integrations — for example, which Gmail label to use for processed invoices, or which Slack channel receives weekly reports. ## How memories are created The agent creates memories in two ways: **Automatically** — As you work in chat, the agent picks up on information you provide and offers to remember it for future sessions. For example, if you tell the agent *"always CC our legal team on any contract emails,"* it will propose saving that as a workspace memory. **Explicitly** — You can instruct the agent to save a specific piece of context at any time: * *"Remember that our finance team is the approver for all invoices over \$5,000."* * *"Save this email template to workspace memory for future use."* * *"Remember that we use HubSpot's 'Enterprise' pipeline for all accounts over 500 employees."* The agent confirms what it is about to store before saving, so you stay in control of what goes into memory. Be specific when storing memories. Instead of *"remember our approval rules,"* try *"require approval before sending any email to a customer contact in HubSpot."* The more precise the instruction, the more reliably the agent applies it. ## How agents use memory Every time you start a chat or a workflow executes, the agent automatically loads your workspace memory as background context. This means: * You don't need to repeat standing instructions in every conversation. * Workflows you built last month still follow the rules you set — even if team members have changed. * New teammates benefit immediately from the context your team has built up over time. The agent references memory silently unless a memory item directly affects a decision. When it does — for example, when an approval rule applies to a workflow being designed — it will tell you which memory item it is acting on. ## Viewing and managing memories To review your workspace memory, open the **Memory** section in the sidebar. You will see a list of all active memory items, each showing: * The memory content * When it was created and by whom * Which category it belongs to (approval rule, preference, file reference, etc.) Scroll through the memory list to audit what the agent currently knows. Look for outdated items — old team structures, deprecated workflows, or rules that no longer apply. Click any memory item to open an edit view. Update the text directly and save. The change takes effect immediately in all subsequent agent interactions. Click the three-dot menu on any memory item and select **Delete**. The agent will no longer reference this item. Deleting a memory does not affect past workflow runs that already applied it. Click **New Memory** to open a creation form. Write the context you want to store, assign it a category, and save it. ## Practical examples Store a rule like: *"Always require approval from the account manager before sending a renewal offer to any customer."* When the agent builds a workflow that involves sending renewal communications, it will surface this rule and ask for your confirmation before activating that action. Store context like: *"Acme Corp has a history of delayed payments. Flag their invoices for manual review before sending."* Whenever a support or finance workflow touches an Acme Corp record, the agent surfaces this note and adjusts its behavior accordingly. Store a delegation rule: *"The finance team ([finance@yourcompany.com](mailto:finance@yourcompany.com)) is the approver for all outbound invoices and payment-related emails."* This memory wires approval routing automatically into workflow design, so no one has to manually specify the approver every time a payment workflow is built. ## Privacy and access Workspace memory is scoped to your workspace. Members of your workspace can view and edit shared memory. Memories are not shared across separate workspaces, and they are not accessible to other customers. Be thoughtful about what you store in workspace memory. Avoid storing credentials, personal data, or sensitive customer information. Use integration-level authentication and your connected apps' access controls to handle sensitive data securely.