> 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/highlighting-in-the-configurator.md). # Highlighting in the configurator When using the Rubens Configurator on a desktop, we provide highlighting in the UI which is shown every time the user hovers over components of a configuration. This highlighting is a white border that is displayed around the affected component.

Highlighting behaviour in configurator

However, you can define an individual highlighting behaviour for your configurators. There are three different states for the highlighting behaviour in the configurator which you can set in your configurator settings. You can use the URL parameter highlighting or set the behaviour in [the tenant settings](/rubens/rubens-admin/rubens-admin-help/administration.md#tenant-settings) in Rubens Admin. Here are the possible options available: `smart`: Highlighting is enabled if there are add-ons available for the configurator. If there are no addons available, the highlighting is disabled. This is the default behaviour. `off`: Highlighting is disabled for all cases regardless of addons being available. `always`: Highlighting is enabled for all cases regardless of addons being available. --- # 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/highlighting-in-the-configurator.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.