> For the complete documentation index, see [llms.txt](https://docs.appfarm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appfarm.io/library/ui-components/drawable-canvas-1.md).

# Speed dial

The UI component **Speed Dial** is an extension of the Floating Action Button component. This reveals additional action buttons when clicked, allowing multiple buttons with multiple purposes to be placed in an efficient way on the screen.

Each Action Button defined within the Speed Dial can be defined an *On Click* action, as with all other Button types.

{% hint style="info" %}
An example setup of the **Speed Dial** component is showcased in our [Showroom](https://showroom.appfarm.app/ui-components/iconbutton)! You may view a demo, as well as access the setup in Appfarm Create. If you do not have access, you may register [here](https://showroom.appfarm.app/sign-up).
{% endhint %}

## Settings

Here are some properties in Appfarm Create which are configurable for the **Speed Dial:**

### **Icon / Open Icon**

Icons can be connected to the component. An Open Icon can also be configured, if it is desired that the Icon will be different depending on if the Speed Dial component is opened or closed. The default value for both is a + icon.

### Direction

The direction that the Speed Dial component expands in. Can be *Up*, *Down*, *Left* or *Right*.

### Tooltip Open

Each Action Button can be configured to have a tooltip value, and with this setting enabled these tooltips are always visible when the Speed Dial component is open.

### Tooltip Placement

Which side of the Action Buttons that the tooltip values appear. If Tooltip Open is enabled, then this value defaults to Left. Can be set to *Left*, *Right*, *Top* or *Bottom*.

### Action Buttons

Each Action Button can be assigned an Icon, a Visibility Condition, a tooltip, and bound to an On Click action.


---

# 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.appfarm.io/library/ui-components/drawable-canvas-1.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.