> For the complete documentation index, see [llms.txt](https://docs.besmart.software/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.besmart.software/getting-started/faq/how-to-remove-a-tool-from-the-revit-ribbon.md).

# How to remove a tool from the Revit ribbon

### Removing tools from the Revit ribbon

If you want to delete some tools that you don't use, follow these steps

1. Open the ARKANCE Dock, and go to 'My tools'
2. Click the tool you want to remove:

![](/files/WFlrWPrv8onFY0qcD3Yw)

3. Click the information mark:

![](/files/YyjwqOmTFsfelYr9nCd8)

4. Click 'Uninstall':

![](/files/xeOtuZM5hOBTmRwaRP8g)

5. Once all unnecessary tools are uninstalled, restart Revit.

{% hint style="info" %}
If you wish to **delete all tools** **and the** ARKANCE **Dock**, navigate to Control Panel\Programs\Programs and Features to uninstall "ARKANCE Dock"
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.besmart.software/getting-started/faq/how-to-remove-a-tool-from-the-revit-ribbon.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.