Changelog
Follow up on the latest improvements and updates.
RSS
new
All Plans
Date Filters: Calendar Periods and Custom Units
Date filter options now mean what their names say. Six options named after calendar periods — "The next week," "The past month" and their siblings — filtered rolling ranges anchored to today, so "next week" returned the next seven days rather than the upcoming calendar week. Those labels now carry true calendar meaning, "Past" becomes "Previous" to keep the distinction explicit, and twelve calendar periods are available across week, month, quarter and year. Quarters arrive as a filter unit for the first time. The rolling behavior moves to the parameterized options, which now pair a count with a unit picker for days, weeks, months, quarters or years.
Key Highlights
- Calendar Periods That Behave Like Calendar Periods: "Next week" is Monday through Sunday of the upcoming week. "Next month" is the first through the last day of next month. "Next year" is January 1 through December 31. No more rolling range hiding behind a calendar name.
- Twelve Periods, Four Units: Previous, Current and Next are each available for week, month, quarter and year. Current week, Current month, Current quarter and Current year are entirely new.
- Quarters, For The First Time: Previous quarter, Current quarter and Next quarter resolve to calendar quarters, with Q1 running January through March. "Everything closing this quarter" is now a single condition.
- A Unit Picker For Rolling Ranges: "The next number of…" and "The past number of…" keep their count and add a unit control for days, weeks, months, quarters or years. Ten unit-specific options collapse into two, so the value list stays short even as the vocabulary grows. Counts are accepted up to 999.
- Resolved-Range Preview: Every filter row shows the date range the condition actually resolves to, produced from the same resolution the filter itself runs. What the row says and what the grid returns agree.
- Week Start Follows Your Locale: Period boundaries come from each member's profile locale, so a Monday-first team and a Sunday-first team each see their own week.
- Comparison Operators Gain Periods: "is before," "is after," "is on or before" and "is on or after" accept calendar periods and parameterized values. Before a period means before its first day; after a period means after its last day.
- First Created And Last Updated Stay Past-Only: These fields get Previous and Current periods plus "The past number of…", and never offer future options.
- Saved Configurations Migrate Themselves: Every saved filter, view and dashboard using one of the six retired rolling options is rewritten to the equivalent parameterized option. No one needs to rebuild a filter.
- The API Is Additive: New mode names cover the new semantics, and existing modes keep their current behavior indefinitely. Nothing an integration sends today changes what it gets back.
How It Works
- Open any date filter and choose an operator. The value list now groups Today, Tomorrow and Yesterday, the twelve calendar periods, the two parameterized options, and Exact Date or Range.
- Pick a calendar period — Current quarter, say — and the condition resolves to that quarter's first and last day. The line beneath the row states the range, so there is nothing to work out.
- For a rolling range, pick "The next number of…" or "The past number of…", type a count, and choose the unit. "The past number of 3 quarters" is one condition.
- Counted ranges look forward from today or back to yesterday: the next N units includes today, the past N units ends yesterday, so no date matches both directions.
- Everything applies wherever date filters already work, including the filter panel, saved views, dashboard widget filters, spotlights, conditional display rules, document templates and exports.
Filters that read like the question you were asking. Available on all plans.
new
All Plans
Sign-Up: Choose Your Data Region
New SmartSuite workspaces now choose where their data lives. A region selector on the sign-up form lets you create your workspace in either the United States or the European Union, and the workspace is provisioned in the region you pick from the moment it is created rather than moved there later. The selector defaults to the region suggested by your location and appears on every path into a new workspace. Everything after that is automatic — the same address and the same login, with requests routed to your workspace's region behind the scenes.
Key Highlights
- Region Chosen At Creation: Pick the United States or the European Union while signing up. The workspace and its data are created in that region from day one, so there is no later migration and no window where records sit somewhere they shouldn't.
- Every Sign-Up Path Covered: The selector appears when a new user signs up with an email address, when a new user signs up with a social account, and when an existing user creates an additional workspace.
- Defaults To Your Location: The selector pre-fills the region suggested by where you are signing up from, so most people can accept the default and keep going.
- Survives A Refresh: The choice is held alongside the rest of your sign-up progress. Reload the page partway through and the region you picked is still selected.
- One Address, One Login: There is no separate regional URL to remember and no second set of credentials. Requests reach the right region automatically once the workspace exists.
- Invitations Follow The Workspace: Invites, shared links and logins all resolve to the workspace's region without anyone choosing again.
- Data Residency Without A Project: Teams working under regional data requirements can satisfy them at sign-up rather than through a migration, a support ticket, or a separate contract.
How It Works
- Start a new SmartSuite workspace from the sign-up page, with an email address or a social account.
- On the account setup step, choose your region. The selector is pre-filled based on where you are signing up from; change it if your requirements differ.
- Finish sign-up. The workspace, its tables and its data are created in the region you selected.
- Sign in as normal from then on. The region is a property of the workspace, so invitations, links and logins all resolve to it automatically.
- The region is set when the workspace is created, so choose deliberately if you have residency requirements to meet.
Where your data lives, decided in the first minute rather than the twelfth month. Available for all new workspaces at sign-up.
new
All Plans
Mobile
Mobile: Date Filters: Calendar Periods and Custom Units
Date filtering in the SmartSuite mobile app gains the full calendar vocabulary. Twelve calendar periods are available across week, month, quarter and year — Previous, Current and Next for each — so "Next month" on your phone means the first through the last day of next month, and quarter filtering is available for the first time. The counted options are presented as "The next number of…" and "The past number of…", each pairing a count with a unit picker for days, weeks, months, quarters or years, which keeps the value sheet short enough to work on a small screen.
Key Highlights
- Twelve Calendar Periods: Previous, Current and Next for week, month, quarter and year. "Current month" is the calendar month and "Next week" is the upcoming calendar week — the period the name describes, not a rolling range counted from today.
- Quarter Filtering On Mobile: Previous quarter, Current quarter and Next quarter resolve to calendar quarters. Checking what closes this quarter no longer waits until you are back at a desk.
- A Unit Picker Built For A Phone: Rather than ten separate counted options crowding the value sheet, mobile offers "The next number of…" and "The past number of…" with a unit control for days, weeks, months, quarters or years.
- Count Input With Guardrails: The count field accepts digits only and clamps to a whole number between 1 and 999, so a mistyped value cannot quietly produce a filter that returns nothing.
- Translated In Every Supported Locale: All of the new options carry translated labels across the sixteen locales the mobile app supports. No one sees a raw identifier.
- Scrolls On Small Screens: The value sheet scrolls so every option stays reachable, verified down to the smallest supported phone.
- Dashboard Widgets Included: Filter widget date presets and comparison widget week start follow the same vocabulary and the same locale-driven week start, so dashboards agree with the views behind them.
- First Created And Last Updated Stay Past-Only: These fields offer Previous and Current periods plus "The past number of…", and never offer future options.
- Saved Filters Keep Working: A condition saved before this release opens and stays selected. Nothing needs rebuilding.
- Same Results Everywhere: The mobile evaluator resolves periods and counted ranges exactly as the server does, so a filtered list on a phone matches what the same condition returns anywhere else in SmartSuite.
How It Works
- Open a view in the SmartSuite mobile app and tap into its filters.
- Add or edit a condition on a Date, First Created or Last Updated field, then tap the value.
- Choose from Today, Tomorrow and Yesterday, the twelve calendar periods, the two counted options, or an exact date or range.
- For a rolling range, tap "The next number of…" or "The past number of…", enter a count, and pick the unit.
- Apply. The list narrows to the same set the condition returns anywhere else in SmartSuite.
The full date-filter vocabulary, in your pocket. Available on all plans.
new
All Plans
Forms: Support for Checklist Field Type
The Checklist field type is now supported on Form Views. Solution Managers can drag a Checklist field onto a form and configure it with all the standard form field settings plus Checklist-specific settings for entry creation, default-entry editing, Due Dates, and Assignments.
Key Highlights
- Full Checklist Support on Forms: Every Checklist field type property that works inside the main app now works on a Form View, so form respondents can complete a Checklist as part of a form submission.
- Standard Form Field Settings: Required, Help Text, Default Value, Show only when conditions are met, and Display help text as tooltip all work the same way they do for every other field type on a form.
- Checklist-Specific Settings: Users can create new entries (default on), Users can modify and delete default entries (default off), Enable Due Dates (default on), Enable Assignments (default on) — each configurable per form.
- Permission-Aware Assignee Picker: When Assignments are enabled, the Assignee picker only shows members that have access to the target table. Same behavior as the Checklist field inside the main app.
- Notification Routing: When a checklist item is assigned through a form submission, a notification is generated for the assignee. Internal forms attribute the assignment to the submitter; public (Shared) forms attribute the assignment to the SmartSuite Form system user.
- Team Assignments Supported: The existing checklist_team_assignment workspace flag is respected on forms too — when the flag is on, Checklist assignments to Teams work on forms the same way they work inside the main app.
How It Works
- Open a Form View in edit mode and drag the Checklist field from the Left Side panel onto the form.
- Configure standard form field settings (Required, Help Text, Default Value, display logic) in the field's edit mode.
- Configure Checklist-specific behavior: entry creation, default-entry editing, Due Dates, Assignments.
- Publish or share the form. Respondents can add checklist items (if enabled), edit default entries (if enabled), set due dates on items (if enabled), and assign items to members (if enabled).
- When items are assigned, notifications route to the assignee. Internal form submissions attribute the assignment to the submitter; public form submissions attribute the assignment to SmartSuite Form.
Available on all plans.
new
All Plans
Linked Records: Advanced Settings
The Linked Record field settings pick up a new Advanced Settings modal that consolidates the display-configuration controls (Fields to Display, Group, Sort) and adds new capabilities on their own tabs. The modal opens with a live Preview on the left rendered from the last 50 records of the target table, and organizes settings across General (display format + Fields / Group / Sort), Filters (new — Static and Dynamic filters, ships alongside this release), and Actions (later phase) tabs. Simplifies the main Linked Record field settings screen while making the advanced surface much easier to configure.
Key Highlights
- New Advanced Settings Button: A single Advanced Settings button on the Linked Record field configuration opens the new modal. Fields, Group, and Sort controls move from the main settings screen into the modal so the main configuration surface stays clean.
- General Tab: Display format, Fields to Display, Group, and Sort in one place. Same functionality as before, better-organized surface.
- Filters Tab (new this release): Configure Static Filters (fixed conditions the viewer can't change) and Dynamic Filters (viewer-facing filter controls) on the Linked Record field. Ships alongside Linked Records: Static Filters and Linked Records: Dynamic Filters this same release.
- Actions Tab (placeholder): Reserved for a later phase.
- Live Preview: The left panel renders a live preview of the configured Linked Record using the most recent 50 records from the target table, so Solution Managers can see the effect of every configuration change without leaving the modal.
- Same Underlying Behavior: This is a UI reorganization plus a new Filters capability, not a change to how Linked Records themselves work. Existing configured Linked Record fields inherit the new modal automatically.
How It Works
- Open a Linked Record field's settings. In place of the previously-exposed Fields, Group, and Sort controls, an Advanced Settings button now appears.
- Click Advanced Settings to open the modal. The General tab loads by default with the display format, Fields, Group, and Sort controls.
- Switch to the Filters tab to configure Static or Dynamic filters on the field (or leave as None).
- Watch the live Preview on the left refresh as you change settings, sampled from the last 50 records of the target table.
- Save. Configuration applies to the Linked Record field everywhere it's referenced.
Second of three Linked Records enhancements shipping this release, following the Jul 27 Sticky Add New + Grouping and Aug 17 Dropdown Mode releases. Available on all plans.
new
All Plans
Linked Records: Static Filters
Linked Record fields pick up Static Filters — preset filter conditions on the field itself that let Solution Managers control which linked records display, without touching how records are actually linked. Configured on the new Filters tab of the Advanced Settings modal, Static Filters use the same condition builder that already drives Filter widgets and view controls. A default "All {record name}" filter is added automatically so users can always see the full set of linked records; additional filter sets can be added for common slices.
Key Highlights
- New Filters Tab: Under the Linked Record field's new Advanced Settings modal (also shipping this release), a Filters tab lets Solution Managers pick None, Static, or Dynamic.
- Static Filter Sets: Configure any number of named filter sets on a Linked Record field. Each filter set uses the same condition builder that already drives Filter widgets and view controls — no new syntax.
- Automatic "All" System Filter: When Static Filters is enabled, a system filter labeled "All {record name}" is added automatically. It shows every linked record, has a read-only label, and can't be removed — so users always have a way back to the full set. Solution Managers can reposition it in the list.
- Same Condition Builder: The Filter widget's condition builder is reused verbatim — no code duplication, no new UX to learn.
- Viewer Sees a Filter Picker: Configured Static Filters appear as a picker at the top of the Linked Record's display surface. Users switch between filters to see the corresponding slice of linked records.
- Preserves Underlying Links: Static Filters change what displays, not what's linked. Every linked record is preserved on the record; the filter is a display-time overlay.
How It Works
- Open a Linked Record field's settings and click Advanced Settings.
- Switch to the Filters tab and choose Static. The system adds an "All {record name}" filter automatically (read-only, non-removable).
- Add additional named filter sets using the standard condition builder — filter by field values, sort, group, whatever narrows the display to a useful slice.
- Save. On the Record Page and other Linked Record display surfaces, users see a filter picker at the top of the field and can switch between the configured filter sets.
- All linked records remain linked at the data layer; Static Filters only change what's displayed.
Second of the three Linked Record enhancements shipping this release, alongside Advanced Settings (the container modal) and Dynamic Filters (viewer-driven filter controls). Available on all plans.
new
All Plans
Linked Records: Dynamic Filters
Linked Record fields pick up Dynamic Filters — viewer-facing filter controls that let end users slice the linked-record list without editing the field configuration. Configured on the new Filters tab of the Advanced Settings modal, Dynamic Filters render as a filter picker at the top of the Linked Record display surface so viewers can filter by any field on the target table at view time.
Key Highlights
- New Filters Tab: Under the Linked Record field's new Advanced Settings modal (also shipping this release), a Filters tab lets Solution Managers pick None, Static, or Dynamic.
- Viewer-Facing Filter Controls: Dynamic Filters render as a filter picker on the Linked Record's display surface (Record Page, Record Details Widget). End users choose values to narrow the visible list without touching the field configuration.
- Same Filter Widget Behavior: Dynamic Filters reuse the same functionality already implemented for the Filter Widget's dynamic filters — no new logic, no new UX. Solution Managers who already know Filter widgets already know Dynamic Filters.
- Configure Which Fields Users Can Filter By: Solution Managers configure which fields on the target table are exposed as filter dimensions. Common picks: Status, Assigned To, Due Date, Priority, any Single Select or Yes/No.
- Per-Viewer, Per-Session: A user's Dynamic Filter selections don't persist to other viewers of the same record. Each user gets their own live view.
- Preserves Underlying Links: Dynamic Filters change what displays, not what's linked. Every linked record remains linked at the data layer.
How It Works
- Open a Linked Record field's settings and click Advanced Settings.
- Switch to the Filters tab and choose Dynamic.
- Configure the filter dimensions viewers can use — which fields are exposed and in what order.
- Save. On the Record Page and Record Details Widget, users see a filter control at the top of the Linked Record field and can filter the visible records by the exposed dimensions.
- Filter selections are per-viewer and per-session — they don't change what's linked, and they don't affect what other users see.
Third of the three Linked Record enhancements shipping this release, alongside Advanced Settings (the container modal) and Static Filters (author-driven preset filter sets). Static and Dynamic Filters share the same Filters tab — pick one flavor per field. Available on all plans.
new
All Plans
UI & Reporting
Dashboards: View-Based Widget Preset Filters
View-Based dashboard widgets pick up a third filter layer: Preset Filters on the widget itself, configured in a new Filters tab. Solution Managers choose Static (fixed conditions the viewer can't change) or Dynamic (viewer-facing filter controls on the widget so dashboard consumers can slice the data themselves). Preset Filters combine with the existing Filter Widget and the widget's own Filter Control using AND logic. Shareable dashboards expose Dynamic Filter controls to recipients with the full record set intact.Key Highlights
- New Filters Tab: A dedicated Filters tab on the widget configuration modal, with a Preset Filters section that lets Solution Managers pick None, Dynamic, or Static.
- Static Preset Filters: Fixed conditions the dashboard viewer can't change. The author writes the filter once and every viewer sees the same slice.
- Dynamic Preset Filters: Viewer-facing filter controls that render on the widget so dashboard consumers can slice the data themselves without editing the dashboard configuration — Status, Assigned To, Linked Record, date range, and any other filterable field type.
- Same Condition Builder: Preset Filters use the same condition builder as the Filter Widget and every other filter surface in SmartSuite — no new syntax to learn.
- Three Filter Layers, All ANDed: Filter Widget (dashboard-wide), Filter View Control (widget-level, editor-owned), and Preset Filters (widget-level, author- or viewer-owned) all combine as AND-joined condition groups. Any narrowing in one layer stacks with narrowing in the others.
- Preset Type Switching Preserves Work: Only one Preset Filter type can be selected at a time, but switching between Static and Dynamic preserves any conditions already configured so authors can flip between the two without rebuilding.
- Shareable with Full Record Set: Sharing a dashboard exposes Dynamic Preset Filter controls to recipients with no pre-selection applied and the full underlying record set intact — a viewer's live filter selection never truncates the data other viewers see.
- Reference-Field Support: Dynamic Preset Filters based on Linked Record, Assigned To, or Lookup fields surface the reference records recipients need in the picker after sharing.
How It Works
- Open a View-Based widget's configuration modal on a dashboard.
- Go to the new Filters tab. In the Preset Filters section, choose Dynamic or Static (or leave as None to skip this filter layer).
- Configure the filter conditions using the same condition builder that drives the Filter Widget and every other filter surface in SmartSuite.
- Save. If the type is Static, every viewer of the dashboard sees the same filtered slice. If the type is Dynamic, a viewer-facing filter control renders on the widget for consumers to slice with.
- Combine with the Filter Widget and the widget's Filter View Control — all three layers work together as AND-joined condition groups.
Available on all plans.
new
All Plans
Mobile
Mobile: Power Search
Power Search comes to SmartSuite Mobile. Tapping the Search icon on iOS or Android now opens a Power Search modal that reproduces the desktop experience — workspace-wide record search across every Solution and Table, with the same filter set that the desktop Power Search provides. Field service techs looking up a work order without remembering which Solution it's in, ITSM agents pulling up an incident from a customer name typed at the pump, and PMO leads finding a task assigned to a specific member across every project all get the same "find anything from anywhere" experience mobile that they already had at their desk.Key Highlights
- Workspace-Wide Mobile Search: Tapping the Search icon on the mobile app opens a Power Search modal that searches record content across every Solution and every Table in the workspace — no more homepage-scoped or Table-scoped search on mobile.
- Desktop Filter Parity: The mobile Power Search modal offers the same filter set that the desktop Power Search provides — narrow the result set by Solution, by Table, by field values, or by any other filter dimension supported today on web.
- Native Mobile UI: The Power Search modal is a native mobile interface, not a mobile-browser fallback — matching the native-mobile experience the app already provides for Grid, Calendar, Card View, Chart View, Internal Forms, and Shared Forms.
- No Configuration Required: Every mobile user picks up the new behavior automatically once they update the SmartSuite Mobile app.
- Continues the Mobile-Parity Arc: Ships alongside a multi-week mobile-parity push — Jul 20 Calendar and Card View widgets, Aug 3 Chart Widget, Aug 10 Internal and Shared Forms, and now Aug 31 Power Search.
How It Works
- Update the SmartSuite Mobile app to the latest version on iOS or Android.
- From the Home screen or from inside any Table, tap the Search icon.
- The Power Search modal opens. Type a search term to search record content across every Solution and Table in your workspace.
- Apply filters to narrow the result set — the same filters available in desktop Power Search work here.
- Tap a result to open the record.
Available on all plans. No configuration required.
improved
All Plans
Automations & Integrations
Webhook Trigger: Optional and Required Fields
The Webhook Received automation trigger picks up per-field Required controls and a distinct Rejected run-history status. All fields in the webhook structure are non-required by default; toggle Required on the fields that truly matter, and requests that arrive without one of those fields return HTTP 400 to the caller (naming the offending field) plus a Rejected run in history — separate from Failed and Error. Non-required fields no longer break the whole run when missing. Incoming webhook payloads are now captured in Run History as an expandable tree (parsed and raw) for every run, including rejected ones.Key Highlights
- Fields Are Optional by Default: Every field in the configured webhook structure is now non-required by default. A missing or empty field on a non-required field no longer rejects the incoming request or fails the automation.
- Per-Field Required Toggle: Each field in the structure gets a Required toggle. Toggle it on for the fields that truly matter — a payment webhook's amount, a signup webhook's email — and only those fields gate the request.
- Rejected Run-History Status: Requests that fail the Required-field gateway land in Run History with a distinct Rejected status, visually separated from Failed / Error. No action steps execute for a rejected request.
- HTTP 400 Response to Callers: Rejected requests return HTTP 400 with the offending field name(s) in the response body — {"error": "Missing or empty required field(s): status"}— so the calling system can react cleanly.
- Payload Capture in Run History: The incoming webhook payload is now recorded on every run — successful, rejected, and failed. Rendered as a collapsed-by-default expandable key:value tree, with a View Raw toggle for the raw request body.
- Deterministic Handling of Empty vs. Absent: Present-and-empty and null both write empty to the target field. Absent-from-payload also writes empty (per the latest team decision). Present-with-value uses the value.
- Extra Fields Ignored: Payload fields not in the configured structure are accepted and ignored — no error, no surface. Delete unneeded fields from the generated structure without consequence.
- Migration: All existing webhook automations move to the new behavior automatically.
How It Works
- Open a Webhook Received trigger in an automation. Every field in the configured structure now shows a Required toggle in field settings, off by default.
- Toggle Required on for the fields that truly need to be present for the automation to make sense. Leave the rest off.
- When a webhook arrives, the trigger checks Required fields first. If any Required field is absent, null, or empty, the trigger returns HTTP 400 with the offending field(s) named, records the run as Rejected, and does not execute action steps.
- If all Required fields pass, action steps run. Each step maps values from the payload independently — empty and null both write empty, absent also writes empty, values are used as-is.
- Open Run History to see the incoming payload on any run (successful, rejected, or failed) as an expandable tree, with View Raw for the raw body.
Available on all plans. All existing webhook automations migrate to the new behavior — no reconfiguration required.
Load More
→