What This Article Covers

Solution Launchpad is available through the Keap certified partner program. Solution Launchpad allows certified partners to install pre-configured solutions — including custom roles — from one app to another. This article covers what is included and excluded when a custom role is installed using Solution Launchpad, how role dependencies are handled, and how the system manages duplicate roles during installation.

To learn how to become a certified partner and access Solution Launchpad, see how to become a Keap Certified Partner.

What Is Included When Installing a Custom Role

When a custom role is installed from one app to another using Solution Launchpad, the following data is transferred to the destination app:

• The role name
• Permission settings for all features configured in the role
• Granular permission controls associated with the role

What Is Not Included When Installing a Custom Role

The following data is not transferred when a custom role is installed using Solution Launchpad:

• User assignments — The users assigned to the role in the source app are not carried over. After installation, administrators in the destination app must manually assign users to the new role.
• Role usage history — The activity and usage history associated with the role in the source app is not transferred to the destination app.

Role Dependencies and Behavior After Installation

Custom role permissions are standalone and do not require additional dependencies to be installed alongside them. However, the following behaviors apply after a custom role is installed in the destination app:

• Feature availability — If the destination app's edition does not include a feature that the installed role has permissions configured for, those permissions will be applied to the role but will have no effect until the feature becomes available in that edition. If the feature is added to the destination app's edition later, the permissions will already be in place and will become active automatically.
• Roles are installed as templates — Custom roles are installed as permission templates only. No users are automatically assigned to the role. Administrators in the destination app must manually assign users to the installed role before any permissions take effect for those users.

How Solution Launchpad Handles Duplicate Roles

When Solution Launchpad installs a custom role into a destination app, it checks whether a role with the same name or permissions already exists. The following logic determines what happens in each scenario:

1. Role was previously installed from Solution Launchpad — Installation is skipped. The existing role in the destination app remains unchanged, even if the permissions in the bundle have been updated since the original installation.
2. Role has a matching name and identical permissions — Installation is skipped because an identical role already exists in the destination app. No changes are made.
3. Role has the same name but different permissions — The role is installed with a number appended to the role name to make it unique in the destination app. For example, if a role named "Sales Manager" already exists, the newly installed role will be named "Sales Manager 1."
4. No conflict exists — The role is installed as configured with no modifications to the role name or permissions.