> 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/floating-action-button.md). # Floating action button The **Floating action button** UI component is positioned above other page content and triggers an action. It shares similarities with the [Button](/library/ui-components/button.md) and [Icon button](/library/ui-components/icon-button.md) components. A Floating action button can have an icon and optional text and is more visually emphasized than other button types. It is recommended to use a Floating action button for the main action on a page/view. A common use case is to position the button in the bottom corner of the screen, for example if you have a table listing all active users, a Floating action button can be placed under the table which runs an action to add a new user to the app. As with all buttons, the *On Click* event handler can be used to connect the component to an action, and every time a user clicks the button, the action will be triggered. {% hint style="info" %} You can see an example setup of the **Floating action button** in the UI Components app in our [Showroom](https://showroom.appfarm.app/ui-components/floatingactionbutton). You can try the component, as well as access the setup in Appfarm Create. If you do not have access, you can register [here](https://showroom.appfarm.app/sign-up). {% endhint %} ## Settings Here are some properties in Appfarm Create which are configurable for a Floating action button: ### Icon Icons can be connected to the button. These can make the button more intuitive, by using symbols instead of words. ### Extended With this property enabled, you can add an optional label to the button. ### Conditional Properties If the button's appearance should differ depending on a condition which can change over time, then using Conditional Properties is recommended. The properties, and conditions for when they should override the given default, are defined in this section. ### Event Handlers Actions can be configured here, and these are run each time the button is clicked. --- # 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/floating-action-button.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.