TL;DR: Please give us a true Folder field and Folder View so we can build record-based wikis, SOP libraries, and team hubs with nested navigation, while keeping all the strengths of SmartSuite records. See attached mock-ups. In the recent “What’s New in SmartSuite” webinar, Jon referenced “Coda-style documentation.” I think that is exactly the right direction. My suggestion is to take that idea one step further in a SmartSuite-native way: instead of making documentation live mainly as separate Document Views, allow records themselves to be organized and browsed in a Coda-style folder/document layout. SmartSuite’s new Document Views are a helpful step toward creating wiki-style content, SOP libraries, team hubs, and internal knowledge bases. However, Document Views currently are more like standalone pages than true SmartSuite records. They can go into top-level folders, but sub-folders cannot be created. They also do not appear to have the same protections and capabilities that make SmartSuite records so powerful, such as record history, recycle bin recovery, flexible movement between tables or solutions, normal field structure, automations, permissions, comments, dashboards, reporting, and API access. My suggestion is to create a new Folder field type, along with a dedicated Folder View. The Folder field would allow users to build a nested folder structure inside a table, then assign each record to a folder. The Folder View would display the folder tree on the left side, similar to a wiki or document workspace, and show the selected record’s SmartDoc/content area on the right. This would give SmartSuite users the best of both worlds: A simple, familiar folder/subfolder navigation experience The full power and safety of real SmartSuite records This would be extremely useful for: Company wikis SOP libraries Employee handbooks Training materials Project documentation Department knowledge bases Policy manuals Customer or vendor documentation EOS/process documentation The key point is that users should not have to choose between a nice document-navigation experience and the power of SmartSuite records. A Folder View would make SmartSuite much stronger as a knowledge management platform without weakening the database-first structure that makes SmartSuite so useful. For example, a company could have a “Pages” table where each record is a real page, with fields for owner, department, status, review date, tags, related process, attachments, comments, and permissions. The Folder field would simply control where that page appears in the navigation tree. That would allow teams to build something that feels as easy to browse as Coda, Notion, or a traditional wiki, while still keeping everything inside SmartSuite’s record-based architecture. This would also be better than relying only on Document Views, because records are safer, more flexible, more reportable, and easier to connect to the rest of a SmartSuite solution.
