Changelog
Follow up on the latest improvements and updates.
RSS
new
All Plans
Data & Field Management
Restore Solutions from Recycle Bin
Solutions deleted in error can now be restored from the Recycle Bin, complete with every child object and even the Linked Record relationships to other Solutions. Solution Managers running short-lived Solutions for projects, audits, or pilots gain a safety net that previously required IT-level intervention or a from-scratch rebuild.
Key Highlights
- Solution-Level Restore: Solution Managers and Account Admins can restore a deleted Solution from the User Profile Recycle Bin in a single click.
- Full Child Recovery: Restoring a Solution brings back all its applications, automations, reports, records and comments, fields, My Work items, and dashboard widgets.
- Cross-Solution Link Repair: Linked Records pointing from other Solutions get reconnected automatically when both Solutions are present, with Mirrored Links and dependent Lookups restored end-to-end.
- Disambiguating Names: Restored Solutions get a '(Restored)' suffix, with a number appended if multiple restores happen for the same name.
- Safe Bin Behavior: Child elements that were already in the bin before the Solution was deleted return to the bin on restore and continue counting their original deletion timer rather than resetting.
How It Works
- Solution Managers and Account Admins access the Recycle Bin from their User Profile to see deleted Solutions alongside other deleted items.
- Click Restore on a deleted Solution to begin the restore; the system walks the Solution's child objects and Linked Record relationships before completing.
- For Linked Records pointing to other Solutions, the system checks whether the target is still available: if yes, the link is restored along with the Mirrored Link and dependent Lookups; if no, the Linked Record remains in text mode until the target is restored.
- Permanent deletion is also available from the bin for Solutions that should be cleaned up rather than restored.
Use this to recover from accidental deletions without rebuilding from a backup, especially in environments where Solution Managers create short-lived Solutions for project planning, compliance audits, or feature pilots.
improved
All Plans
AI Field Agent: Manual Stop
AI Field Agents in the middle of generating can now be stopped manually. When generation runs long or gets stuck in a perpetual loading state, click Stop Agent next to the field to immediately return it to its regular state and discard the in-flight LLM response.
Key Highlights
- Stop Agent Button: A new Stop Agent button appears on every AI Field Agent currently in the generating state, with a 'Stop agent' tooltip on hover.
- Immediate Return: Clicking Stop returns the field to its regular state without waiting for the LLM response, so the user can continue working.
- Discarded Response: Any LLM response that arrives after a stop is discarded and does not write to the record, so the field stays in the state the user left it in.
- Configuration Preserved: Stopping an agent does not change its configuration; the prompt, the model, and any toggles stay in place for the next run.
- Free Runs Counted: Cancelled executions still count against the workspace's Free Runs pool, since the LLM call has already been issued at the point of cancellation.
How It Works
- When an AI Field Agent enters the generating state, a Stop Agent button appears next to the field.
- The button is available wherever the agent renders: inline editing in Grid View, the Record Page, and the Record Details Widget.
- On click, the field reverts to its regular state immediately, abandoning the in-flight LLM call from the user's perspective.
- The system listens for the LLM response in the background and discards it on arrival; the record value is never updated by a cancelled run.
- The agent's configuration is untouched, so the next manual run or automatic trigger executes normally without reconfiguration.
Use this when an AI Field Agent is taking too long, when a slow model is blocking inline editing, or when an agent appears stuck and you need to recover the field without disabling the agent.
new
All Plans
UI & Reporting
Internal Forms
Forms now support an Internal mode designed for authenticated, in-app submissions. ITSM service desk teams, GRC compliance leads, and any builder running an internal intake workflow can collect data with full awareness of the signed-in user, complete with field-level permission enforcement and submitter attribution captured on the record.
Key Highlights
- Two Operational Modes: Every form can run as Internal (in-app, authenticated) or Shared (public link), independent of one another, with both modes available on the same form simultaneously.
- Authenticated Submissions: Internal forms know which SmartSuite user is filling them out, opening the door to user-aware logic, permission enforcement, and per-user defaults.
- Permission-Aware Fields: Field-level view and edit restrictions apply to internal forms; fields a user cannot view are hidden, and fields they cannot edit are read-only.
- Service Desk Intake: ITSM teams can build authenticated intake forms that capture the requester's identity automatically, with no manual entry of who submitted.
- Submitter Attribution: An extended Created By model captures the submitter, the form title, and the source type, displayed as 'Created by [Member] via [Form Title] Form' in the activity history and on the record page.
How It Works
- Open any form's configuration; Internal mode is automatically available without any toggle, and the Shared (public link) state remains independent.
- Internal forms can be opened from a Form View inside the app or launched from the new Open a Form button action on dashboards.
- When a user opens an internal form, the system loads it inside the SmartSuite app context, applies their permissions, and pre-resolves any user-aware defaults.
- On submission, the record is created with the submitter as Created By, plus a Source Type (Form) and Source Title (the form's name) for full traceability.
- Automation triggers that listen for 'When a form is submitted' fire for both internal and shared submissions, so existing automations work unchanged.
This release is the foundation for richer in-app form workflows, underpins the new Open a Form button action shipping alongside it, and the Created By extension carries forward to upcoming workflow actions like MS Teams Actionable Notifications.
new
All Plans
Automations: Dynamic values in URLs
The Rich Text URL control now accepts dynamic field values, so URLs across SmartDoc, automation messages, and embedded rich-text content can resolve to the right record at runtime instead of pointing to a single hardcoded destination. ITSM teams sending MS Teams Actionable Notifications, GRC teams linking evidence pages to source records, and any builder embedding contextual links in rich text get a foundational upgrade.
Key Highlights
- Dynamic URL Composition: Highlight text in any rich-text field, click the URL control, and insert a field placeholder using the same picker that powers automation message bodies.
- ITSM Notification Foundation: The Open Record button on the upcoming MS Teams Actionable Notification action uses this capability to link straight to the relevant ticket or change request.
- SmartDoc Live Links: Rich-text URLs in SmartDoc fields can now resolve to the correct record on every view, no manual editing per record required.
- Single Underlying Control: The same dynamic URL control works everywhere the Rich Text component is used, so a builder learns the pattern once and applies it across surfaces.
- Backward Compatible: Existing static URLs continue to function unchanged, so no automation or SmartDoc content needs to be migrated.
How It Works
- Highlight the text you want to link in any rich-text field, click the URL control, and the URL input now supports the standard field picker.
- Use the field picker to insert placeholders that the system resolves to the live value at runtime when the automation runs or the SmartDoc renders for a record.
- Static URLs remain valid input; you can mix static and dynamic segments in the same URL when the destination needs both.
- The change applies wherever the Rich Text URL control appears, giving consistent behavior across automation messages, SmartDoc fields, and any embedded rich-text input.
Pair this with the upcoming MS Teams Actionable Notification action to send approval requests that land recipients on the exact record that triggered the workflow.
improved
All Plans
Calendar View: Support for Cross-Solution Calendars
The Calendar View can now combine public calendars from multiple Solutions into a single primary calendar. PMO leaders coordinating across teams, operations leads building unified availability views, and anyone who has been maintaining duplicate calendars to bridge Solutions can consolidate to one rolled-up view.
Key Highlights
- Cross-Solution Roll-Up: Pull public calendar views from any Solution you have access to into a single primary calendar, instead of being limited to one Solution at a time.
- PMO Portfolio View: Combine engineering release schedules, marketing campaigns, and product launches in one calendar to coordinate across functions.
- Operations Visibility: One calendar can render team availability across HR, customer success, field service, and any other Solution holding scheduled work.
- Permission Aware: Each rolled-up calendar respects the source Solution's permissions, so users only see events from Solutions they have access to.
- Source-Of-Truth Editing: Drag, drop, resize, and inline edits flow back to the original Solution rather than creating cross-Solution copies, keeping each calendar's source clear.
How It Works
- In Calendar View configuration, the calendar source picker now shows public calendar views from all Solutions you have access to, not just the current Solution.
- Pick any combination of public calendars and the resulting Calendar View renders them together with the existing scale, drag-and-drop, and event-editing behavior.
- Events keep the visual identity of their source calendar (color, icon) so the rolled-up view stays scannable even with many sources.
- Permission checks happen per source calendar at render time, so a user without access to one of the source Solutions sees the rest of the calendar normally.
- Existing single-Solution Calendar Views continue to work unchanged; cross-Solution support is additive.
Use this to consolidate scheduling visibility across teams and Solutions, especially in PMO portfolio coordination, operations planning, and any role that has to look across multiple Solutions to plan their day.
new
All Plans
Automations & Integrations
Automations: Support for Team Field
The new Team field works end-to-end in automations: triggers, actions, loops, and notification routing. Service desks running approval workflows, GRC teams notifying ownership groups of compliance events, and any automation that previously had to fan out to individual members one at a time gets a more direct path.
Key Highlights
- Team as Action Input: Set a Team field's value from a static team name, a lookup, a formula, or any text source the field picker accepts.
- Team-to-User Mapping: Setting an Assigned To field from a Team field writes all team members to the destination, with the first member used when the destination is single-value.
- Smart Email Routing: Send Email actions go to the Team Email when set, or fall back to deduplicated individual member emails when targeting multiple teams.
- Notification Fan-Out: Send Notification actions reach every team member directly without per-member configuration, mirroring how individual assignment notifications work today.
- Loop Support: Use a Team field in a Loop step to iterate over team members and run per-member follow-up actions like creating tasks, sending personal updates, or generating reports.
How It Works
- In any automation action that targets a Team field, use the standard text input control to map the value, with field picker support for dynamic resolution.
- The Send Email action checks each target team for a Team Email, with the team email handling distribution when present and individual member emails sent (with deduplication across multiple selected teams) when not.
- Inactive or deleted teams encountered at runtime are skipped silently, consistent with how Assigned To handles deactivated members, so workflows stay running rather than failing on stale references.
- Validation respects table permissions: a team without explicit access to the target table is skipped at runtime rather than written, with the skip recorded in run history.
- Triggers fire when a Team field value changes, the same way they do for any other tracked field.
This release closes the loop on the Team field type: configure it once on the table, and every automation surface treats it as a first-class assignment source.
new
All Plans
Data & Field Management
Introducing the Team Field
A new Team field type joins Assigned To as a first-class way to allocate work in SmartSuite. Service desks routing tickets to a service team, change-approval boards routing to an oversight team, and PMO leaders splitting work across squads can now treat teams as the unit of assignment, with full permission inheritance.
Key Highlights
- New Team Field: Pick Team from the Project Essentials field category, with single or multi-value selection and the same display options as Assigned To.
- Permission Inheritance: Team members get Contributor, Assignee, or Assignee+ access to records based on their team's table permission, exactly mirroring how individual assignment works today.
- ITSM Service Desks: Route a ticket to its target service team and every member of that team gains the right access automatically, with no per-user grant management.
- Team Email Routing: A new optional Team Email property handles notifications cleanly, sending to one address with the team's distribution list handling delivery, falling back to individual member emails when no team email is set.
- 'My Team' Filter: Build views scoped to 'Where Responsible Team is My Team' once and every user sees the records assigned to their own teams without per-user filter duplication.
How It Works
- When configuring a field, choose Team under Project Essentials, set single or multi-value, and pick from the list of teams with access to the table.
- Notifications honor the Team Email when set, or send to individual members with deduplication when the same person belongs to multiple selected teams.
- An Assigned To field can optionally link to a Team field as its Parent Team, narrowing the Assigned To picker to members of the currently selected team.
- Filter operators match Assigned To, including a new 'My Team' comparison value that resolves to the current user's team memberships at view time.
- Supported across Grid, Kanban, Form, Calendar, Timeline, Gantt, Map, and Charts, plus bulk update, import, public API, Document Designer, and formulas (as text for single-value, list for multi-value).
Use the Team field to clean up workflows that previously hacked around assignment via tags or duplicate Assigned To fields, especially in service desk intake, change management, and compliance ownership tracking.
new
All Plans
View Based Widgets: Support for Custom Buttons
The hardcoded Add New Record button on every view-based widget has been replaced with a configurable button bar that supports up to ten custom buttons. Service desks, compliance boards, and project dashboards built on Grid, Card, Calendar, Timeline, Chart, or Gantt widgets get full button configurability without rebuilding anything.
Key Highlights
- Configurable Button Bar: View-based widgets share the same button component used in Button Row widgets, replacing the old hardcoded button.
- Up to Ten Buttons: Configure as many as ten buttons per widget, with the first two visible and the rest under a '...' overflow.
- Broad Widget Support: Grid, Card, Calendar, Timeline, Chart, and Gantt widgets all pick up the change in the same release.
- Service Desk Friendly: ITSM teams can place Create Ticket, Open Form, Open URL, and Run Script buttons side by side on a single widget.
- Safe Migration: Existing widgets with Allow Inline Edit or Allow Edit enabled get an automatic Create-a-Record button preserving the previous label, color, and target table, so no flows break.
How It Works
- Open a view-based widget's configuration to access the new Buttons section, where you can add, remove, reorder, and configure each button.
- Each button supports the standard properties: Label, Icon, Color, Tooltip or Description, Ask for Confirmation, and Action.
- Supported actions include Open URL, Create a Record (with default values), Open a Form, and Run a Script, identical to Button Row buttons.
- During the upgrade, the system migrates existing buttons automatically: Allow Inline Edit and Allow Edit settings keep their other behaviors but no longer control the Add Record button.
- Chart Widgets do not get a migration button by default, since they did not previously expose Add Record.
Combine this with Open a Form to build dashboards where every common workflow is one click away from the right view.
new
Mobile
Mobile: Timeline Widget
Timeline Widgets embedded in dashboards now render natively on the SmartSuite mobile app, with the same layout, scale options, and filter behavior as desktop. PMO leaders, portfolio managers, and operations teams keep one dashboard for everyone and trust that the experience matches across devices.
Key Highlights
- Full Mobile Rendering: Timeline Widgets show the complete timeline layout on phones and tablets.
- Dashboard Filter Support: Existing Filter Widget links to a Timeline Widget continue to work, narrowing the timeline by team, status, or release window the same way they do on desktop.
- PPM-Ready: Portfolio dashboards, sprint trackers, and operations coordinators get a consistent experience across devices.
- Touch Controls: Pinch to zoom, drag to pan, and tap a record bar to open the record detail in mobile context.
- Permission Aware: Dashboard edit permissions and record-level permissions apply on mobile the same way they apply on desktop.
How It Works
- Open any dashboard that contains a Timeline Widget on the mobile app to see the new rendering.
- Existing widget configuration carries over, including the Default Scale, Allow Inline Edit, Display Toolbar, and Display Records Listing settings.
- The Scale control collapses into a dropdown when the widget renders in a narrow column, mirroring the desktop responsive behavior.
- Tap any record bar to open the record detail panel for inline edits when dashboard and record permissions allow.
- Dashboard owners' settings changes flow to the backend the same way they do on desktop; non-owner viewers see the configured state without persisting their own changes.
Update the SmartSuite mobile app to the latest version to see Timeline Widgets render in full.
new
All Plans
Mobile
Mobile: Timeline View
Timeline View now runs natively in the SmartSuite mobile app, with the same layout, scale options, and inline edit behavior as the desktop client. Project managers, PMO leads, and any team running a Timeline View can review schedules and milestone progress from a phone or tablet without losing fidelity.
Key Highlights
- Full Mobile Parity: Open any Timeline View directly from the mobile app, with the same fields, dependencies, and color coding as on desktop.
- PPM Ready: Portfolio reviews, release planning, and milestone tracking work the same way on a phone as they do on a laptop.
- Configurable Scale: Switch between Hours, Days, Weeks, and Months from the mobile view's scale control, defaulting to Days.
- Touch-Optimized: Pinch to zoom across time, drag to pan, and tap any record bar to open the record detail in mobile context.
- Permission Aware: Field-level and record-level permissions apply the same way on mobile as they do on desktop.
How It Works
- Open a solution that has a Timeline View configured and tap the view selector to switch to it.
- The view renders a touch-friendly timeline layout, automatically adapting controls for narrower screens.
- Pinch and drag gestures replace the desktop scrollbar and zoom controls; the toolbar collapses into a dropdown when space is tight.
- Tap a record bar to open the record detail panel for inline edits when permissions allow.
- All changes flow back to the underlying table the same way they do on desktop, so the team sees updates immediately.
Update the SmartSuite mobile app to the latest version to access Timeline View on the go.
Load More
→