> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getunblocked.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Shared Memories
> How Unblocked learns from your team's corrections and applies them to everyone's answers
Shared Memories let Unblocked learn from your team. When someone corrects one of Unblocked's
answers in a shared conversation, Unblocked saves what it got wrong — and everyone's future
answers benefit from the correction.
This is the knowledge that usually never makes it into documentation: the deploy process that
changed last quarter, the service that was renamed, the convention everyone follows but nobody
wrote down. The first person to notice a wrong answer fixes it once, for the whole team.
Where [Personal Memories](/unblocked-chat/personal-memories) remember preferences about *you* and
shape how you're answered, Shared Memories remember facts about your *organization* and shape what
everyone is told.
## How it works
In a shared conversation, tell Unblocked what it got wrong — either by replying in the thread
("that's out of date, we moved off Jenkins last quarter") or by giving the answer a thumbs-down
with a correction.
Unblocked looks at your connected sources to confirm a correction. Corrections
it can verify are saved as facts. Corrections it can't check — because the
evidence lives somewhere it can't reach, like a meeting — are remembered with
an attribution, so future answers know who said it.
When anyone in your organization asks something the note is relevant to, Unblocked applies it and
links back to the conversation the correction came from, so readers can see where the knowledge
originated.
Unblocked treats its memories as strong hints, not as the last word. When a memory and your
connected sources disagree, Unblocked weighs both and goes with whichever is better supported — so a
memory that has gone out of date gets caught rather than repeated forever.
### Access control
With [Data Shield](/team-settings/data-shield) enabled, Unblocked won't search access-controlled
sources to check a correction, since that could pull restricted material into a note the whole team
can read. The note records what the correction says, attributed to the person who made it, rather
than as verified fact — and because it's built only from a conversation your organization can
already read, it exposes nothing new.
### Where it works
Shared Memories are learned **only in conversations your whole organization can already read** — a
public Slack or Microsoft Teams channel, or a shared conversation in the web app.
Nothing said in a private space becomes shared knowledge. Direct messages,
private channels, and group chats never produce Shared Memories, even when the
correction itself would be useful to everyone.
Once saved, a shared memory applies **everywhere Unblocked answers** — the web app, the Mac app,
Slack, Microsoft Teams, and the CLI.
## What Unblocked remembers
* **Processes that changed but the docs didn't.** "Staging deploys through Jenkins now, not GitHub
Actions." The runbook still says the old thing and will for months. One correction stops Unblocked
repeating it.
* **Conventions nobody wrote down.** "We use trunk-based development — don't suggest release
branches." The kind of rule every team member knows and every new hire learns the hard way.
* **Migrations in flight.** "The legacy billing API is frozen; new endpoints go in billing-v2."
During a long migration the codebase honestly looks ambiguous, and a memory tells Unblocked which
half is the future.
* **Words that mean different things in different places.** "In the Acme product, a *workspace* is a
billing container, not a UI panel." Overloaded terms are a common cause of confidently wrong
answers. Unblocked remembers where a correction applies — a product, a repo, an audience — so
settling the meaning in one place doesn't rewrite answers everywhere else.
* **Rules for customer-facing answers.** "When answering in the support channel, don't name internal
services." A correction can capture how to answer for a particular audience, not just what's true.
### What doesn't become a shared memory
* **Anything about a specific person.** "Alex prefers short answers" is a personal preference, not
organizational knowledge, and Unblocked won't turn one into a rule applied to everyone. Those
belong to [Personal Memories](/unblocked-chat/personal-memories).
* **Secrets and credentials.** Unblocked never copies tokens, keys, or personal data into a memory.
If a correction depends on such material, the note points at where it lives instead.
* **Thread-specific chatter.** A correction that only makes sense for one question is not saved.
## Setup and management
### Turn Shared Memories on or off
Shared Memories are managed by your team's admins.
In the Unblocked web app, open **Settings** and find the **Answers** section.
Find the **Shared Memories** setting and turn it on to start learning from your team's
corrections, or off to stop.
Turning Shared Memories off stops Unblocked from learning new memories and from applying existing
ones. Memories already saved are kept, not deleted — turn the setting back on and they apply again.
### Managing shared memories
You manage shared memories the same way you create them — by telling Unblocked in a shared channel
or conversation. For example:
* **See what it knows:** "What do you remember about how we deploy?"
* **Correct a memory:** "That's changed. We deploy from the release branch now."
* **Narrow one:** "That's only true for the payments service."
* **Remove one:** "Forget what you know about the legacy billing API."
Because these memories are shared, anyone in your organization can correct them, and every change
applies to everyone. Unblocked keeps the set small and sharp on purpose: a new correction that
covers the same ground as an existing note updates that note rather than piling up near-duplicates.