This article supports Gainsight NXT, the next evolution of the Customer Success platform. If you are using Gainsight CS Salesforce Edition, you can find supporting documentation by visiting the home page, and selecting CS > Salesforce Edition.
Not sure what your team is using? Click here.
IMPORTANT: Solution Marketplace is enhanced and launched as Sightline Vault containing pre-configured solutions by Gainsight and the Gainsight Community, which help you effectively utilize Gainsight features and incorporate best practices into your Gainsight instance with the click of a button. Click here to learn more.
Note: Solution Marketplace support documentation will be removed soon.
IMPORTANT: Solution Marketplace is now a community-enhanced customer success technology called Gainsight Sightline Vault which is a one-stop-shop for accessing pre-configured solutions from Gainsight and the Gainsight community. Sightline Vault helps you effectively utilize Gainsight features and incorporate best practices into your Gainsight instance with the click of a button. Learn more.
To make data, tasks, or workflows across the customer success tech stack easier to connect, Gainsight recommends you upgrade your production org to Gainsight release v6.15 or higher. The Solution Marketplace feature is completely replaced with the enhanced Sightline Vault feature.
When you’re ready to upgrade, please contact firstname.lastname@example.org and include your Salesforce Org ID. Our support team will work with you to perform the upgrade. (Note: Please allow 2 business days lead time.)
This article explains how to deploy an Element or a Package in Solutions Marketplace.
Solutions Marketplace helps you derive value from Gainsight by easily deploying pre-built Packages and Elements. When you deploy a Package or Element, you have various deployment options available to you. This article explains the deployment process and available options.
The deployment process creates the Gainsight Assets configured with an Element or a Package. Assets include Playbooks, Rules, Surveys, Reports, etc.
By default, all the Assets of an Element or a Package are selected for deployment. If you do not wish to deploy an Asset, clear the checkbox for that Asset. The Asset(s) whose respective check box(es) is not selected is not configured when the Element or Package is deployed.
Once you select all of the required Assets, click DEPLOY.
To preview a particular Asset, click the eye icon for that Asset. To create the Asset, click the download icon.
Handling Manual Assets
Some Assets are part of a Package or Element but must be manually created. You can differentiate a manual Asset from an automated one by the symbol present against the Asset.
Assets that are created automatically are accompanied by a checkbox. When you select the checkbox for the Asset, it is created during deployment.
Manual Assets are accompanied by a human symbol and have to be manually created. If you wish to use a manual asset, you must create them before deploying the respective package or solution. However, some manual rule assets are for post-deployment.