Solution Launchpad is available through our certified partner program. Click here to learn how you can become a certified partner.

This document outlines what is included when a custom role is installed from one app to another, using Solution Launchpad.

What's included?

The following data is included when installing a custom role:

• Role name

• Permission settings for all features

• Granular permission controls

What's NOT included?

The following data is not included when installing a custom role:

• User assignments to the role

• Role usage history

Role Dependencies

When configuring a custom role, permissions are standalone and do not require additional dependencies. However, keep in mind:

• Feature Availability: Permissions for features not available in the destination app's edition will be applied but will have no effect. If that feature later becomes available in your edition, the permissions will already be in place.

• Roles are installed as templates and require manual user assignment in the destination app

Note: Custom roles provide granular permission management capabilities. After installation, administrators in the destination app will need to assign users to the new role as needed.

Duplicate Role Handling

When installing roles through the Solution Launchpad, the system uses the following logic to handle duplicates:

1. Previously installed from SLP: Installation is skipped and the existing role remains unchanged, even if permissions in the bundle have been updated since the original install.

2. Matching name and permissions: Installation is skipped since an identical role already exists.

3. Same name, different permissions: The role is installed with a number appended to the name (e.g., "Sales Manager 1") to make it unique.

4. No conflict: The role is installed as-is with no modifications.