> For the complete documentation index, see [llms.txt](https://docs.ezra360.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ezra360.com/overview/components-overview/action-buttons.md).

# Action Buttons

The action buttons are clickable controls that allow users to perform specific actions or operations within the system. These buttons are typically placed at the top of a form or within the ribbon, providing easy access to frequently used functionalities and commands.

Action buttons in Ezra are context-sensitive, meaning they change based on the entity type or the specific form being viewed. Different entities and forms may have different action buttons available, depending on the actions that are relevant to that particular context. Your security role also determine your buttons accessibility.\ <mark style="color:orange;">**#1**</mark> Shows action buttons.

<figure><img src="/files/o5QmuDeAD8fXTXv6GzGW" alt=""><figcaption><p><mark style="color:red;">Click image to view full screen</mark></p></figcaption></figure>

These action buttons provide a user-friendly and efficient way for users to perform various tasks within the system. They help streamline processes, enhance productivity, and enable users to work with data and records more effectively in Ezra360.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ezra360.com/overview/components-overview/action-buttons.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.