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.

Linked Record fields now support default values on the field, on Create-a-Record button actions, and on forms. Pre-populate the most common relationship so new records start with the right connections in place; multi-link fields can carry multiple defaults. Service desks routing new tickets to a default queue, GRC programs attaching new findings to a default control area, and PMO templates pre-populating a linked Sprint all benefit.

Pair this with the rest of the Default Values rollout this year, including Yes/No default values from last week and the broader Default Values framework in the form designer.

The AI Center now supports the latest flagship models from Anthropic, OpenAI, and Google Gemini, organizes every model into four clear price tiers, and retires deprecated model IDs. Cost-optimizing existing automations and upgrading to flagship reasoning for complex work both get a lot easier.

Applies to every AI-powered surface in SmartSuite: AI Field Agents, AI Assist, and automation-triggered AI actions.

Yes/No fields can now have form-level default values, joining the growing list of field types that support form-specific defaults. Set the starting state (Yes, No, or empty) per-form, so risk acknowledgment toggles default to No, opt-in checkboxes default to Yes when appropriate, and any boolean question comes pre-set to fit the form's audience.

Pair this with the rest of the Default Values rollout this year, including Linked Record default values and the broader Default Values framework documented in the form designer.

The Filter Widget on SmartSuite dashboards now supports Static Filter mode. Solution Managers pre-configure named filter sets, the widget renders them as tabs across the top, and connected dashboard widgets re-load their data when a viewer clicks a different tab. Service desks toggling between ticket cohorts, GRC dashboards switching between audit areas, and PMO sprint dashboards flipping between sprint stages all get a viewer-facing filter surface that is consistent across the team.

Use this when the dashboard's filter combinations are stable and curated by a manager, and you want viewers to switch between them with a single click instead of building filters themselves.

The form designer's Style tab now exposes a Layout section with Classic, Banner, and Full options, plus a new Appearance section for background color and button styling. Service desk intake forms can wear corporate branding, GRC attestation forms can use full-bleed hero imagery, and HR onboarding forms can match team-specific color treatments without leaving the form designer.

Pair this with the rest of the Forms 2.0 work shipping this year, including Multi-Page Forms, Progress Bar, Enhanced Submission Page, and the New Forms Page.

Single Select, Multiple Select, and Status fields can now render on forms as Radio Buttons or Checkboxes instead of the dropdown default, with a configurable 1, 2, or 3-column layout. Service desk forms exposing all priority options at once, GRC attestation forms showing every compliance answer side by side, and HR forms surfacing role choices without a dropdown click all benefit from a more scannable submission experience.

Pair this with the rest of the Forms 2.0 work shipping this year, especially the new Layout and Appearance options and the Enhanced Submission Page.

Dynamic Record Permissions is now generally available. Solution Managers can build table-level rules that restrict who can View, Edit, Create, or Delete records, with scope down to individual tabs and sections and conditions tied to field values. GRC programs locking completed policies, audit programs making engagements read-only on completion, and security teams walling off sensitive records all now have a control surface that matches how their governance actually works.

A note on the upgrade path: customers who used Dynamic Record Permissions in the early access period get the GA experience with no migration work.

Solutions now have a dedicated Forms page in the Solution menu that shows every form in the solution as a tile, grouped by its target table. Service desks running multiple intake forms, GRC teams maintaining attestation forms across control areas, and HR programs juggling onboarding, leave, and exit forms can all manage their forms from a single operational hub instead of hunting through individual tables.

Pairs naturally with the rest of the Forms 2.0 work this year, including Multi-Page Forms, Progress Bar, Enhanced Submission Page, and the Submittable Form View.

The Form View has been redefined. It is now a view type linked to an underlying source form, rendered in ready-to-fill state for any table member with view access. Service desks placing an intake form in every team's view panel, HR teams attaching onboarding forms to people tables, and GRC programs putting attestation forms next to control records all get a one-click submission surface inside the work they already do.

Use this when a form needs to be available inside the team's existing workspace rather than as a public link, especially for high-volume internal submissions like ticket intake, attestation, or onboarding requests.