Changelog
Follow up on the latest improvements and updates.
RSS

AI Field Agents now support the Address field as a target output. The agent generates a structured address from record context — populating dispatch locations from incident descriptions, shipping addresses from lead notes, or project sites from proposal text — with the same governance, Manual/Automatic run controls, and audit-trail logging as the existing Text and Single Select Field Agents. ITSM service desks generating dispatch locations, sales teams parsing prospect leads into shipping addresses, PMO leads inferring site locations from proposals, and any workflow where the address is knowable-from-context rather than typed by hand get a first-class AI target for structured location data.
Key Highlights
- New Field Type Coverage: Address joins Title, Text, Number, SmartDoc, Text Area, Single Select, Multiple Select, Status, and Link as a supported target for AI Field Agents. Same prompt-builder UI, same governance model, same audit trail — new output type.
- Structured Output, Not Just Text: The agent generates a properly-structured address (street, city, state, postal code, country) that populates the Address field's native storage model. Search, geocoding, and mapping integrations work against AI-generated addresses exactly as they do against typed ones.
- Manual and Automatic Runs: Configure Automatic runs to re-evaluate the address whenever a triggering field changes, or leave Automatic off for user-initiated runs from Grid view, the Record Page, or a Record Details widget.
- Full Audit Trail: Every AI-populated address logs as AI-driven activity in the record's audit history. Manual overrides re-attribute cleanly to the user who made the edit, preserving traceability.
- Same Workspace Governance: Requires the workspace-level AI Field Agents toggle. Inherits the workspace's Internet Search setting when relevant. Uses the connection registry from the July 14 Managed Connections release for provider/model routing.
How It Works
- Open an Address field's Field Settings and switch to the AI Field Agent tab.
- Toggle Enable AI Field Agent. Compose the prompt referencing other fields on the record with the field-variable selector (for example: "Generate the dispatch address for this incident based on {{Location Description}}, {{Nearest Landmark}}, and {{Asset Site}}").
- Pick a Connection from the dropdown of admin-enabled connections for AI Field Agent on the current solution.
- Optionally enable Automatic runs so the address re-generates when the triggering fields change; leave off for manual-only runs.
- Save. On the Record Page or Grid view, run the agent manually or watch it populate automatically as record context evolves. The generated address appears in the Address field and the activity log flags the change as AI-generated.
Requires the workspace-level AI Field Agents toggle in Workspace Administration → AI Control Center → AI Field Agents. Available on all plans.

AI Field Agents now support the Date field as a target output. The agent generates a structured date value from record context — inferring project completion dates from status updates, SLA target dates from priority levels, or control review deadlines from Framework context — with the same governance, Manual/Automatic run controls, and audit-trail logging as the existing Text and Single Select Field Agents. PMO leads inferring project phase completion dates, ITSM service desks generating SLA target dates, GRC compliance teams computing control review deadlines, HR onboarding workflows setting 30-60-90 review dates, and any workflow where the date is derivable from other record context all get a first-class AI target for structured time data.
Key Highlights
- New Field Type Coverage: Date joins Title, Text, Number, SmartDoc, Text Area, Single Select, Multiple Select, Status, and Link as a supported target for AI Field Agents. Same prompt-builder UI, same governance model, same audit trail — new output type.
- Structured Output With Time Support: The agent generates a properly-structured date value that populates the Date field's native storage model. If the underlying Date field has time enabled, the AI generates both date and time components. Timeline View, calendar widgets, and date-based filters and formulas work against AI-generated dates exactly as they do against typed ones.
- Manual and Automatic Runs: Configure Automatic runs to re-evaluate the date whenever a triggering field changes (SLA target dates recompute when Priority updates), or leave Automatic off for user-initiated runs from Grid view, the Record Page, or a Record Details widget.
- Full Audit Trail: Every AI-populated date logs as AI-driven activity in the record's audit history. Manual overrides re-attribute cleanly to the user who made the edit, preserving traceability.
- Same Workspace Governance: Requires the workspace-level AI Field Agents toggle. Inherits the workspace's Internet Search setting when relevant. Uses the connection registry from the July 14 Managed Connections release for provider/model routing.
How It Works
- Open a Date field's Field Settings and switch to the AI Field Agent tab.
- Toggle Enable AI Field Agent. Compose the prompt referencing other fields on the record with the field-variable selector (for example: "Compute the SLA target resolution date based on {{Priority}}, {{Reported Date}}, and the standard escalation policy in the attached SLA document").
- Pick a Connection from the dropdown of admin-enabled connections for AI Field Agent on the current solution.
- Optionally enable Automatic runs so the date re-generates when the triggering fields change; leave off for manual-only runs.
- Save. On the Record Page or Grid view, run the agent manually or watch it populate automatically as record context evolves. The generated date appears in the Date field and the activity log flags the change as AI-generated.
Requires the workspace-level AI Field Agents toggle in Workspace Administration → AI Control Center → AI Field Agents. Available on all plans.
new
Mobile
Mobile: Chart Widget Support

The Chart View widget now renders on SmartSuite Mobile with full desktop feature parity — grouping, sorting, filters, benchmark lines, and chart totals — across every chart type the widget already supports (Bar, Column, Line, Area including Stacked variants, Pie, Donut, Bubble, Scatter, Heatmap). Regional sales managers reviewing performance against benchmarks while traveling, executives checking KPI dashboards before meetings, and field supervisors monitoring grouped inspection data from job sites all get the full charting toolkit on phone and tablet.
Key Highlights
- Full Chart-Type Coverage on Mobile: Bar, Column, Line, Area (including Stacked and 100% Stacked), Pie, Donut, Bubble, Scatter, and Heatmap all render natively on iOS and Android. No more falling back to Grid View when a chart is the right visualization for the audience.
- Desktop Configuration Carries Over: Grouping, sorting, filtering, benchmark lines, and chart totals configured on the Saved View on Web all apply automatically on mobile. Dashboard builders don't design a separate mobile chart.
- Chart Totals on Mobile: Up to three configured totals render consistent with the desktop treatment — useful for KPI displays where the total or comparison number is the actual headline.
- Filter Widget Support: Attached Filter widgets on the dashboard narrow the chart view on mobile just like they do on desktop, so viewers can slice data on the go.
- Interaction Preserved: Tap data points or bars to surface values, swipe between widgets across the dashboard, and use grouping expansions where the chart type supports them.
How It Works
- Update to mobile app version 3.12 (MOB 166) or later on iOS or Android.
- Open a Dashboard that already has a Chart View widget configured on desktop (the widget's Saved View, chart type, groupings, sorts, filters, benchmark lines, and totals are all read from the existing configuration — nothing separate to set up for mobile).
- Chart renders natively on the mobile Dashboard with the desktop configuration applied.
- Tap chart data points or bars for values; use any attached Filter widgets on the dashboard to narrow the view; swipe to move between widgets on multi-widget dashboards.
With Chart View joining the mobile-supported widget set — and following the July 20 addition of Calendar View and Card View, SmartSuite Dashboards are closer than ever to full mobile-desktop parity.
new
All Plans
Data & Field Management
Forms: Support for Date Range Field

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.
Key Highlights
- First-Class Form Input: Date Range fields now appear alongside every other supported field type when building a Form, with no extra configuration needed beyond adding the field to the underlying table.
- Display Format Honored: The form field renders using whichever Display Format (Compact, Standard, Long, or Pill) is set on the underlying Date Range field. No separate form-only styling to configure.
- Time Entry Support: If the underlying Date Range field has time enabled, respondents can enter both date and time components — otherwise it's date-only.
- Works in Read-Only Forms: Date Range fields display correctly in read-only form contexts, so confirmation and review flows work as expected.
- Same Auto-Fill Invariant: If a respondent enters only a start or only an end value, the missing side auto-fills to the same value, preserving the invariant that Date Range fields always carry both endpoints.
How It Works
- Add or open a Date Range field on the source table (from Grid View column menu, or Record View add-field control).
- Open the Form Builder for that table and drag the Date Range field into the form layout, or turn it on via the field toggle if you're editing an existing form.
- Save the form. Respondents see a Date Range control on the live form, matching the Display Format configured on the underlying field.
- Submitted responses populate the Date Range field on the record as expected, including in Timeline View, which relies on Date Range values.
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.
new
All Plans
Data & Field Management
Linked Records: Sticky Add New Button

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.
Key Highlights
- Always-Visible Add New Button: The + Add New button now anchors to the bottom of the Linked Records grid, staying visible while users scroll through the linked-record list. No more scrolling to the bottom of a long grid to add another record.
- Fixes Group By Blind Spots: When Group By is enabled with a non-editable grouping field, users can now add new records via the sticky footer. Previously this scenario blocked new-record creation entirely.
- Two Ways to Add When Group By Is Editable: When grouping is by an editable field, users choose between adding a new record within a specific group (via the group-scoped add control) or at the outer level (via the sticky footer). Both surfaces coexist cleanly.
- Applies to Record Page and Record Details Widget: The sticky footer renders on both the main Record Page inline-editing surface and inside the Record Details Widget, matching wherever inline editing is enabled.
- Grid Display Format Only: The sticky footer is scoped to Linked Records using the Grid display format with Allow creating new records inline set to True. Non-Grid display formats and read-only Linked Record grids are unchanged.
How It Works
- Open a Linked Record field's settings and confirm Grid display format is selected, with Allow editing records inline and Allow creating new records inline both enabled.
- Open a Record Page (or a Record Details Widget) where that Linked Record renders as a Grid.
- Scroll through the linked-record list. The + Add New button stays fixed at the bottom of the grid regardless of scroll position.
- Click Add New. If the grid is grouped by an editable field, the new record is added at the outer level; you can also use the group-scoped add control to add inside a specific group. If the grid is grouped by a non-editable field, the sticky footer is the only add-new surface, but it works.
- Fill in the row values inline. Changes save immediately without needing to save the parent record.
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.
new
All Plans
Data & Field Management
Linked Records: Grouping for Record Selector

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.
Key Highlights
- Grouping as a First-Class Selector Control: Solution Managers can now configure Group By on the Record Selector alongside Fields, Sort, and Filter — a full set of view controls on the record-picking surface, not just the field-display surface.
- Multiple Levels of Grouping: The Record Selector supports multiple grouping levels, each with its own sort order, defaulting to whichever collapsed-or-expanded state the Solution Manager configures.
- Search Plays Nicely With Groups: When users search inside the Record Selector, matching results render within their groups and any collapsed groups containing matches auto-expand — no need to browse the tree by hand.
- Solution Manager Configuration, User Consumption: Only Solution Managers can set the grouping configuration; regular users see the configured selector and pick records without needing to understand or reconfigure anything.
- Independent From Field-Display Grouping: The Record Selector's grouping is separate from Group By on the Linked Record's display grid — Solution Managers can group the selector one way and the display grid another, or use both.
How It Works
- Open a Linked Record field's settings as a Solution Manager. Under the Record Selector configuration, find the new Group By control.
- Pick the field to group by, the sort order for the groups (or per level, if using multiple levels), and whether groups default to collapsed or expanded.
- Save the field settings. Every user working with the Record Selector for this Linked Record field now sees the grouped view.
- As a regular user, click into a Linked Record cell to open the Record Selector. Records appear grouped as the Solution Manager configured them.
- Type in the search input to narrow the list. Matching records render inside their groups, and any collapsed groups containing matches auto-expand so nothing gets missed.
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.
new
All Plans
Mobile
Mobile Dashboards: Calendar and Card View Widgets

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.
Key Highlights
- Calendar View on Mobile: The Calendar View widget now renders on SmartSuite Mobile with the same date-field configuration as the desktop version. Scheduled records appear against a calendar grid that scrolls and taps cleanly on phone and tablet.
- Card View on Mobile: The Card View widget now renders on SmartSuite Mobile as an image-and-text card list that scrolls naturally on a small screen — no more falling back to Grid View when a gallery-style layout is the right presentation.
- Broader Mobile Coverage: These two widget types join Grid View, Timeline View, all chart widgets (Bar, Column, Line, Area, Pie, Donut, Bubble, Scatter, Heatmap), Summary Card, Progress Metric, Comparison Metric, Filter Widget, Countdown, World Clock, and the full set of embed widgets. The mobile dashboard toolbox is now closer to feature parity with the desktop experience.
- Same Configuration Model: No new configuration to learn — Calendar and Card View widgets configured on desktop render as expected on mobile with their existing settings, filters, and sort order. Dashboard builders don't have to design a separate mobile version.
How It Works
- Open any dashboard in the Web app you'd like to make mobile-friendly, and add or edit a Calendar View or Card View widget as you normally would.
- Configure the widget with the date field, sort order, filter conditions, and visible fields you want — same controls as any other widget on the dashboard.
- Save the dashboard. Open the SmartSuite Mobile app, navigate to the dashboard, and see the Calendar or Card View widget rendered natively.
- The widget honors the same filters and permissions on mobile as it does on desktop — no separate mobile configuration needed.
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.
new
Enterprise
Collaboration & Security
Record Page: Conditional Required Fields

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.
Key Highlights
- New Required Fields Section on Display Logic: A dedicated Required Fields area on the Display Logic tab lets solution admins define rules that make a field required when another field's value matches a condition. Same UI pattern as the existing Sections, Tabs, and Fields rule types.
- Immediate Enforcement, Not Just On Save: Rules become effective as soon as the triggering field value changes on an open record, before the record is saved. Users see the required-state indicator update in real time and can complete the record before submission.
- Visibility Wins: If a field is hidden by a Display Logic rule (whether directly or because its tab or section is hidden), the conditional-required rule doesn't fire against it. Hidden fields are never treated as required, no matter what the require rule says.
- One Rule Per Field: Every field can have at most one conditional-required rule. System fields (Record ID, First Created, Followed By, and so on), calculated fields (Formula, Lookup, Rollup, Count, Autogenerated Title), and fields already marked as required in the field settings are excluded from the rule builder.
- Same Tab-Level Validation UX: When a save action generates multiple required-field errors, the Record Page shows the count of empty required fields per tab, exactly matching the existing required-field validation model. No new failure UI to learn.
How It Works
- Open a table's field settings and go to the Display Logic tab. The new Required Fields section sits alongside the existing Sections, Tabs, and Fields rule categories.
- Click Add Rule, pick the field that should become required, define the condition against another field's value (Status equals Resolved, Priority equals Critical, Result equals Pass), and save the rule.
- The rule-indicator icon appears on the field in the Fields tab so admins can see at a glance which fields have a conditional-required rule attached.
- On the Record Page, as users edit a record and change the triggering field's value, the conditionally-required field shifts to a required state immediately. If they try to save without providing a value, validation errors surface per tab.
- Pair conditional-required rules with existing conditional-display rules for the full picture: hide a field until it's relevant, then require it once it is.
Available on Enterprise and Signature plans.
new
All Plans
Collaboration & Security
Manage Members: Access Level Overview

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.
Key Highlights
- Solution Access Modal from Manage Members: A new option under each member's three-dot menu opens a modal showing every Solution the user can reach with the highest combined (personal + team) permission — no more reconstructing effective access by hand.
- Two Modes, One Modal: Solutions listing is the default; click a Solution to switch to Tables listing for that Solution, complete with breadcrumbs showing the selected User and Solution.
- Personal-vs-Team Source Indicator: Every permission value shows whether it was granted directly at the personal level or inherited through a Team, so admins know exactly where to go to change it.
- Filter, Search, and Switch Users In-Place: User Selector to jump between users without closing the modal, Permission Selector to narrow to a specific access level, name search across the current listing, all working together.
- Click-Through to Permissions Editors and CSV Export: Click any permission value to open the corresponding Solution Permissions or Table Permissions modal and edit access in place; the listing refreshes immediately when the editor closes. Export the current filtered listing to CSV for evidence or offline review.
How It Works
- Open Workspace Administration → Manage Members. Find the user you want to audit and open their three-dot menu; pick Solution Access.
- The Solution Access modal opens in Solutions listing mode: every Solution the user can reach, sorted A-Z, with the highest combined permission and an icon showing whether that permission came from a personal grant or a Team grant.
- Filter the listing with the Permission Selector (defaults to All Permissions), search by Solution name, or switch to a different user via the User Selector without closing the modal.
- Click a Solution to drill into Tables listing mode for that Solution: same layout, same filters, breadcrumbs indicating the selected User and Solution.
- Click any permission value to open the Solution Permissions or Table Permissions modal. Adjust the permission; when the modal closes, the listing refreshes to reflect the new effective access immediately.
- Export the current listing to CSV via the Export control for offline record-keeping or audit-evidence attachment.
new
All Plans
SmartSuite AI: Managed Connections

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.
Key Highlights
- Centralized Connection Registry: A new Providers and Models section under Workspace Administration → AI Control Center lets admins add, edit, test, disable, and delete AI provider connections in one place. API keys are encrypted at rest and only visible to workspace admins.
- Solution and Feature Scoping: Every connection is scoped to all solutions or a specific list, and to AI Workflow Agent Action, AI Field Agent, or both. Governance-restricted solutions can be limited to specific approved connections without the risk of stray keys leaking across projects.
- Test Before Saving: Every new or edited connection runs through a live test-connection step (system prompt sent to the provider, response displayed) before the connection saves. A failed test blocks the save; a successful one gates the Next button.
- Usage and Activity Log: Each connection has a Used-In tab showing every automation and Field Agent consuming it, plus an Activity History tab with every API call's status (success or error), filterable and sortable. Three-year retention on activity records.
- Trial Connection Built In: New workspaces get a pre-configured SmartSuite Trial Connection (OpenAI GPT 5.1, 100 free requests) so evaluators and new customers can experience the full AI feature set without configuring their own key first.
How It Works
- A workspace admin opens Workspace Administration and finds the new AI Control Center section with Providers and Models inside.
- Click Edit to open the Providers and Models modal; click Add Connection to start the setup wizard. Pick a provider, enter the required credentials, name the connection, optionally add a description, and set Enable Internet Access for models that support web browsing.
- Click Test Connection. The system sends a test system prompt to the provider and shows the response; a successful test unlocks the Next button.
- Pick a scope of solutions (All Solutions by default, or Only Selected with a solution picker) and pick which features can use this connection (AI Workflow Agent Action, AI Field Agent, or both).
- Save. Automation builders and Field Agent authors now see the connection in their Select Connection dropdown wherever it matches the solution and feature filter, no key re-entry required.
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.
Load More
→