> For the complete documentation index, see [llms.txt](https://docs.omics.ai/products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omics.ai/products/publisher/settings/removing-an-admin.md).

# Removing an Administrator

[Publisher](https://github.com/DNAstack/dnastack-product-docs/blob/main/docs/publisher/settings/broken-reference/README.md) allows you to revoke administrative access when needed. Removing an administrator changes their status to "Disabled" while maintaining their access history.

## Disabling Administrator Access

1. Navigate to the Settings page through the left sidebar
2. Locate the administrator you want to remove:
   * Use the search bar to find them by name or email
   * Browse the full administrator list if preferred
3. Click the Actions menu next to their name
4. Select "Disable Access" from the dropdown
5. Confirm the action in the verification dialog

## What Happens After Removal

When you disable an administrator's access:

* They immediately lose ability to log into Publisher
* Their account status changes to "Disabled"
* Their previous actions remain in the audit history
* They can be reinstated later if needed

## Important Considerations

Before removing administrator access:

* Ensure critical administrative tasks are reassigned
* Consider temporarily disabling access for short-term changes
* Remember that disabled administrators can be reinstated through the same Settings page

{% hint style="info" %}
The administrator list maintains records of disabled accounts for audit purposes, but these users cannot access Publisher until explicitly re-enabled by another administrator.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.omics.ai/products/publisher/settings/removing-an-admin.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.