The following tips and best practices are for Gainsight Administrators who work in organizations that completed their initial Gainsight implementation without the Admin’s involvement, or for people who are taking over from another Gainsight Administrator.

Transfer Knowledge & Permissions from Previous Administrator

If possible, new Administrators should receive a walk-through of their org’s configuration from the existing Admin before taking over. In particular, we recommend that the hand-off focus on the purpose and configuration of each rule; and your org’s metrics and usage data, so that you understand how your data integration with Gainsight works. Additionally, we encourage you to record any knowledge transfer sessions, if possible, since important details may not make into your written notes.

Complete the following permissions transfers. Steps marked by an asterisk (*) indicate they’re mandatory:

*Gainsight App OAuth Change (perform in numbered order):

  1. Refer to the How to Revoke OAuth Access article.
  2. MDA: Go to Administration > Connectors > Authorize MDA > Revoke > Authorize
. Note: There should be pop-ups throughout the process; if they’re not visible, make sure pop-ups are not blocked.

If using Gainsight Surveys:

  • Go to SFDC Setup > Scheduled Jobs: Look for a job name that contains “Gainsight Survey Response Count”. Submitted by should have the name of the former OAuth User. If so, delete the Job, and navigate to any Gainsight Survey and click “Publish” to create the new job under the new user.

If using Scorecard 1.0:

  • Scorecard Load to Usage: Go to Administration > Account Scorecards > Global Settings > uncheck "Load Snapshot to Engagement every week" > check "Load Snapshot to Engagement every week"
. Note: Modify All Data and Customize Application permission is needed in the SFDC Profile to see the option.

If Org is using Notifications:

  • Notifications: Go to Administration > Notifications > click Configure next to Notification Frequency > Uncheck any boxes that are checked. Then click Save > Click Configure again > Re-check the boxes that were checked, then click Save.

If Rules use action “Load to Usage” and data aggregation is used:

  • Usage Configuration Schedule: if there is any schedule created under Administration > Usage Configuration > Run Aggregation > Schedule Aggregation, turn this OFF and ON again.

If using API:

  • API: If you have been using the API to load data, you will need to make sure that the access key credentials used in the API are still valid. Check the cURl command itself, as this is where the access key and login info will reside. If it is the same person who was the Oauth and is now leaving, then you will need to update the login info and regenerate a new access key from the data load configuration.

Learn About Gainsight

We recommend the following resources to help new Admins learn about Gainsight:

In addition, you’ll want to leverage previous work completed by a Gainsight Admin, the Gainsight Services team, or in the form of templates available in Gainsight’s Vault:

  • Rules engine:

    • Use “Clone” option to make copies of existing rules, complete test run, and preview results.

    • Review rules engine tutorials 
  • Report builder:

    • Use “Save as” to make copies of existing reports, make modifications, and review results.

    • Review report tutorials 

General Advice for New Admins

1. Deliver value quickly

  • If your CSM team is new to Gainsight, pick a simple and familiar existing business processes to replicate in Gainsight, such as your new customer onboarding process. 

  • Avoid creating rules that generate too many automated CTAs right away, which can overwhelm CSMs and block adoption.

  • Foster an open collaborative environment with CSMs/Management, to identify priorities and ensure your efforts provide value.

2. Make your work transferable

  • Create a system that the next Admin can understand. For example, use this sample spreadsheet to document rules in your org.
  • Apply system for implementing new initiatives:

    • Align: understand and align on the need or request; have a clear end goal, and know what needs to be seen in the application

    • Plan: understand relevant, pre-existing systems; avoid redundancy, leverage what already exists

    • Copy existing rules/reports

    • Test: frequently and incrementally test rules; be generous with Show fields; and scrutinize test results

    • Schedule: order of rules may be critical and improper rescheduling can interrupt a meaningful sequence. Leverage Rule Chains in Gainsight wherever possible, as they make re-running rules much easier if there is a problem.

    • Document: for example, create glossary of fields used and schedule of rules; and CTA priorities and reason codes; use effective naming system

    • Monitor: review output of new rules and compare to old rules; also watch for unplanned impact to old rules

3. Tip for Part-time Gainsight Admins

  • Dedicate some time on a daily basis to getting up to speed.

Additional Admin Resources

Note: To have any open Zendesk support tickets transferred to a new Admin, please contact