The buttons block is how viewers make things happen: each button runs one of your app's actions — add a row, open a form, jump to a view, compose several steps, or trigger a workflow.
Try it: Press the buttons: each runs its action, and Delete asks for confirmation first. Change the alignment in the settings strip.
Settings
Example. A buttons block with the four styles: a primary New order button that opens the form, an outline Export button, a ghost Help link, and a destructive Delete that asks for confirmation. Buttons a viewer's role can't use are left out.
Each button has a label, the action it runs, and a style.
Button style
primary / outline / ghost / destructive
Visual weight per button — use destructive for deletes.
Alignment
left / center / right
Where the row of buttons sits in the block.
On record pages, actions run with the current record as context — an Edit rowbutton edits the record the viewer is looking at. Actions also honor role visibility, so a button a role can't use simply isn't rendered.
Like every block, this one also has the shared block settings: a title and optional description, a header you can show or hide, auto-height, conditional visibility, and role-based visibility.