> For the complete documentation index, see [llms.txt](https://docs.senpiper.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.senpiper.com/workflow-builder/how-to-create-workflows/define-workflow-step/configuring-button-settings-for-a-step-of-the-workflow/basic-details.md).
# Basic details
This section contains the formatting and visibility settings of a button.
Basic Details
| **Field** | **Description** |
| ------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| Name of the button\* | The name for the button |
| Choose color | The color for the button |
| Select button type | The type of the button |
| Select button size | The size of the button |
| Select action that happens on button click | Select an event that should occur on clicking the button |
| Users who will see this button | Select the users for whom this button is to be visible |
| Users who have started the following steps | Select the initiator of the next step (Applicable when the next step is to be assigned to a user/role assigned to a previous step) |
| Enable users to provide remarks at click of this button | Turn on the toggle switch if you want to allow the assignees to enter remarks on clicking the button |
So let's say we want to add an **Approve** button for the **Manager** at step 2. The **Basic Details** for this button would be:
As you can see, there are 4 important details for the **Approve** button.
* It is self-explanatory that we have selected the **Name of the button** as **Approve**
* On clicking the **Approve** button, the flow will continue and the next step will be assigned to the **Department Head** in the next step. So for **Select action that happens on button click**, we have selected **Continue workflow** so as to move the flow to the next step.
* The **Approve** button is to be assigned to the **Manager**. The role **Manager** belongs to **Company defined role** category. Hence, for **Users who will see this button**, we have selected **Company defined role** and for **Select roles to whom this button will be shown**, we have selected **Manager**.
---
# 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.senpiper.com/workflow-builder/how-to-create-workflows/define-workflow-step/configuring-button-settings-for-a-step-of-the-workflow/basic-details.md?ask=&goal=
```
`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.