Feature Requests

I want to create an MCP connection between SmartSuite and Claude Cowork. While SmartSuite provides an open-source MCP server that runs locally, it would be more convenient to have a native connector within SmartSuite. This would simplify the process of setting up the connection and enhance integration capabilities.

I have a complex solution with many fields, formulas, and automations, making it difficult to understand how everything connects. It would be beneficial to have a feature that allows exporting a full solution schema, including formulas, automations, and field linkages, to better understand the data structure and relationships.

I wanted to export all the data in one of my solutions into a single spreadsheet, with each table in the solution having its own tab. Currently, I have to export each table individually and manually combine them into one workbook with separate tabs. It would be much more efficient if there was an option to export the entire solution into one spreadsheet with tabs per table directly from SmartSuite.

I want to set up an automation where a different action is triggered if the condition cannot be met. Currently, SmartSuite automations only run the action when the condition is true, and there isn't a built-in 'else' action in the same automation. It would be beneficial to have an 'else' option to handle the opposite case within the same automation.

I need to send a Slack notification when a certain number of records in the status 'onboarded' is reached. Currently, this isn't possible natively unless the single select is changed to a Linked Record. I would appreciate the ability to take conditional actions based on the number of records found in an automation, without relying on third-party services like Make or Zapier.

We have over 70 users that use our SmartSuite solution, and we wish to have finer control who can add Public Views. This would help to avoid people accidentally adding new Public Views and clogging up the Public Views panel. Currently, we can only Lock existing Public Views, and anyone can add their own Public View.

SmartDoc tables currently lack basic editing actions. Adding a row requires opening the 3‑dot menu, and there is no way to move a row up or down. This makes tables feel rudimentary compared to standard table widgets used in most document editors. Requested improvements: Add a keyboard shortcut to insert a new row at the bottom of the table. Allow rows to be moved up or down (drag or keyboard shortcut). Provide basic table editing actions similar to common document/table editors. Business use case: When building long SmartDoc tables (notes, logs, documentation), repeatedly opening menus slows editing. Basic row manipulation would make tables much more practical for everyday use.

The goal of this feature is to add an if/else statement in order to do différents actions, depending previous actions like a search. For example, if a find return a record, I will update it, if it does not find a record, I will create a new one.

Admin users have come to expect to have a separate place where they can manipulate their admin configurations. Creating and managing fields from the end-user field is good but you will win technical folks over with a more administratively focused interaction option.

Can there be an error message or an "are you sure?!" prompt before deleting a field that's involved in automations or dashboards? It would be nice to see the downstream effects of seemingly harmless field deletion :)