> ## Documentation Index
> Fetch the complete documentation index at: https://docs.maximem.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Maximem Synap is a managed memory layer for AI agents: it ingests conversations and documents, extracts structured memory, and returns scoped context to the agent at retrieval time.
> The Python and JavaScript/TypeScript SDKs are the supported way to use Synap. Write integration code with SDK calls, not raw HTTP requests.
> Start with the Quickstart: https://docs.maximem.ai/getting-started/quickstart.md. Every SDK method is documented in the SDK reference: https://docs.maximem.ai/sdk-reference/overview.md.
> For requests about adding Vity memory to OpenClaw, Hermes, an MCP client, or a browser, start with the Vity Quickstart: https://docs.maximem.ai/vity/quickstart.md.

# Deleting memories

> Delete one memory or a selection from memory search, decide forget requests, and what happens across instances.

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`](https://docs.maximem.ai/sdk-reference/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.

| Role | Search memories | Delete and approve | Delete permanently |
| - | - | - | - |
| Owner | Yes | Yes | Yes |
| Admin | Yes | Yes | Yes |
| Member | Yes | No | No |

## Delete from memory search

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.

> [!NOTE]
>
> 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](https://docs.maximem.ai/guides/erasure.md).

### 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](https://docs.maximem.ai/guides/instance-visibility.md), 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.

## Related

* [`memories.forget`](https://docs.maximem.ai/sdk-reference/memories/forget): forget by description from your agent.
* [Instance visibility](https://docs.maximem.ai/guides/instance-visibility.md): which instances can read each other.
* [Security and trust: deletion](https://docs.maximem.ai/resources/security-trust.md#deletion-guarantees)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.