Skip to main content
You can remove memories from the dashboard in two ways:
  • From memory search, when you find a memory that is wrong or should not be kept.
  • From the deletion requests queue, when your agent asked to forget something with memories.forget and a person has to decide.

​
Who can delete

Deleting needs the delete permission. Owners and Admins have it; Members do not. A Member can still read memory search and the deletion requests queue.
  1. Open Memories and pick the instance you are working in, or All instances.
  2. Delete one memory: open it and choose Delete. Delete several: tick their rows (or tick the header box to select the whole page), then choose Delete selected.
  3. Confirm.
By default the delete is not permanent: the memory stops being served to your agents, and its record is kept, marked deleted. Tick Delete permanently to remove it now, along with the text Synap’s change history kept of it. A permanent delete cannot be undone.
A delete covers what Synap stored as that memory. It does not change the documents or conversations you sent. To remove everything about one person, see Erasing a person.

​
Memories in other instances

Memory search can list memories from every instance of your account. A delete never reaches into another instance without you saying so:
  • With one instance picked, if your selection includes memories from other instances, nothing is deleted yet. The dashboard names those instances and asks: delete only in this instance, or delete across instances.
  • With All instances picked, Delete stays disabled until you tick the box that confirms deleting in whichever instance holds each memory.

​
Decide forget requests

When your agent calls memories.forget in preview mode, the matches wait in Requests → Deletion requests. Approve to delete exactly the memories listed, or reject to delete nothing. Approving is not permanent either: it hides the memories the same way. Each request shows the instance it was asked in. Every approval is recorded in the memory’s change history, and the request keeps who decided and when.

​
Requests queued for an isolated instance

If your instances are isolated, a forget made in one instance changes only the instances that instance can read. When it also matches memories in an instance it cannot read, nothing changes there. Instead, a request is filed for that instance, marked Owned by that instance:
  • The agent that asked is not shown those memories and is not told the request exists.
  • A person with the delete permission decides. Approving deletes the memories in the owning instance.
The same holds for the follow-up searches Synap runs after a direct forget that found nothing yet: they never delete in an instance the asking one cannot read; they file a request instead.