The five memory layers
Not all context belongs everywhere. WorkLLM organizes memory into five layers, so the right information reaches the right people, automatically.Thread memory
Thread memory
Every conversation remembers what you’ve already said, so you never repeat yourself mid-chat. Context stays alive for the full length of a conversation, automatically, with nothing to set up.
Context memory
Context memory
Every folder in a project carries its own memory. Threads inside that folder automatically know what’s relevant without you explaining it. This layer is scoped to the folder, so unrelated work never bleeds in, keeping client folders, campaigns, and features cleanly separated.
Project memory
Project memory
Everything inside a project shares the same memory layer, applying across all folders and threads automatically. It gives every part of an initiative one consistent foundation, no matter who’s working in it.
Personal memory
Personal memory
Your writing style and preferences travel with you across every project and folder in WorkLLM. AI adapts to how you write instead of the other way around, so outputs already sound like you.
Organization memory
Organization memory
Company-wide knowledge available to everyone, everywhere, one source of truth every conversation can draw from. It’s available in every project, folder, and thread with no exceptions, keeping product details, brand guidelines, and policies consistent across the whole team.
How memory flows
A thread inside a folder has access to that folder’s context memory, its project’s memory, and your company’s organization memory, all at once. You never have to manually connect the dots. WorkLLM does it for you.
FAQs
What's the difference between project memory and context memory?
What's the difference between project memory and context memory?
Project memory applies to everything inside a project, every folder and every thread. Context memory is scoped to a specific folder, so only threads inside that folder use it. Project memory is the broader, parent layer; context memory is the more specific, child layer.
Does organization memory apply across every project automatically?
Does organization memory apply across every project automatically?
Yes. Organization memory is available everywhere in WorkLLM, regardless of which project, folder, or thread you’re working in. It’s meant for company-wide knowledge that should always be available.
Who can add something to organization memory?
Who can add something to organization memory?
Anyone on the team can suggest content for organization memory by adding files, links, or saving an AI answer. A memory owner or admin then reviews and approves it before it becomes visible to everyone else.
Do we need to connect our entire Google Drive or Slack to use org memory?
Do we need to connect our entire Google Drive or Slack to use org memory?
No. You only add what you actually want AI to know: files, folders, links, or templates. There’s no need to authenticate and share access to your entire workspace just to get a few documents into memory.
What happens if a teammate doesn't have access to a file I added?
What happens if a teammate doesn't have access to a file I added?
Nothing breaks. Once something is added to org memory, it’s available to everyone with workspace access, regardless of whether they have permissions on the original file or app it came from. This avoids the common problem where an AI agent fails because the person using it doesn’t have the right file permissions.
Can organization memory be deleted or corrected if something's outdated?
Can organization memory be deleted or corrected if something's outdated?
Yes. Organization memory owners and admins can edit, replace, or delete anything in organization memory at any time, so your company’s knowledge stays accurate as things change.
Next steps
Request a Demo
Talk to the WorkLLM team and see organization memory set up around your workflows.
Contact Us
Have a question or want to talk to the team? Reach out and we’ll get back to you.