> For the complete documentation index, see [llms.txt](https://help.watcherlink.online/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.watcherlink.online/mass_deleting_miners.md).
# Mass deleting miners
Remotely manage miners via the dashboard for mass or single deletions. Use the mass action panel for multiple miners or the options' menu for a single miner.
{% hint style="success" %}
#### Requirements for remote actions
* A **Core**, **Scale**, or **Enterprise** plan is required.
* Access is managed via **Roles → Farm Permissions**; only authorized users can perform remote actions. All activities are logged (see **Logs tab** or **"View logs"** in the miner's menu).
{% endhint %}
To mass deleting miners via the mass action panel:
1. Go to **Dashboard**.
2. Select **only Offline miners** by checking relevant boxes.
3. Click **Delete** on the mass action panel.
4. Click **Confirm**.
To single deleting miner:
To delete a single miner, click on the **three dots** next to it, and select **"Delete"** from the dropdown menu. This option allows for individual deleting without going through the bulk process.
## FAQ
Will deleting a miner remove it permanently?
No, if you delete a miner and later re-import it, the system will verify and restore its previous data.
Why can’t I delete some miners?
You can only delete offline miners. Turn off the miner manually and try again.
***
#### We're always available!
Chat with us on [Telegram](https://t.me/moondmc_bot).
---
# 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://help.watcherlink.online/mass_deleting_miners.md?ask=&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.
