Changelog
Follow up on the latest improvements and updates.
RSS
new
All Plans
Dashboards: Kanban Widget
Kanban now works as a widget on any SmartSuite dashboard. Service desks rendering a ticket board inside a wider operations dashboard, PMOs visualizing sprint work next to their burndown chart, and GRC programs tracking control status alongside KPI tiles can all drop a Kanban directly onto the canvas, no separate view required.
Key Highlights
- Kanban as a Widget: Place a configurable Kanban widget on any dashboard, with columns driven by a Status, Single Select, or single-value field on the source records.
- Swimlane Grouping: Group cards into rows using another single-value field, including Lookups that target single-value Linked Records, for a two-dimensional view.
- Drag-and-Drop Editing: Drag cards between columns to update the underlying record live, with permissions controlled by record-level access rather than dashboard permissions.
- Performance-First Defaults: Show All button appears on any column with more than six cards, hide empty columns and rows for cleaner boards, collapse all swimlanes for high-density views, and a 3,000-card cap keeps the widget fast.
- Full View Controls: Sort, Filter, Find, Group By, Spotlight, Card Size, and Fields to Display all work in-widget just like they do on a regular Kanban view.
How It Works
- Open a dashboard you can edit and add a new widget; select Kanban View from the widget library under Views.
- Pick the Solution and Application the widget should pull records from; configure View Controls (sort, filter, group by, fields to display) and decide whether users can drag cards.
- Choose a column field (Status, Single Select, or any single-value field) and optionally a swimlane field for two-dimensional grouping.
- End users see the Kanban inline with the rest of the dashboard, can drag cards between columns if their record permissions allow it, and can click any card to open the record.
- Use Hide Empty Columns, Hide Empty Rows, and Collapse All to control density on busy boards; the Show All button surfaces when a column has more than six cards.
Use this when you want a visual board view alongside other dashboard widgets instead of jumping between a Kanban view and the rest of your reports.
improved
All Plans
Forms: Enhanced Submission Page
Publicly shared SmartSuite forms now have a fully configurable Submission Page. Service desk intake forms, GRC attestation flows, and any customer-facing form can show a polished Thank You message or redirect submitters directly to a follow-up URL of your choosing.
Key Highlights
- Two Configurations: Pick Message mode for an inline Thank You page, or Redirect mode to send submitters to a URL of your choice.
- Custom Thank You Page: Configure a toggleable icon, a Title (default "Thank you!"), and a rich-text Description, all editable with the same controls used elsewhere in the form designer.
- Redirect Handling: Specify a URL with inline validation; submitters land there automatically after clicking Submit.
- Public-Only Behavior: The Submission Page applies to publicly shared forms only; internal forms continue to close their dialog on submit, so existing internal workflows are untouched.
- Always Present: The Submission step cannot be removed from a form's setup, so every public form has a defined post-submit experience without builders having to remember to configure it.
How It Works
- Open the Pages control on any form and select the Submission Page; it is always present at the end of the form's page list and cannot be deleted.
- Choose Message (default) or Redirect for the page mode.
- For Message mode, set whether the icon shows, write a custom Title, and compose a rich-text Description; the defaults work fine if you want a generic confirmation.
- For Redirect mode, enter a destination URL; standard inline validation flags any malformed input before you save.
- Publicly share the form and submitters experience the page you configured on submit; internal users continue to see the dialog close as before.
Pair this with Multi-Page Forms and the Progress Bar shipped earlier in May to give long public forms a polished start-to-finish experience.
The Button field on a record now supports Create a Record and Open a Form actions, matching what Button widgets on dashboards have offered. Service desks placing a 'Create Follow-Up Ticket' button on every incident, change boards launching a CAB approval form from a record, and GRC programs offering one-click attestation submissions can now wire the action directly onto a record without leaving it.
Key Highlights
- Create a Record Action: Open the standard record creation page in any Solution and Table, with default values pre-applied to specific fields, all configured directly in the button's settings.
- Open a Form Action: Launch any form from any table in Popup (default), Slider, Fullscreen, or New Tab mode, keeping the user's session and pre-loading the form ready for input.
- Default Values: Most input field types are supported (text, number, date, select-based, etc.). The button overrides field-level default values when both exist, so the button's value wins for that launch.
- Broken Config Handling: If the target Solution, Table, or referenced Field is deleted or migrated, the button surfaces a clean error toast and recovers automatically when the resource is restored from the Recycle Bin.
- Action Parity Across Surfaces: The Button field, Button Row widget, Simple Banner widget, Hero widget, dashboard tabs, and view-based widgets all now share the same action set.
How It Works
- Open a record's field configuration and add a Button field; pick a Display Format (Colored Pill or Text Only), Label (default 'Click me'), and Color.
- Under Actions, choose Create a Record or Open a Form (Open URL and Run an Automation remain available).
- For Create a Record, pick the target Solution and Table, optionally select a Record Template, and configure Default Values for specific fields by adding them one at a time.
- For Open a Form, pick the target Solution and Table, choose the Form from a dropdown of available forms in that table, and pick the rendering mode (Popup, Slider, Fullscreen, New Tab).
- Save and the button appears on the record in your selected display format; clicking it executes the configured action with the user's session and permissions.
Use this when a record needs a one-click follow-up that produces a related record or opens a structured form, without forcing users to navigate to a different surface first.
new
Mobile
Mobile: Kanban View
Kanban views now render on the SmartSuite mobile app with the same layout, controls, and drag-and-drop behavior as the desktop version. Field service technicians clearing tickets between site visits, change managers approving on the move, and PMOs ticking sprint work from anywhere can pick up cards and advance them through their lifecycle without opening a laptop.
Key Highlights
- Mobile Kanban Parity: Open any Kanban view or Kanban dashboard widget on the mobile app and see the same columns, swimlanes, cards, and configuration.
- Drag-and-Drop on Touch: Drag cards horizontally between columns to update the underlying record, with permission checks running through the same record-level model used on the web.
- Honors All View Controls: Sort, Filter, Fields to Display, Group By, swimlane settings, and the Show All density rule all apply on mobile exactly as they do on desktop.
- Tap to Open: Tap a card to open the record details view, including fields, comments, history, and the rest of the standard record surface.
- Service Desk Ready: ITSM technicians clearing a queue between site visits, change managers approving from the field, and GRC reviewers acknowledging controls on the go all get a board view that travels with them.
How It Works
- Open the SmartSuite mobile app and navigate to any table that has a Kanban view configured, or to a dashboard that includes a Kanban widget.
- The Kanban renders with columns left-to-right and swimlanes top-to-bottom, matching the desktop configuration exactly.
- Tap and hold a card to start a drag; drag horizontally to a different column to move the record forward.
- Tap a card to open the full record view, with fields, comments, and history available for review or edit.
- Apply view controls (Sort, Filter, Group By, Fields to Display, density toggles) through the standard mobile controls; changes apply live to the rendered board.
Use this when your team's Kanban board is part of how they actually move work, and they need it in their pocket as much as on a screen at the desk.
new
Enterprise
Signature
Microsoft Teams Automations v2: Actionable Notifications
Microsoft Teams Automations v2 turns one-way notifications into two-way workflows. Service desks running approval flows, change-management boards routing requests through Teams, and any GRC workflow that needs a recipient to take a documented action in Teams can now do it with a single click, attributed back to SmartSuite with a full audit trail.
Key Highlights
- Actionable Notifications: Send a Teams message with up to three clickable buttons mapped to values in a Status, Single Select, Multiple Select, or Yes/No field. Clicking a button updates the target record directly.
- Personal and Team Messaging: Target an individual (static or dynamic mapping from Assigned To, Email, Text, Lookup, Formula, or Single Select fields) or post into a specific Team and Channel.
- Dynamic Record Targeting: Drive notifications from a Trigger output, a Single Find output, or the Current Item inside a Loop, without hardcoding records.
- Dynamic Links in SmartDoc: Build hyperlink URLs inside the message body by mixing static text with dynamic field values, so Open Record buttons always point to the right record.
- Built-In Run History and Error Capture: Failed executions are recorded as comments on the target record with human-friendly reasons (Not enough permissions, Record not found) and a link back to the originating automation.
How It Works
- Admins configure the O365 integration once in Workspace Administration by registering an Azure application and granting the delegated Microsoft Graph permissions.
- Automation builders add the new 'Send an actionable notification' action under Integrations, Microsoft Teams, pick a target record source, choose Personal or Team message, write the title and body with dynamic values, and map a field to buttons.
- When the notification lands in Teams, the recipient clicks a button. SmartSuite validates their record-edit permissions, applies the update, and attributes the change to the person who clicked via the automation.
- Anything that goes wrong (a permission issue, a missing record, a timeout) surfaces as a comment on the record with a clear reason, so automation owners can resolve it quickly.
- Available on Enterprise and Signature plans. Existing legacy Teams actions remain operational.
Upgrade your connection to take advantage of Actionable Notifications and the faster O365 configuration.
new
All Plans
Forms: Progress Bar
Multi-page forms now support a configurable Progress Bar at the top. Service desk intake forms, GRC attestation flows, and any structured multi-page submission can show users where they are in the form, complete with one-click backward navigation to any previous page.
Key Highlights
- New Progress Bar Option: Toggle a Progress Bar on any form with two or more pages from the Style Tab.
- Two Visual Styles: Choose Dot or Numbers to match the form's design language.
- Page Name Display: Optionally show the name of each page next to its progress indicator, or hide names for a cleaner look.
- Backward Navigation: Completed pages are clickable, so submitters can jump back to fix an earlier answer without losing form state.
- Safe Default Behavior: The feature is off by default, requires at least two pages to enable, and auto-disables if page count drops below two.
How It Works
- Open the Style Tab on a multi-page form and find the Progress Bar section near the bottom of the panel.
- Toggle the Progress Bar on (only available when the form has two or more pages, not counting the Submission step).
- Pick a Style (Dot or Numbers) and decide whether to Show or Hide page names alongside the indicator.
- Submitters see the bar at the top of each page, with their current page highlighted, completed pages shown as clickable history, and upcoming pages shown but not yet navigable.
- If a builder removes a Page Break and the form drops to a single page, the Progress Bar disables automatically and no half-configured bar appears on the live form.
Pair this with Multi-Page Forms (released last week) to give long forms the pacing cues submitters need to push through.
Loop actions in automations can now loop over the values in a list-style field on a single record. Service desks fanning a request to multiple owners, GRC workflows looping over a list of related controls, and PMO automations splitting per-member work all get a more direct path than chaining multiple Find Records steps.
Key Highlights
- New Loop Source: Loop over the values in a list-style field (Linked Record, Assigned To, Team, Multiple Select, Tags, Email, Phone, URL, IP Address, or any Lookup to those types) on a single record.
- Per-Value Cycle: Each cycle exposes Current Item with both the current value and the source record's context, so downstream actions can reference either freely.
- ITSM Service Desk Ready: Route a single request to every member in its Assigned To list with one action per member, no chained Find Records required.
- Team Member Loop: For Team fields, choose to loop over the teams themselves or over the deduplicated union of all team members.
- Backward Compatible: Existing loops over record lists work unchanged; this is an additive option.
How It Works
- In a Loop action, choose 'a list field on a single record' as the source instead of the default 'list of records'.
- Pick the source record (Trigger output or Single Find output) and the specific list field on that record to loop over.
- The loop runs once per value in that field; Current Item exposes the value and the record context.
- For Team fields, an additional choice lets you loop over the team names or the unique list of members across all selected teams (with deduplication for members who belong to multiple teams).
- Each cycle's actions reference Current Item just like any other loop step, including Find, Update, Create, and Send Email actions.
Use this when you need to fan one request out to a list of owners, send an email per item in a Multiple Select field, or process every value in a list-bearing field without writing extra Find steps.
new
All Plans
Forms: Review Page
Multi-page forms now support an optional Review Page that lets users confirm their answers before submitting, with one-click edits back to any page. Service desk intake, compliance attestations, and any form with consequential downstream effects gets a built-in safety check at the end.
Key Highlights
- Built-In Review Step: Add a single Review Page to any form to give users one last look at their answers before submission.
- Page-Grouped Answers: Fields display grouped by the page they live on, with the page name as a heading and an Edit button to jump back.
- Configurable Title and Description: Set custom copy for the review header, or use the defaults ('Please review your submissions' and 'Update any relevant information as needed.').
- Per-Field Selection: Choose which fields appear on the Review Page; by default all form fields are pre-selected, including conditionally visible ones.
- Smart Empty States: Unanswered fields show as 'Unanswered', Yes/No fields default to 'No', and fields with configured default values show their default rather than appearing empty.
How It Works
- Add a Review Page from the Pages control at the bottom of the form canvas; one Review Page is allowed per form, and it always sits in a fixed position before the Submission Page.
- Configure the Title and Description for the review header, both with translation support for the default values.
- In the Fields to Review setting, deselect any fields you do not want users to confirm; everything else appears as a Label-Value pair grouped by source page.
- When a user reaches the Review Page, they see all their answers and can click Edit next to any page name to navigate back, make changes, and return.
- The Submit button only appears on the Review Page (or the last Form Page if no Review Page is configured), so users always know they are at the final step.
Use the Review Page wherever a submitter benefits from a confidence check before their answers commit, especially in service desk intake, compliance attestation, and structured onboarding flows.
new
All Plans
Forms: Support for Multiple Pages
SmartSuite Forms now support multiple pages with a built-in Review step and a configurable post-submit experience. Service desks running long intake forms, GRC teams gathering attestations across multiple control areas, and HR teams onboarding new hires can pace longer forms cleanly instead of presenting one wall of fields.
Key Highlights
- Multiple Form Pages: Group related fields into pages, with up to 10 pages per form including an optional Review page.
- Three Page Types: Form Pages hold the fields, the optional Review Page lets users confirm answers before submitting, and the Submission Page handles the post-submit message or redirect.
- Automatic Navigation Buttons: The system shows Next, Back, and Submit buttons in the right places based on which page the user is on, with no manual configuration.
- Page-Level Field Moves: Any field can be moved between pages from its three-dot menu, keeping a form organized as it grows.
- Progress Bar Pairing: Form Pages work hand-in-hand with the new Progress Bar option on the Style Tab to show users their position in a multi-step form.
How It Works
- Open a form's Pages control at the bottom of the canvas to add, rename, reorder, or delete pages.
- Add a Review Page (one per form, optional) to show users their answers grouped by page, with an Edit button next to each page name for jumping back to make changes.
- Configure the Submission Page to either display a thank-you message (with a customizable title, description, and optional icon) or redirect submitters to a URL.
- The form's Title and Header display on every page, so the form's identity stays clear no matter which page the user is on.
- The Submit button only shows on the last Form-type page; Back and Next buttons appear automatically on the right pages.
Use this to break long forms apart into manageable steps, especially for service desk intake, compliance attestation, structured HR onboarding, and any workflow where the form would otherwise feel overwhelming.
new
All Plans
Forms: Linked Record Table Display
Linked Record fields on forms can now display as a table with configurable columns from the linked record's table. ITSM service desks linking to existing tickets, GRC teams linking evidence to controls, and PMO intake linking to active initiatives can give submitters far more context inline than the previous title-only display.
Key Highlights
- New Table Display Format: Pick Table from a Linked Record field's display options to render linked records as rows in an inline table.
- Configurable Columns: Use the Fields to Display control to pick which fields from the linked record's table show as columns; the Title field is pre-selected by default.
- Inline Context for Submitters: Show ticket priority, control status, project sprint, or any other field inline next to the linked record, so submitters do not have to guess what they are linking.
- Familiar Record Selection: Submitters click '+ Link to {Table}' to open the standard record-picker modal, then remove rows with a single X click.
- Backward Compatible: The Standard format (text or pills) is unchanged and remains the default, so existing forms are not affected.
How It Works
- Open a Linked Record field's settings on a form and pick Table as the display format.
- The Fields to Display control appears; pick the fields from the linked record's table that should show as columns. Title is selected by default.
- The Record Selector setting is hidden when Table is chosen, since the modal picker is the default selection method.
- Submitters see the table inline and use the Link button to add records or the X button on a row to remove one without a confirmation prompt.
- Each linked record's field values render as plain text in the table columns; column ordering follows the order you selected fields in the configuration.
Use Table Display anywhere submitters need to see what they are linking to, especially in service desk intake forms (priority and owner inline), GRC evidence forms (control status), and project intake (sprint and dependencies).
Load More
→