> For the complete documentation index, see [llms.txt](https://docs.roomle.com/rubens/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roomle.com/rubens/rubens-products/rubens-configurator/customisation/enable-disable-buttons.md).
# Enable / Disable buttons
In our user interface it is possible to nearly hide every button which is not dynamically generated. This means you can hide all buttons on the left side and also all buttons in the bottom bar.
Hiding buttons is possible within the init data or in the tenant settings. You have to override the `buttons` object with the right key of the button. Hiding buttons can be useful when you either want to implement you own button in html or when you just do not want that a user has a certain functionality.
You can look up the complete list of buttons in the UI\_BUTTONS enum which you can [find here](/rubens/rubens-products/rubens-products-reference/enums/types.ui_button.md)**.**
The call-to-action button in the bottom bar (add to cart) is controlled by `requestproduct` in the Rubens Configurator and by `requestplan` in the Room Designer:
```javascript
// Rubens Configurator
{...options, buttons: {requestproduct: false}}
// Room Designer
{...options, buttons: {requestplan: false}}
```
Here is a short example where the parts list button on the left is side is hidden.
```javascript
const configurator = await RoomleConfiguratorApi.createConfigurator(
'demoConfigurator',
document.getElementById('configurator-container'),
{...options, buttons: {partlist: false}},
);
```
---
# 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.roomle.com/rubens/rubens-products/rubens-configurator/customisation/enable-disable-buttons.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.
.svg?alt=media)