The Files and Images field can now cap how many attachments a single field instance will accept. Solution admins turn on "Limit the number of allowed attachments" in field settings and set the maximum — the field then refuses uploads beyond that count. Contract tables enforcing exactly one signed PDF per record, product catalogs capping reference images at a fixed number, HR employee profiles allowing only one headshot, and any workflow where the attachment count is a first-class part of the data model get field-level enforcement.

Available on all plans; existing Files and Images fields keep their prior unlimited behavior until an admin explicitly opts into the limit.

The Record Selector on Linked Records now opens as an inline dropdown by default instead of a full modal. Picking from a short list of existing records to link takes one click and no modal round-trip; the modal experience is still available for longer lists and advanced browsing. Service desks assigning a ticket to one of a small set of Change Requests, sales teams linking a deal to an Account from a short recent-account list, GRC compliance teams connecting a control test to a filtered short-list, and PMO leads connecting a task to a Sprint from a handful of active options all get quicker linking on the common case.

Third refinement in the Linked Records 2.0 arc, following the Sticky Add New button and Grouping for Record Selector from Jul 27.

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.

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.

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.

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.

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.

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.

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.

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.

Requires the workspace-level AI Field Agents toggle in Workspace Administration → AI Control Center → AI Field Agents. Available on all plans.

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.

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.

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.