> For the complete documentation index, see [llms.txt](https://help.vectary.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.vectary.com/documentation/design-process/design-mode/interactive-elements.md).

# Interactive elements

These tools are used to create a 3D configurator.

<div align="left"><figure><img src="https://2973737105-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAXNLyKVZ2tvtyDr8sVES%2Fuploads%2F5po494yfsspcTZQx7zCR%2Fimage.png?alt=media&amp;token=9e2b061e-2939-40fc-8e21-4edaff03ff40" alt="" width="435"><figcaption></figcaption></figure></div>

<table><thead><tr><th width="165">Tool</th><th>Description</th></tr></thead><tbody><tr><td><a data-mention href="/documentation/3d-configurator/variants.md">Variants</a></td><td>This tool allows multiple objects/groups to be grouped together, with only one object visible at a time. This functionality is controlled using a radio button switch, enabling quick toggling between different variations within the group.</td></tr><tr><td><a data-mention href="/documentation/3d-configurator/floating-ui.md">Floating UI</a></td><td>This tool enables the integration of 2D UI elements within the 3D canvas, allowing for interactive overlays, labels, buttons, and other interface components</td></tr><tr><td><a data-mention href="/documentation/3d-configurator/hotspots.md">Hotspots</a></td><td>Hotspots are 2D UI elements that can be easily attached to any part of a 3D object or scene, functioning as triggers for various actions (displaying/hiding UI elements, triggering animations/interactions)</td></tr></tbody></table>


---

# 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.vectary.com/documentation/design-process/design-mode/interactive-elements.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.