Quick Steps Column
Common Use Cases
- Status buttons: a Mark Complete or Resolve button that stamps the Status column on the row without opening the edit form
- Help Desk triage: separate Assign to Me, Escalate and Resolve buttons, each colored to match its urgency
- Approval requests: a Request Approval button on each document or item so reviewers are asked in one click
- Contact the owner: a Teams chat or email button addressed to the person in the row’s Person column
- Kick off a process: a button that runs a Power Automate flow for onboarding, publishing or archiving the selected item
- Sign-off stamping: a Set a Value button that records the current user and today’s date in Approved By and Approved On columns
Benefits
- Actions in the view: buttons sit on every row, so users no longer hunt through the Automate menu or open each item
- No JSON required: buttons are configured through a guided sentence-builder panel instead of column formatting code
- Fewer custom flows: common tasks like setting a status or notifying a colleague run without building a Power Automate flow
- Consistent process: every user performs the same step the same way, which keeps column values clean and predictable
- Context-aware buttons: conditions hide buttons that do not apply, so each row only shows the next sensible action
- Out-of-the-box: the column type ships with SharePoint Online and needs no add-ins, licenses or tenant admin setup for the core actions
Details
- Feature Category: Columns & Views
How It Works
- A column of buttons: the column holds no data of its own and renders one or more Quick Step buttons in each row
- Built on Quick Steps: each button is a Quick Step, either an existing one from the list or a new one created from the column panel
- Five core actions: draft an email, start a Teams chat, set a value, send an approval request, or execute a flow, plus Ask SharePoint prompts with Copilot
- Labels and colors: each button gets its own label and color, set separately from the column name shown in the header
- Show conditions: rules based on other column values or the current user decide when each button appears on a row
- Multi-row stamping: Set a Value can update several columns, insert the current user or date, and stamp every selected row at once
Limits and Nuances
- No undo: Set a Value runs immediately with no confirmation dialog, so a mis-click changes data until someone edits it back
- Simple conditions: show rules are column value and current user checks, not full formulas or JSON logic
- Drafts, not sends: email and Teams actions open a prefilled draft that the user still reviews and sends
- Flows need access: Execute a Flow requires a flow shared with the list, and users without access see an error when they click
- Approval prerequisites: the approval action depends on approvals being enabled on the list or library
- Copilot licensing: Ask SharePoint buttons require a Microsoft 365 Copilot license for the user who runs them
Common Questions About the Quick Steps Column
What is the Quick Steps column in SharePoint?
The Quick Steps column is a SharePoint column type that displays one-click action buttons on every row of a list or library view. Each button runs a Quick Step, such as drafting an email, starting a Teams chat, setting a column value, sending an approval request, or executing a Power Automate flow. The column stores no data itself. It exists to put the most common next action for each item directly where users are already working.
What is the difference between Quick Steps and the Quick Steps column?
Quick Steps is the automation feature itself, a set of predefined one-click actions defined on a list or library. By default those actions live in the Automate menu and the right-click menu once an item is selected. The Quick Steps column is a way of surfacing the same actions as visible, labeled buttons inside the view, one row at a time. The actions are identical. The column simply makes them easier to find and faster to use.
How many buttons can one Quick Steps column hold?
A single Quick Steps column can hold multiple buttons, and community testing has put the practical limit at 15 per column. Each button has its own label, color and display conditions, so one column can act as a compact action bar for an entire process. In practice most well-designed lists use two to four buttons per column, because too many choices on every row slows users down rather than speeding them up.
How do conditions on Quick Steps buttons work?
Each button can carry show conditions built with the same sentence-builder used by SharePoint rules. A condition checks a column value or the current user, for example showing Resolve only when Status is not Resolved, or showing Assign to Me only when Assigned To is empty. When the condition is false the button is hidden on that row. This keeps each row focused on the next valid step and prevents actions that make no sense for the item’s current state.
Why does a Quick Steps button not work for some users?
Quick Steps buttons run under the permissions of the person who clicks them. Setting a value or requesting approval needs Edit access to the item, while drafting an email or starting a Teams chat works with Read access. Execute a Flow buttons fail for users who have no access to the connected flow, and Ask SharePoint buttons need a Microsoft 365 Copilot license. The column itself does not grant any rights beyond what SharePoint already allows.
When should I use a Quick Steps column instead of a Power Automate flow or column formatting?
A Quick Steps column is the right choice when the action is a single, well-defined step that users trigger by hand, such as stamping a status or asking for approval. Multi-step logic still belongs in a Power Automate flow, which the button can trigger. Greg Zelfond, the consultant behind LookBook 365, designs these buttons around the real process a team follows, deciding which steps become buttons, which stay in flows, and which conditions keep every row clean and self-explanatory.