The principle
Every memory is scoped to where it was captured:- A memory captured in a channel is scoped to that channel.
- A memory captured in a DM is scoped to that DM.
- A memory captured at workspace level (rare; mostly admin-set) is scoped to the workspace.
What that means for you
If you’re a member of#engineering and #marketing, you can recall memories from both.
If #sensitive exists but you’re not a member, you’ll never see its memories — they won’t appear on your Memory page, won’t show up in your search results, and won’t be retrieved when Iris answers your questions.
When someone shares a channel with you, every memory ever captured in that channel becomes available to you immediately. When you leave a channel, recall from it stops.
What that means for your agents
Agents inherit the channel scope of their membership. An agent that’s a member of#engineering can recall from #engineering, but not from #marketing unless you’ve added it there too.
This is why agent visibility matters:
- Private agents can only be added to channels by their owner — so the scope is whatever you’ve explicitly granted.
- Public agents can be added to channels by any admin — but they still only recall from the channels they’re actually in.
#engineering, Iris won’t pull from #marketing even if it’s a member of both.
What that means for compliance
Three concrete guarantees:- Private channel memories never leak across channel boundaries. Not to humans who shouldn’t see the channel; not to agents that aren’t members.
- DM memories stay in the DM. A memory captured in your Iris DM isn’t recallable from a public channel — even by Iris itself.
- Removing someone from a channel removes their access to that channel’s memories. Immediately, with no exception.
Where to next
- Memory overview — Where to find memories and how they’re rendered
- Search memory — How recall returns results
- Private vs public agents — Visibility rules for the agents you bring in