Solution Packaging

Solution Packaging — Distribute Governed Solutions as Versioned Packages

Bundle one or several Solutions—structure, Records, Views, Dashboards, and Automations—into a published snapshot you can install across Workspaces, environments, and regions with relational integrity intact.

What Is Solution Packaging?

Solution Packaging is a SmartSuite capability that bundles entire Solutions—Tables and Fields, optional Records, Views, Dashboards, and Automations—into portable packages published as versioned snapshots. It helps GRC, IT, and business operations teams distribute standardized workflows across Workspaces, environments, and US and EU regions with linked data and configuration preserved. Solution Packaging is managed by Workspace Administrators from Workspace Administration.

Portable Packages

Package Entire Solutions—Structure, Records, Views, and Automations

From the Solution Packaging tab in Workspace Administration, select one Solution or several related ones and configure what travels with them. Tables and their Fields always come along; toggles control whether Records, Automations, and Views and Dashboards are included—private Views stay out, and packaged Automations install inactive so nothing fires before you're ready.

The package captures the working system, not just a schema—so a control register arrives with its reports and workflows, ready to run.

Versioned Snapshots

Publish Frozen Snapshots and Distribute Them with Confidence

Work on a package as a draft, then publish it as a snapshot—a frozen version of the Solution exactly as configured at that moment. Published packages can't be silently altered; only the name, description, and icon can change, so what recipients install is what you reviewed.

Distribution runs through shareable install links, and regenerating a link invalidates the old URL instantly—giving you control over who can still install each published version.

Cross-Workspace Deployment

Install Packages Across Workspaces, Environments, and Regions

Installing is a guided, Administrator-only flow: preview the package contents, choose the target Workspace, place the incoming Solutions in a new or existing category, and track status through to installed. Packages move between Workspaces, environments, and the US and EU regions—so a build validated in one environment deploys cleanly to another.

Packages can be created on any plan, and install into paid-plan Workspaces.

Relational Integrity

Keep Linked Records and Lookups Intact with Automatic Remapping

Relational structure survives the move. Linked Records between packaged Solutions and Tables stay connected after installation, Lookups and Rollups keep working, and internal IDs are automatically remapped so filters and calculated Fields point at the right targets in the new Workspace.

Before you publish, the Package Inspector surfaces missing references and the Audit for Broken Links check flags anything that wouldn't survive the trip—so integrity problems are caught at build time, not after deployment.

Platform Context
How GRC Teams Use

Solution Packaging

Governed programs live or die on consistency—every business unit running the same registers, workflows, and reports. Solution Packaging turns a validated GRC build into a distributable, versioned standard.

Standardized Compliance Rollouts

Package the approved compliance Solution—control register, evidence Tables, testing workflows—and install it in each subsidiary's Workspace. Every business unit starts from the same reviewed version, not a hand-copied approximation.

Environment-to-Production Promotion

Build and validate risk workflow changes in a separate environment, publish the package as a snapshot, and install it into production. The frozen version guarantees what was tested is what deploys.

Framework Program Distribution

A central GRC team maintains packaged register structures for programs like SOC 2 or ISO 27001 readiness and distributes them by install link—regional teams deploy in minutes and retire their spreadsheet variants.

EU Region Deployments

Deploy the same governed Solution into US and EU region Workspaces from one published package, keeping structure identical where data residency requirements keep the data apart.

From Template to Governed Standard

Start a build from Solution Templates, tailor it to your control environment, then use Solution Packaging to publish your own versioned standard for every Workspace that follows.

Works Better Together
Related Features

Governed programs live or die on consistency—every business unit running the same registers, workflows, and reports. Solution Packaging turns a validated GRC build into a distributable, versioned standard.

Features FAQ’s
Frequently Asked Questions About
Solution Packaging
What is Solution Packaging in SmartSuite?

Solution Packaging bundles one or more Solutions—Tables and Fields, optional Records, Views, Dashboards, and Automations—into a portable package published as a frozen snapshot, which Workspace Administrators can install into other Workspaces via shareable links.

What does a package include?

Tables and their Fields are always included. Toggles control whether Records, Automations, and Views and Dashboards travel with the package—private Views are excluded, and Automations install inactive by default so nothing runs until you enable it.

Can a published package be changed?

No. Publishing freezes the package as a snapshot—only its name, description, and icon can be edited afterward. To ship changes, publish a new version and share its install link.

Do Linked Records and Lookups keep working after installation?

Yes. Linked Records between packaged Solutions and Tables stay connected, Lookups and Rollups continue to work, and IDs are automatically remapped so filters and calculated Fields resolve correctly in the destination Workspace.

Who can create and install packages, and on which plans?

Only Workspace Administrators can create or install packages. Packages can be created in any Workspace and installed into paid-plan Workspaces, and they move across Workspaces, environments, and the US and EU regions.

How does Solution Packaging support governed change management?

Published packages are immutable snapshots, so what was reviewed is exactly what deploys—supporting controlled rollouts across business units. Pre-publish checks like the Package Inspector and Audit for Broken Links catch integrity issues before distribution, which helps change-control processes stay audit-ready.

Roll Out Governed Workflows in Minutes, Not Migration Projects

Package your validated Solution once—then install the same versioned standard in every Workspace that needs it.