Skip to main content

Button Field

Turn records into action hubs, letting teams launch links, workflows, forms, and related resources with a single click

Written by Brian Dollen

A Button field puts a clickable button on a record. Think of a "Submit" button that lives in the record itself.

Here is the test: is there one action people take from this record again and again? If yes, you want a Button field.

Example: a Vendors table with a button called Request assessment. One click starts the automation that creates the assessment task and tells Security. Nobody has to find the automation.

The Request assessment button in a vendor record, a green pill under the field label.

The Request assessment button in a vendor record, a green pill under the field label.

Plan Availability

All plan types.

Permissions

Solution Managers and Workspace Administrators can create, modify and manage Button fields. Who can click depends on the action, see Permissions.

Platform

Web

Related Reading


Adding a Button Field Type

  1. In Grid View, select the + at the right end of the column headers. From an open record, select + Add new field to this Table at the bottom instead.

  2. Select Button. You can type to search the list of field types.

  3. Name the field. In this article it is Request assessment. A field name can hold up to 50 characters, and there is no restriction on the characters it can contain.

The field settings panel opens. It has two tabs: Settings and Help Text. The rest of this article takes them in that order. Save with Add Field (or Update Field on a field that already exists). The type is locked: a Button field cannot become another field type.

The field settings panel, Settings tab, with Display Format, Label, Color and Action set to Open Url with a static URL.

The field settings panel, Settings tab, with Display Format, Label, Color and Action set to Open Url with a static URL.


Settings

The Settings tab holds how the button looks and what it does. Top to bottom: Display Format, Label, Color and Action.

Display Format

How the button looks in a record and in views. The preview box shows the current choice; open it to switch.

  • Colored Pill (the default): the label on a colored button.

  • Text Only: the label in the chosen color, with no button around it.

Use Colored Pill for an action people should notice. Use Text Only for a quiet link, such as a button that opens a reference page.

Label

The text on the button. The default is "Click me"; change it. The label is separate from the field name, so the field can be called Request assessment and the button can read "Request assessment" or something shorter.

Tip: Start the label with a verb and say what happens: "Request assessment", "Open trust center", "Log incident". A person should know what the click does before they click.

Color

Pick one of 20 swatches, ten colors in a solid row and a pale row. The default is green. Use one color for buttons that start work and another for buttons that only open something.

Action

What the click does. The dropdown has four options: Open Url, Execute an Automation, Create a Record and Open a Form. The settings under it change with the choice. Add Field stays off until the action is complete, such as an automation paired or a form chosen.

Open Url

Opens a web address in a new browser tab. Two forms:

  • Static URL (the default): one address for every record, typed into the URL box.

  • URL Formula: an address built from the record's fields. Select Edit Formula to compose it in the formula builder, with fields, functions and text. An invalid formula shows "Invalid Syntax".

A button with no address stays unclickable. Any member who can view the record can click an Open Url button.

Tip: Use URL Formula when the address changes per record, such as each vendor's Trust Center page stored in a Link field. Use Static URL for a page everyone shares, such as the assessment procedure.

Execute an Automation

Runs an automation when the button is clicked. The panel shows "You need to create a paired Automation." with a + Create New Automation button. Create the automation from there; the button is its trigger. Request assessment uses this action: the automation creates the assessment task and notifies Security.

Only members with edit rights on the record can click. On a record page, SmartSuite saves the record before the automation runs, so it works on current values. With unsaved changes, a prompt offers Save and run the automation, Run without saving or Cancel. Required fields must be filled first.

Create a Record

Opens a new record in a table of your choice, with values already filled in. The record is created only when the person selects Save.

  • Table: where the new record goes. The default is the current table.

  • Default Values: select + Select Field, pick a field of that table from the list (grouped by the record layout's sections), and set its value in the Default Value popover. Each field you add gets a row with a trash icon to remove it.

The Create a Record action with the Select Field list open and a Default Value popover for a text field.

The Create a Record action with the Select Field list open and a Default Value popover for a text field.

Only members who can create records in the chosen table can click; others see the button hidden or disabled.

Note: Default values are fixed values. They cannot be the current user or today's date, and they cannot fill a Linked Record, Files and Images, Signature or Time Tracking Log field. When a field has defaults in several places, the button's value wins, then the template's, then the field's own.

Open a Form

Opens a SmartSuite form from the record, for a controlled way to submit something, such as a change request.

  • Table: the table that owns the form.

  • Form: the form to open. A form must be chosen before the field can be saved.

  • Open in: Slider (the default), Popup, Full Screen or New Tab.

Any member with access to the form can click.


Help Text

A note for the person using the record, up to 800 characters. Help Text Appearance shows it As A Tooltip (the default, behind an info icon next to the field name) or Below The Field Name (always visible).

Use it to say what the click sets in motion. For Request assessment: "Creates an assessment task for Security and emails the vendor contact. Click once per assessment cycle."


Permissions

Field Permissions. Every field can carry its own permissions, which control who can see the field and who can edit it. Open the column menu and select Edit Field Permissions. Hide the button from members who should not request assessments. See Field Permissions.

What the action needs. Each action checks the member's own rights. Open Url works for anyone who can view the record. Execute an Automation needs edit rights on the record. Create a Record needs the right to create records in the target table. Open a Form works for anyone with access to the form.

Dynamic Record Permissions are driven by other field types, not by a Button field. To limit who sees a vendor, use Field Permissions or a rule on another field. See Dynamic Record Permissions.


Using the field in views and records

Every record shows the button, in Grid View and in the record. A button holds no value, so most view tools do not apply to it.

Filtering

Not available. The column menu has no filter entry for a Button field, because a button has no value to compare.

Grouping

Not available, for the same reason.

Sorting

Not available, for the same reason.

Counting and rolling up

Not available. A button is not a value that another field can count or roll up.

Formulas

A formula cannot read a Button field. The link runs the other way: a URL Formula inside the button can read any field in the record.

Automations

Execute an Automation pairs the button with an automation that starts when the button is clicked. Every click is written to the record's Activity History as its own entry, "{User name} clicked {Button name} button", with the action under it.

Note: A click is never merged with other changes in the Activity History, even when they happen in the same minute. The history is a reliable record of who requested what, and when.

Forms

A Button field cannot be placed on a form. Open a Form runs the other way: the button opens a form from the record.


Editing a Button field

Change the label or color. Open Modify Field Settings, change Label or Color, then Update Field.

Change the action. Open Modify Field Settings and pick another Action. The settings for the old action are replaced by the new action's settings: a paired automation is deleted and a chosen form is dropped.

Fix a button that does nothing. A button with no address, no paired automation or no form stays unclickable. Open the settings and complete the action.

Delete the field. Open the column menu and select Delete Field. Deleted fields sit in the Recycle Bin for 30 days.

Note: A Button field cannot be converted to another field type. The panel shows a lock in place of the type dropdown.


Frequently asked questions

Who can click the button?

It depends on the action. Open Url: anyone who can view the record. Execute an Automation: members with edit rights. Create a Record: members who can create records in the target table. Open a Form: anyone with access to the form.

Can the link change from record to record?

Yes. Choose URL Formula and build the address from fields in the record, such as the vendor's Trust Center URL.

Why did my automation run with old values?

It should not. On a record page the record is saved before the automation runs. If the prompt appeared, Run without saving uses the saved values, not the unsaved edits.

Can the new record be pre-filled?

Yes. Create a Record sets fixed default values for most field types. It cannot set linked records, files, signatures or time tracking, and it cannot use the current user or date.

Is each click recorded?

Yes. Every click is its own entry in the record's Activity History, never merged with other changes.

Why is Add Field off?

The action is not complete. Pair an automation, choose a form, or enter a URL, and the button saves.

Last verified 1 Nov 2026.

Did this answer your question?