Forms now support the Date Range field. Respondents can submit both a start date and end date in a single form field, using whichever Display Format (Compact, Standard, Long, or Pill) the underlying field is configured with. Event teams collecting session times, PMO leads gathering project phase start and end dates, and HR teams scheduling interview windows all get a native single-field control instead of composing two separate date fields.

With Date Range as a native form input, SmartSuite's Form Builder now covers the full span of scheduling, phase-capture, and window-based workflows in a single field.

The Add New button in inline-editable Linked Records grids is now sticky to the grid's footer, so it stays visible no matter how long the linked-record list gets or how the grid is grouped. Service desks adding tickets to a Change Request's linked grid, PMO leads adding deliverables to a Sprint's linked grid, and any workflow using inline Linked Record editing on the Record Page all get a more reliable path to Add New.

With the sticky footer, inline editing on Linked Records grids behaves the same across every grid state, giving teams a dependable path to Add New whether the grid is short, long, or grouped in any configuration.

The Record Selector on Linked Records now supports Grouping alongside the existing Fields, Sort, and Filter controls. Solution Managers configure which field records get grouped by, group ordering, and whether groups default to collapsed or expanded — regular users see a grouped selector with search that auto-expands matching groups. Service desks grouping ticket links by Priority, GRC teams grouping controls by Framework, and PMO leads grouping sprint records by Owner all get a more navigable Record Selector.

Adding Group By to the Record Selector rounds out its view-control set — Fields, Sort, Filter, and now Group — so large linked-record pools stay navigable no matter how many records they hold.

Calendar View and Card View widgets are now supported on mobile Dashboards. Field service techs checking today's assigned work on a mobile Calendar widget, sales reps scrolling through a Card View of open opportunities between meetings, and PMO leads sharing status dashboards that work across every device all get two more layouts that render properly on phone and tablet.

With Calendar and Card View joining the mobile-supported set, SmartSuite Dashboards keep closing the gap on full mobile-desktop parity, giving builders a growing library of layouts that work wherever their teams do.

The Record Page now supports Conditional Required Fields. Solution admins define per-field rules on the Display Logic tab that make a field mandatory when other field values dictate it, and the rule fires immediately as users edit the record — no save-time surprise. ITSM incident forms requiring a resolution note only when Status equals Resolved, GRC attestation records requiring an evidence link only when Result equals Pass, and PMO project intakes requiring an executive sponsor only when Priority equals Critical all get conditional validation at the right moment.

Available on Enterprise and Signature plans.

The Manage Members page adds a new Solution Access modal that gives Workspace Admins a full access map for any user in the workspace. Open a member's three-dot menu, pick Solution Access, and see every Solution they can reach with the highest combined personal-and-team permission for each — drill into a Solution to see its Tables, filter, search, and export to CSV. ITSM operators reviewing who can access the Incident Management solution, GRC compliance teams verifying auditor scope before a SOC 2 review, and Workspace Admins running quarterly access reviews all get member-level visibility from a single pane.

SmartSuite AI now centralizes LLM provider connections in a new AI Control Center under Workspace Administration. Workspace admins configure a provider key once, scope it to specific solutions and features, and reuse it across AI Workflow Agent actions and AI Field Agents. Existing configurations migrate automatically; new workspaces get a pre-configured Trial Connection with 100 free requests. Compliance-conscious ITSM teams, GRC programs enforcing model governance, and any organization scaling AI across multiple solutions get the configuration surface that production AI use warrants.

Existing AI Field Agent and AI Workflow Agent Action configurations migrate automatically. Workspaces without a previously-configured key get automatically pointed at the SmartSuite Trial Connection so no automation or agent breaks.

Dynamic Filter Widgets on dashboards can now filter by Lookup fields. ITSM service desks filtering a Tickets widget by the linked Change Request's Priority, GRC dashboards filtering a Findings widget by the linked Control's Status, and PMO dashboards filtering a Tasks widget by the linked Sprint's Owner all get filter behavior that reaches through the relationship instead of only working with the direct record's own fields.

Pair this with the Static Filters mode released in the June 22 cohort for dashboards where the filter combinations are stable enough to expose as tabs.

Forms now support a configurable Footer on the Style tab, giving form builders visual control at the bottom of the form to match what the Layout and Appearance sections provided at the top. Service desk intake forms with contact info and SLA reminders, GRC attestation forms with compliance boilerplate, and customer-facing forms with company brand messaging all now have a proper footer surface without leaving the form designer.

Pair this with Forms: Layout and Appearance (Jun 22 release) and the rest of the Forms 2.0 work shipping this year for a full end-to-end style pass on any customer-facing or publicly-shared form.

Every automation-driven change on a record now includes a direct link to the specific automation run that made it, embedded in the record's Activity History. Change managers investigating an unexpected update, GRC auditors tracing per-record data changes to their source, and anyone debugging an automation outcome can now hop straight from the affected record to the run that touched it, instead of scrolling through the automation's run history one-by-one.

Use this whenever a record ends up in an unexpected state and you need to trace exactly which automation execution caused it.