Build a Business Documentation Hub in SmartSuite from Scratch

Executive overview

Business knowledge trapped in employees' heads is a liability — when people leave, that knowledge walks out with them. The fix is a centralized documentation hub where SOPs, wikis, and market research live in a shared, searchable system. SmartSuite provides a flexible, database-driven workspace that makes this practical even for non-technical teams. This tutorial walks through building an SOP database from a blank solution, customising fields to fit documentation rather than task management, and extending the structure to cover all knowledge types.

Setting up the SmartSuite solution

• Create a new blank solution called Documentation — templates don't yet cover this use case
• Add a brain icon and custom colour for quick visual identification
• Each solution holds multiple apps (databases); each app holds records
• Start with one app named SOP — the core how-to library for the business

Designing the SOP database

• Rename the default view to "All SOPs by Department" to make navigation intent clear
• Add two placeholder records ("How to make toast", "How to butter toast") to test the structure before adding real data
• Delete irrelevant default fields: Priority and Due Date don't apply to reference documents
• Rename the Assigned To field to SOP Owner — the person responsible for keeping the SOP current
• Enable "display in My Work" so owners get reminded when an SOP needs updating
• Rename the Status field to SOP Condition with values: Not Started, In Process, Needs Revisions, Perfect
• Rename the title field to SOP Title and require unique entries for clean reporting

Writing actual SOPs inside records

• Repurpose the default description field into a Procedure field using the SmartDoc field type
• SmartDoc gives rich formatting — numbered steps, tables, images, collapsible sections
• The collapsible layout keeps records clean and scannable for new team members
• Add a Departments multi-select field (e.g., Ops, Marketing, Finance) with fixed choices to prevent ad-hoc category sprawl
• Use checkbox display style for departments so they're easy to tick inside each record

Organising SOPs by department

• Apply a Group By: Departments setting on the view — records appear under each relevant department
• Multi-select records appear in every matching group, which is intentional for cross-functional SOPs
• Switch between grid, card, and other layouts depending on how teams prefer to browse
• Each group can be collapsed for a tidy, directory-style overview

Filling the hub with real content

• Add a record for every SOP that needs to exist — even blank stubs — to make gaps visible
• Paste or build your SOP template inside each Procedure field to standardise the format
• New hires can self-serve from the hub instead of waiting for tribal knowledge hand-offs

Extending beyond SOPs

• Add more apps inside the same Documentation solution: Market Research, Wikis, industry reading lists
• Build alternate views — group by SOP Condition to let an ops manager monitor documentation health
• Add dashboards or charts to visualise how many SOPs are complete vs. in progress
• The hub outlives any individual employee, founder, or owner