eBPF Continuous Profiling released

Last updated:

Control Memory Sharing and Access

Understand who owns a memory, review sharing suggestions, share knowledge with your organization, and stop sharing it without deleting it.

A memory belongs to you or to an automation. Sharing your memory lets other Agent0 sessions in the same organization and dataset use it. It does not make the memory available in other datasets or organizations.

Understand ownership and access

Memories Agent0 saves while working for you in Dash0, Slack, Linear, or MCP belong to you. A memory saved during an automation run belongs to the automation, not the person who started the run.

MemoryWho can use itWho can change it
Your unshared memoryAgent0 sessions working for you in its datasetYou can edit, share, or delete it.
Your shared memoryAgent0 sessions in the same organization and dataset, including automation runsYou can edit it or stop sharing it. You and organization admins can delete it.
A memory shared with youAgent0 sessions working for you in its datasetIts owner can edit it or stop sharing it. Its owner and organization admins can delete it.
An automation's memoryRuns of that automation in its datasetPeople with Edit access to the automation can delete it. It cannot be manually edited or shared.

Sharing does not grant dataset access. Other users need access to the memory's dataset to review it.

Review visibility

On Knowledge → Memories, the Visibility filter separates your unshared memories, memories you shared with all users, and memories others shared with you.

A sharing suggestion is still private. In a thread's Memories tab, it appears under Suggested for sharing until you approve it. Choosing Don't share keeps it under Not shared and declines that suggestion.

Share or stop sharing a memory

Open one of your memories on the Memories page. The sharing actions are in its details and in the menu on its card. You can also use them in a thread's Memories tab.

  • Share: Make the memory available to other sessions in its dataset.
  • Don't share: Decline Agent0's suggestion to share it. The memory remains yours to use.
  • Stop sharing: Remove other users' access without deleting your memory. It becomes Not shared and remains available in your own sessions.

Only the owner can change sharing. If you want someone else's memory removed from shared use, ask its owner to stop sharing it, or ask an organization admin to delete it.

If a memory changed since you opened it, Dash0 refreshes it rather than sharing text you have not reviewed. Read the current content and choose Share again if you still want to share it.

Auto-sharing

Auto-share memories is a personal setting under Settings → Agent0 → Your preferences. It is on by default. See Auto-share Memories for the setting.

With auto-sharing on, Agent0 can share memories it saves while working for you in Dash0, including the side panel, when it judges the content useful to your organization and free of anything private. This does not mean every memory is shared. Memories saved in Slack, Linear, or MCP still require you to share them. Automation-owned memories cannot be shared.

Turning auto-sharing off prevents automatic sharing of new memories. It does not stop sharing memories you already shared. Use Stop sharing on those memories individually.

When a shared memory changes

There are two different ways a shared memory can change:

  • You edit it in the UI: The edit keeps the memory's existing visibility. Other sessions read your updated content without a separate sharing step.
  • Agent0 saves a correction: Agent0 creates a replacement. If the replacement is shared automatically, it replaces the previous shared version. If it waits for your approval under Suggested for sharing, other sessions keep using the previous shared version until you share the correction. When Agent0 cannot share the correction, the previous shared version stays available to other sessions.

Asking Agent0 to make a memory private is not the same as saving another copy. The shared original would still be available. Use Stop sharing on the original memory instead.

Further Reading