Save

The Save action adds a button to your layout that writes the user's changes to the database. When someone edits a record - updating a contact's phone number, changing a project's status, filling out a new entry - nothing is stored until they click Save. Without this button, any changes made in a form are lost as soon as the user navigates away.

When to use it

Any layout that contains editable fields - the Save button is required to commit those changes.
Edit forms for contacts, projects, invoices, tasks, or any other object type.
New record creation forms where the user fills in fields and then confirms.
Multi-step forms where you want to save progress before moving to the next section.

How to add it

Open the layout editor for the layout you want to modify.
Click Add Block in the area where you want the button to appear.
Select Action from the block type list.
Choose Save from the action options.
Optionally rename the button label (e.g. "Save Changes" or "Update Contact").
Save and publish your layout.

Place the Save button at the bottom of your form where users expect it, or pin it to the top if you have a long form. Pairing it with a Cancel or Go to Page button gives users an easy way to discard changes.

Example

You run a small CRM and have an edit layout for your Contacts object. The layout has fields for First Name, Last Name, Email, Phone, and Status. You add a Save button at the bottom of the form. When your team opens a contact, edits the phone number, and clicks Save, the new number is immediately stored. If they close the tab without clicking Save, nothing changes - the original data remains intact.

Tips

You can customize the button label to be more descriptive, like "Save Contact" or "Update Order", so users know exactly what they're saving.
If your form is long, consider adding a Save button both at the top and bottom so users don't have to scroll to confirm.
The Save action only works within a layout that has editable fields - it has no effect on read-only display layouts.