Changelog

Follow up on the latest improvements and updates.

RSS

Whats New page - Team - Support Mention
Comments and Checklist Items now support Team assignments and Team @-mentions, extending the Teams Field infrastructure from field-level assignments into the two most conversational surfaces in SmartSuite. Assign a Team to a comment or checklist item instead of picking a specific member, or @-mention a Team inline; every Team member gets an in-app notification and (if a Team Email is configured at the workspace level) one email goes to that address instead of individual member emails. ITSM service desks routing tickets to on-call teams, GRC compliance teams assigning control-review checklists to review committees, PMO leads @-mentioning cross-functional teams in project discussions, and HR teams distributing onboarding checklists across a Team all get first-class Team routing.
Key Highlights
  • Team Assignments on Comments and Checklists: Assign a Team to a comment or checklist item exactly the way you'd assign a member. Every Team member receives an in-app notification; email routing follows the workspace-level Team Email setting (single address if configured, individual members if not).
  • Team @-Mentions on Comments and Checklists: Type
    @
    followed by a Team name in a comment or checklist item; the mention resolves to the whole Team with matching notifications. Notification wording distinguishes mentions from assignments ("mentioned {Team} team" vs "assigned {Team} team").
  • Same Governance as the Teams Field: Only active, non-deleted Teams that currently have Contributor or Assignee access to the record appear in the picker or @-mention list. Deleted or Inactive Teams are filtered out; the "Everyone" pseudo-team is never available.
  • Team Email Deduplication: If a Team has a Team Email configured at the workspace level, that single address gets the email — no individual member emails. Multi-team memberships deduplicate cleanly so users aren't double-emailed when a Team Email address is in play.
  • Full Audit Trail: Team assignments and mentions log in the record's activity history the same way Member assignments and mentions do — preserving traceability for compliance, incident post-mortems, and audit reviews.
How It Works
  • Open a record and go to the Comments panel (or open a Checklist field and target a checklist item).
  • Type
    @
    followed by a Team name in the comment field. The picker shows Teams that are active, non-deleted, and currently have Contributor or Assignee access to the record.
  • Optionally check "Assign Comment" (or the equivalent on a checklist item) if you want the mention to be an assignment as well as a mention.
  • Send the comment / save the checklist item. In-app notifications go to every Team member; email routes to the Team Email if configured, else to individual members (capped at 50 recipients).
  • Resolve/reopen a Team-assigned comment the same way you'd resolve a member-assigned one. Team members see the resolution notification.
With Team assignments and @-mentions on comments and checklists, SmartSuite closes the gap between record-level Team routing (already available on the Teams Field) and conversation-level Team routing — the right responder can now be "whoever on this Team picks it up first" across every collaboration surface.
Whats New page - Mobile App - Internal Forms Support
Internal Forms — the logged-in-member form mode that respects field and record permissions and captures the submitting member as Created By — now work natively on SmartSuite Mobile. Previously desktop-only; this release brings the full Internal Form experience to iOS and Android with no separate configuration required. Field service techs submitting inspection forms from the job site, HR managers filing employee change requests on the road, and ITSM operators opening tickets from a phone all get the same permissioned form experience on mobile they already had on desktop.
Key Highlights
  • Full Internal Form Behavior on Mobile: Same field permissions (hidden fields removed, view-only fields read-only, editable fields fillable), same record permissions (creation gated by the member's permission on the target table, dynamic record permissions honored), same Created By attribution (the submitting logged-in member, not "SmartSuite Form") as on desktop.
  • Two Entry Points Preserved: Members open Internal Forms on mobile from either a Button field configured with the Open a Form action, or from a Form View in the mobile app — matching the desktop entry-point model.
  • Automatic Availability: An Internal Form is available for mobile use as soon as it's created. No separate mobile toggle or mobile-only configuration to manage — the same form that works internally on desktop works internally on mobile.
  • Login-Required URLs: If someone opens an Internal Form URL and isn't logged in, SmartSuite requires them to log in first — same behavior as on desktop, preserving the member-attribution guarantee that distinguishes Internal Forms from Shared Forms.
  • Independent from Shared Form Sharing: A form can be used internally on mobile even when its public sharing toggle is off. The two form modes stay independent — no need to expose an internal-only form to the public just to make it mobile-accessible.
How It Works
  • Update to the latest SmartSuite mobile app on iOS or Android.
  • Open a Dashboard, Record Page, or Form View in the mobile app that contains a Button configured with Open a Form, or navigate directly to a Form View for a form you have permission to fill out.
  • Tap the Button or open the Form View. The Internal Form loads with the member's field permissions applied, dynamic record permissions evaluated, and standard form fields presented as configured.
  • Fill in the form and submit. The record is created with the submitting member as Created By, source details captured (Form title, submission date, submission source), and any downstream "When a form is submitted" automations fire the same way they would for a desktop submission.
With Internal Forms working natively on mobile, the last major gap between mobile and desktop form workflows closes — permissioned form submission with member attribution now works wherever the submitter is.
Whats New page - Mobile App - Shared Forms
Shared Forms — public-link forms that any recipient can fill out without a SmartSuite login — now open natively inside the SmartSuite mobile app on iOS and Android instead of the mobile browser. Recipients tapping a shared form link on a phone or tablet with the SmartSuite app installed land in the app itself, keeping form submissions in one place alongside the rest of their SmartSuite work. Event teams collecting attendee registrations, HR teams running employee satisfaction surveys, and customer success teams gathering feedback from mobile-heavy audiences all benefit from the tighter mobile experience.
Key Highlights
  • Native App Handoff: When a recipient taps a public form link on a device that has the SmartSuite mobile app installed, the form opens in the app instead of the mobile browser. Matches the native experience the app already provides for Grid, Calendar, Card View, Chart View, and Internal Forms.
  • Same Submission Behavior: Public-link submissions still don't require a SmartSuite login, still track SmartSuite Form as the Created By value (matching Shared Form semantics on desktop), and still respect any form field / submission logic configured on the underlying Form View.
  • Completes the Mobile Forms Story: Shipping alongside Mobile: Internal Forms Support — together, Internal Forms (logged-in members, permission-aware) and Shared Forms (public link, browser-independent) now both work natively on the mobile app.
  • No New Configuration: Form authors don't need to enable a mobile mode. Any Shared Form with a public link automatically routes to the native app when the recipient has it installed.
How It Works
  • Publish a Form View with the Shareable Link option — same setup as before.
  • Distribute the link (email, chat, embed on a website, share in-app) as you normally would.
  • When a recipient taps the link on a phone or tablet with the SmartSuite mobile app installed, the form opens in the app.
  • The recipient fills in the form and submits. The submission is recorded exactly as before — SmartSuite Form remains the Created By value, form-submission automations fire, and the underlying Form View permissions apply.
With Shared Forms on mobile complementing this release's Internal Forms mobile support, SmartSuite's mobile Forms coverage closes — both form modes work natively on phone and tablet, and the recipient experience matches the tighter native handling the app already provides across other view types.
Whats New page - AI Field - Address FIeld Support
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.
Whats New page - AI Field - Address FIeld Support
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.
Whats New page - Mobile App - Chart View 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

Whats New page -  Form - 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

Whats New page - LR - sticky add new
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

Whats New page - LR - group by record select
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.
Whats New page  - mobile - calendar and card view support
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.
Load More