Modules & Templates

Modules and templates are designed to reduce repetitive work when deploying the same set of assets across multiple portals. Modules bundle assets together. Templates save deployment configurations for reuse. Together, they turn a one-time implementation into a repeatable process.

Modules

A module is a named bundle of related assets stored in the Asset Library. Instead of selecting individual assets every time you deploy, you can deploy an entire module as a single unit.

When to Use Modules

Modules are useful when you have a set of assets that are always deployed together. Common examples:

• Client onboarding kit — a workflow, a list, two forms, and three emails that every new client receives
• Campaign stack — a landing page, form, email sequence, and enrollment workflow for a repeatable campaign pattern
• Pipeline setup — a deal pipeline with associated lifecycle workflows and notification emails
• Reporting package — a dashboard with its underlying reports and required properties

Creating Modules

There are two ways to create a module:

During import (Step 4): After selecting assets and completing the import, the wizard offers the option to group the imported assets into a module. Provide a title and optional description, and the module is created automatically with all imported assets bundled inside.

Manually from the library: Navigate to the Modules tab in the Asset Library and click Create Module. Enter a title and description, then select assets from your library to include. This is useful when you want to bundle assets that were imported at different times or from different source portals.

Module Contents

A module can contain any combination of asset types. There is no restriction on mixing CRM assets (workflows, lists, forms) with CMS assets (pages, templates, blog posts) or Ultimate assets (dashboards, reports) in the same module.

Each asset in a module retains its individual identity in the library. An asset can belong to multiple modules simultaneously. For example, a shared email template might appear in both your “Onboarding Kit” and “Campaign Stack” modules.

Editing Modules

Open a module from the Modules tab and click Edit to:

• Rename the module or update its description
• Add assets from the library
• Remove assets from the module (the assets remain in the library)
• Reorder assets to control their display order

Deploying a Module

When you start a deployment and select a module, all of its bundled assets are loaded into the deployment wizard as the initial asset set. From there, you can:

• Remove individual assets from the deployment if you do not need the full bundle
• Add additional assets not in the module
• Proceed with mapping and configuration as usual

The module itself is not deployed — its individual assets are. The module is simply a selection shortcut.

Deleting Modules

Deleting a module removes the grouping. The individual assets remain in the library unaffected. If you want to remove both the module and its assets, delete the assets separately after deleting the module.

Templates

A template is a saved deployment configuration that can be applied to future deployments. While modules define what to deploy, templates define how to deploy it.

What Templates Save

A template stores:

• Property mappings — how source properties map to destination properties
• Pipeline mappings — how source pipeline stages map to destination stages
• Owner mappings — how source user assignments map to destination users
• Asset selections — which assets are included in the deployment
• Configuration overrides — any per-asset configuration adjustments

When to Use Templates

Templates are valuable when you deploy the same set of assets to multiple portals with similar configurations. For example, if every client portal has the same pipeline structure, you can create a template that pre-fills all pipeline mappings. Each deployment then requires only minor adjustments instead of full reconfiguration.

Managing Templates

Templates are managed at Implementations > Templates. From this page you can:

• Create a new template — start from scratch or save the configuration from a completed deployment
• Edit an existing template — update mappings, asset selections, or configuration overrides
• Delete a template — remove it permanently
• Duplicate a template — create a copy to modify for a variation

Creating a Template from a Deployment

The most common way to create a template is from a completed deployment:

1. Complete a deployment through the standard wizard
2. On the results page, click Save as Template
3. Provide a name and optional description
4. The full deployment configuration is saved

This captures every mapping and configuration decision you made during that deployment, so you can replay it against a different destination portal.

Using a Template in a Deployment

When starting a new deployment:

1. In the deployment wizard, click Load Template
2. Select the template to apply
3. Mappings and configurations are pre-filled from the template
4. Review and adjust for the specific destination portal
5. Proceed with deployment

Templates are suggestions, not locks. You can override any pre-filled value. The template saves time on the common configuration while leaving full flexibility for portal-specific adjustments.

Modules and Templates Together

The most efficient workflow combines both:

1. Create a module bundling the assets for your standard implementation
2. Deploy the module to a client portal, configuring all mappings
3. Save the deployment as a template
4. For the next client: select the module (assets), load the template (configuration), adjust as needed, deploy

This pattern turns a complex multi-asset deployment into a repeatable, near-automated process.

Next Steps

• Browsing the Asset Library — Navigating and finding assets
• Managing Assets — Edit, delete, and bulk operations
• How Deployment Works — The full deployment pipeline