You can use dashboard buttons to create new records with pre-filled information—making it easier for your team to submit requests, log work, or start workflows from one central place.
This turns your dashboard into a guided entry point instead of just a place to view data.
What This Does
The Create a Record button lets you:
Open a new record in any table
Pre-fill fields with specific values
Guide users into the right workflow
Keep data consistent across submissions
Instead of asking users to choose where to go, you can give them clear options like:
“Submit IT Request”
“Request Equipment”
“Log Incident”
How It Works
When someone clicks the button:
A new record opens
Some fields are already filled in
The correct layout (template) is applied
The user completes the form and clicks Save
The record is only created after the user clicks Save
How to Set It Up
1. Add a Button to Your Dashboard or Widget
Open your dashboard
Add or edit a button
Choose Create a Record as the action
2. Choose Where the Record Goes
Select the table where the record should be created
By default, it uses the current table
3. (Optional) Choose a Template
Templates control what users see when the record opens.
They can:
Show or hide fields
Organize tabs and sections
Adjust the layout for different use cases
4. Set Default Field Values
You can pre-fill fields so users don’t have to.
Examples:
Set Request Type = IT Support
Set Status = New
Assign to a specific team
To do this:
Add a field
Choose a value
These values will automatically appear when the record opens.
What You Can Pre-Fill
You can set defaults for most field types, including:
Text and numbers
Dates and times
Status and dropdowns
Checkboxes (Yes/No)
Assigned users
Tags and colors
Addresses
Not supported:
Linked records
File uploads
Signatures
Time tracking
Which Values Take Priority?
If a field already has a default set elsewhere:
Button values win
Then template defaults
Then field-level defaults
This ensures your button always controls the entry experience.
Example: Build a Request Dashboard
You can create a simple request hub like this:
Request Laptop
Request Access
Submit Issue
Each button:
Creates a record in the same table
Sets a different Request Type
Shows only the fields needed for that request
This makes it easier for users and keeps your data organized.
Make It Visual with Card Buttons
You can display buttons as cards instead of standard buttons.
Card options include:
Icons
Titles
Multi-column layouts
This is great for building a clean, app-like experience.
Permissions
Buttons follow your existing permissions:
If a user can create records → they can use the button
If not → the button will be hidden or disabled
Best Practices
Use buttons to guide users into the right workflow
Keep logic (automations, conditions) inside templates—not buttons
Use a field like Type or Category to control workflows
Design dashboards as simple entry points, not just data views