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

<AgentInstructions>

## Submitting Feedback

If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback:

POST https://docs.omni.co/feedback

```json
{
  "path": "/administration/users/delete",
  "feedback": "Description of the issue"
}
```

Only submit feedback when you have something specific and actionable to report.

</AgentInstructions>

# Revoking user memberships

> Learn how to permanently revoke a user's membership in Omni, including what happens to their content and deliveries.

<Danger>
  Revoking user memberships is **not reversible**. Read this guide carefully before revoking a user's membership.
</Danger>

When a user's membership to your Omni instance is revoked, the following will occur:

* **Schedules created by the user will be deleted**. Unless transferred, the schedules must be re-created by another user to continue.
* [**Content in the user's Personal folder**](/content/navigate#personal) will be accessible to **Organization Admins** through search. Content outside of the user's Personal folder will not move.
* [API Keys](https://docs.omni.co/api/authentication)
  * [PATs](https://docs.omni.co/api/authentication#personal-access-tokens-pat) will be disabled.
  * [Organization API keys](https://docs.omni.co/api/authentication#organization-api-keys) will remain active. Requests to endpoints which require context about the user taking action may fail if the user is revoked.

Even if the user is re-added to your Omni instance with the same name and email, their previous history, permissions, content, etc. will not be associated with them. It will be as if they are a brand new user.

## Preparation checklist

Before you revoke a user's membership, complete the following:

<Steps>
  <Step title="Move any content in the user's Personal folder to a different location">
    Prior to being revoked, **Organization Admins** can impersonate the user to directly access this folder and move its content.

    You can also use the [**Analytics dashboard**](/administration/analytics) to identify the content the user owns, including documents in their personal folder.
  </Step>

  <Step title="Transfer or re-create any necessary schedules created by the user">
    To find the schedules created by the user, navigate to **Settings > Deliveries** and apply a filter for the user. You can navigate to the documents from this page and re-create the schedules to prevent disruptions.

    Alternatively, you can use the [transfer ownership API](/api/schedules/transfer-schedule-ownership) to programmatically transfer ownership.
  </Step>
</Steps>

After the user is removed, **Organization Admins** will still be able to find and access the user's **Personal** content using search or the [**Analytics dashboard**](/administration/analytics).

The **Settings > Deliveries** page will also list the user's schedules, but they will need to be re-created in order to run.