Overview
Solution Packaging allows Workspace Admins to bundle entire solutions into portable packages that can be shared and installed across different workspaces. This makes it easy to move solutions between testing and production environments, deploy partner-built solutions to client workspaces, and support installations across regions (US and EU).
This feature is available for Pro plans and higher.
Key Capabilities
Create Packages – Select one or more solutions (and their related solutions) to include in a package.
Maintain Relationships – Linked Records, Lookups, Rollups, and related content are preserved.
Include Content Options – Decide whether to include records, automations, views, and dashboards.
Audit for Broken Links – Identify missing references before publishing.
Publish & Share – Finalize packages as snapshots, generate share links, and track installation history.
Install Packages – Preview package contents before installing into your workspace.
Accessing Solution Packaging
Only Workspace Admins can create or install packages.
To access the feature:
Go to Workspace Administration.
Open the Solution Packaging tab.
Choose from two sections:
Created Packages – Packages built in your workspace.
Installed Packages – Packages you’ve installed.
Creating a Package
Start a New Package
Click + New Package from the Created Packages tab to start creating a new package.
Click Add Solution to choose from your workspace’s solutions.
Related solutions will be suggested for inclusion. Click on the + icon to add linked Solutions to your package.
Configure Package Content
Expand the Package Includes section in the right-side panel to configure package options.
Options include:
Include Records (default: on)
Include Automations (default: on)
Include Views & Dashboards (default: on, private views excluded)
Handle Linked Records
The Package Inspector highlights Linked Records that reference missing tables.
Click on any of the Missing Fields items to automatically add all missing references to the package.
You can choose whether to exclude or include “broken” references. To enable inclusion of Linked Records with missing references, toggle on the Include fields with missing references in the package option.
Save or Publish
Save as Draft. Click the Save as Draft button to save your progress and continue editing the package later. Note that the exact configuration of the selected Package components will not be fixed until you publish the package.
Publish. Click the Publish Package button to "freeze" the package as a snapshot of the current state. The package will enter a generating status, which will change to Published when complete (and ready to share).
Note: Published packages cannot be modified (you cannot change anything in their package contents). You can, however, modify metadata information such as package name, description, icon, and notes.
Sharing Packages
After publishing, Admins can enable Shared Links to a specific package. Configuring package sharing takes just a few steps:
Open Sharing Dialog. In the Created Packages list, click the 3-dot menu to the right of the target package, then click Share.
Enable Sharing. Toggle the Enable Sharing option to on (green).
Share the Link. You can now Copy the package link, or click the Preview button to open the installation interface directly.
Regenerate Link. You also have the option to regenerate the link to the shared package. This resets its link URL and invalidates the old one. You will be prompted for confirmation that you want to continue.
Important Notes
Sharing is off by default.
Shared links can be copied, regenerated, or previewed.
Deleting a package automatically invalidates its shared link.
Installing Packages
Packages are installed using the shared package link. When someone clicks a shared link, they must log in to SmartSuite and then complete the Install Package workflow:
Login & Permissions
You must be logged in and have Admin rights in at least one workspace to install a package.
If you click a Package link and are not logged in to SmartSuite, you will be prompted to log in.
Preview the Package
The install process starts with a preview of the package's contents. You will be able to view summary information as well as the details of included Solutions, Tables, Views, Records, and Automations.
Package Summary. The package summary includes:
Entity Counts for:
Solutions
Tables
Views
Records
Automations
Package creator name and publish timestamp
Solution Details. You can expand the Solutions included in the package to see more details:
Tables
Fields
Record count
Views
Automations
Containing table and list of included Automations.
Select Workspace
If you’re Admin in multiple workspaces, you’ll select the target workspace. If you are Admin in a single workspace, this step is skipped.
Choose Category
You will be prompted to choose a Home Page Category for the installed Package. You have two options:
Install as New Category. A new category will be created for the package using the package name, icon and description.
Install in Existing Category. This option allows you to select from existing categories as the target for package installation.
5. Installed Packages
You will be taken to the Installed Packages tab in your selected installation Workspace. You will have the ability to view installation status, which will reflect one of the following status conditions:
Installing Package. The package installation process is in progress. You can check back to view updates to the installation state at any time, the install process will proceed even if you leave the page.
Installed. The package installed successfully.
Failed. There was a problem installing the package. You will have the option to re-try installation.
Notes:
Solutions created during installation default to “Private to Me” until permissions are updated.
If conflicts exist (e.g., duplicate solution names), SmartSuite applies its standard naming logic, appending a number to the end of the name.
Managing Created Packages
Editing Packages
Packages in Draft status can be freely edited:
Select the Edit option from the package's 3-dot menu.
The package will open in the package editor, and you can continue making modifications until you choose to publish the package.
You can also click the package 3-dot menu to edit:
Package Name
Package Description
Package Icon
Packages in Published status can be edited, but you can only change:
Package Name
Package Description
Package Icon
Duplicating Packages
You can duplicate any package, whether in Draft or Published status. Duplicating a package makes an editable copy, starting with the original package's configuration. The process is simple:
Open the 3-dot menu for the package as click Duplicate.
A new package will be created named {Package} Copy.
You will then be able to edit the package, saving as a draft or publishing as a new package.
Use Cases
Example 1: Moving from Testing to Production
An Admin creates a package in the testing workspace and installs it in production to ensure consistency.
Example 2: Partner Deployments
A partner bundles a custom-built solution and shares a package link with their client for installation.
Example 3: Regional Deployments
Packages can be deployed between US and EU instances, supporting compliance and localization needs.
✅ Tip: Always preview and audit packages for broken references before publishing to ensure smooth installation.