> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hiveku.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Buttons and Forms on Dashboards

> Act on what a dashboard shows: buttons on rows, buttons that run a workflow, and forms that add rows

A dashboard can do more than show numbers. Buttons on a list's rows act on the record, a button can run one of your workflows, and a form can add a row to one of your [Your data](/dashboards/your-data) tables.

Every button does exactly what the same button does on its department's page, with the same permission checks, notifications and workflow triggers. Someone whose role can't do it there can't do it from a dashboard either.

## Buttons on each row

A **List** of records, such as leads, tickets, tasks or deals, can carry buttons on each row. Open the widget's settings and choose them under **Buttons on each row**. The ones offered depend on the data:

| Data | Button | What it does |
| - | - | - |
| Form leads | **Mark read** | Marks the lead read. It stays in the inbox; nothing is sent. |
| Form leads | **Mark answered** | Marks the lead answered. It stays in the inbox; nothing is sent. |
| Form leads | **Archive** | Moves the lead out of the inbox to Archived, where the Forms tab still shows it. Nothing is sent. |
| Form leads (spam) | **Not spam** | Moves the lead back to the inbox. If nobody was told about it yet, the owner is emailed, a CRM contact is made and the form's workflow runs, once, like any new lead. |
| Tickets | **Assign to me** | Gives you the ticket, as the inbox does: the ticket's workflows run, and on a website chat handed to the team the visitor is told a teammate joined. |
| Tickets | **Resolve** | Marks the ticket resolved, as the inbox does: the ticket's workflows run, and a satisfaction survey goes out if the account sends them. |
| Tasks | **Mark done** | Marks the task done, with its open subtasks, as the PM board does: the task's workflows run and the person it is assigned to is told. |
| Deals | **Move stage** | Moves the deal to the stage you choose, as a drag on the CRM deal board does. Its stage-change workflows run. When the stage has a lifecycle stage and lifecycle sync is on, the deal's contacts take it, which starts their lifecycle workflows. Contacts are taken out of sales sequences set to stop on those changes. A won or lost stage closes the deal, and its won or lost workflows run too. |

A button whose action sends something or starts workflows **asks before it runs**, and says exactly what will happen. When it has run, the widget's numbers update.

## Run a workflow

Anything you can build as a workflow can become a button on a dashboard, such as "Send this week's report to the client" or "Create an onboarding project".

<Steps>
  <Step title="Make the workflow">
    In **Workflows**, make a workflow that starts with the **Dashboard Button** trigger. Its settings are the **Button label** (what the button says) and **Fields to ask for**: up to 12 fields the person fills in before pressing, each with a **Name**, a **Kind** (text, long text, number, date, yes/no or a choice) and whether it **Must be filled in**. Later steps read each field as `{{trigger.fields.<name>}}`, as the field's settings show. Add the steps, then switch the workflow on.
  </Step>

  <Step title="Add the button">
    On the dashboard, press **Customize**, then **Add widget > Build your own**. Under **A button that runs a workflow**, each workflow that starts from a Dashboard button is listed by its name, with **Add**.
  </Step>

  <Step title="Check what it does">
    The button is added switched on. Its settings say exactly what pressing it does (the kinds of steps the workflow has) and can switch it off.
  </Step>
</Steps>

Only people who can run workflows can switch a button on or press it. If a step in the workflow moves money, pressing the button also needs that step's own permission. Each press is recorded in the account's activity log with who pressed it, and the run shows in the workflow's history as started from the dashboard.

## Forms

A **Form** adds a row to one of your Your data tables. Its fields are the table's own columns, and a submit is checked exactly as **Add row** on the table is. Find forms on the library's **Your data** tab, under each table.

## Tallies

A **Tally** widget shows a count with an **Add 1** button, for the people the tally lets add. See [Tallies](/dashboards/your-data#tallies).

## Buttons added by AI agents

An AI agent can put a button or a form on a dashboard, but it stays **off** until a person who is allowed to do what it does checks it and switches it on in **Customize**. AI agents never press dashboard buttons.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.