How it works
1
Someone corrects an answer
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.
2
Unblocked remembers the 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.
3
Everyone's answers improve
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.
Access control
With 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.
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.
- 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.1
Open your team settings
In the Unblocked web app, open Settings and find the Answers section.
2
Toggle Shared Memories
Find the Shared Memories setting and turn it on to start learning from your team’s
corrections, or off to stop.
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.”