Tables

Tables — The Structured Core of Every Solution

Organize projects, controls, assets, and requests as Records in structured Tables—each with its own Fields, Views, and relationships, all connected inside one governed Solution.

What Is Tables?

A Table is the core organizational unit inside a SmartSuite Solution: it manages items of the same type—projects, tasks, controls, or assets—as a set of Records structured by Fields. It helps GRC, IT, and business operations teams keep every work item in a governed, relational structure instead of scattered spreadsheets—queryable, permission-aware, and viewable from any angle. Tables are available on every SmartSuite plan, and each Solution holds up to 25 of them, working like tabs within one connected system. Tables relate to each other through Linked Records.

One Type, One Table

Organize Every Kind of Work Item in Its Own Table

Each Table holds Records of a single type—Tasks in one, Milestones in another, Resources in a third—so structure stays clean as work grows. Tables sit as tabs within their Solution, comparable to worksheet tabs in a spreadsheet, and a Solution can hold up to 25 of them.

The result is a data model your whole team can read: one place for each kind of item, connected to everything it touches.

Structured by Design

Shape Each Table With Fields and Views

Tables store data through Fields—columns drawn from SmartSuite's 44 field types, from text and dates to formulas and file attachments—so every value lands in the right format from day one.

The same Table then displays across multiple Views: a Grid for data work, a Kanban for flow, a Calendar for deadlines—different lenses, one underlying dataset.

Table Management

Add, Duplicate, Hide, and Move Tables as Work Evolves

Add a Table with one click, reorder tabs, hide archival Tables while keeping their data on demand, or move a Table to another Solution from a dedicated menu option. Duplication offers two modes—copy all Records into the new Table, or create an empty copy that keeps only the field structure.

Reusing a proven structure for the next quarter's work takes seconds, not a rebuild.

Relational Model

Connect Tables Into One Relational Work Graph

Tables relate to each other through Linked Record fields, so one Table's Records reference—and roll up data from—another's. Contacts link to Accounts, changes link to assets, controls link to the risks they mitigate.

Shared data lives once and appears everywhere it matters, without duplicate entry.

Governed Structure

Keep Table Changes in the Right Hands

Table management actions—adding, deleting, duplicating, hiding, and moving—are restricted to Solution Creators, Workspace Administrators, and Solution Managers. General users work within Tables without restructuring them.

Teams get the flexibility to work their way, and the structure everyone depends on stays intact.

Platform Context
How GRC Teams Use

Tables

Governed workflows depend on clean structure—every control, policy, and finding in its own Table, related to everything it touches.

Control Register Structure

Keep Controls, Frameworks, Evidence, and Test Results as separate linked Tables in one Compliance Solution, so each control carries its framework mappings and test history without duplication.

Policy Lifecycle Tracking

Manage Policies in one Table and Attestations in another, linked together—each policy Record shows exactly who has attested and what remains outstanding.

Audit Lifecycle Tables

Model the audit practice as related Tables—Engagements, Requests, Findings, and Remediation—where findings link to the engagement that raised them and the controls they test.

Assessment Cycle Reuse

Duplicate a proven vendor-assessment Table as an empty structural copy each cycle, keeping the field setup while starting the period's assessments clean.

Cross-Table Reporting with Rollups

Combine Tables with Lookup & Rollup Fields to surface totals across relationships—open findings per control, or total contract value per vendor.

Works Better Together
Related Features

Governed workflows depend on clean structure—every control, policy, and finding in its own Table, related to everything it touches.

Features FAQ’s
Frequently Asked Questions About
Tables
What is a Table in SmartSuite?

A Table is the core organizational unit inside a Solution, used to manage items of the same type—projects, tasks, controls, or assets—as Records structured by Fields. Tables work like tabs within their Solution.

How many Tables can a Solution contain?

Each Solution can contain up to 25 Tables, and every Solution needs at least one. The 25-Table ceiling is a platform-wide structural limit, not a plan-tiered one.

How many Records can a Table hold?

Record capacity is set by plan at the Solution level: 5,000 Records per Solution on Team, 100,000 on Professional, and 400,000 on Enterprise. Per-Table limits are 5,000, 50,000, and 125,000 Records respectively.

Can I duplicate a Table without copying its data?

Yes. Duplicating a Table offers two modes—copy all Records into the duplicate, or create an empty Table that keeps only the field structure, which is ideal for reusing a proven setup.

Can I move a Table to a different Solution?

Yes. A dedicated menu option moves a Table from one Solution to another, so structure can be reorganized as processes evolve without rebuilding or re-importing data.

Who can add, delete, or restructure Tables?

Table management is restricted to Solution Creators, Workspace Administrators, and Solution Managers. General users work within Tables—adding and editing Records—without changing the structure.

Is a SmartSuite Table the same as an App?

Yes—"Table" is the current name for what some older SmartSuite documentation and the developer API call an "App" or "Application." Current help-center and product documentation use "Table" throughout.

Give Every Kind of Work a Structured Home

Build your first Table, shape it with Fields, and connect it to the rest of your work—structured from day one.