The specific aspects of user management in Gainsight are detailed here.
For a user to gain access to Gainsight, an Access Request (AR) must be created. These should be created automatically for new employees. Similarly, when users leave GitLab an Offboarding issue will be created. The following GitLab pages will show any ARs or Offboarding issues that need to be actioned by the CS Ops team:
There are some situations where an AR is not automatically created. If this happens for a user that should receive a Gainsight license, direct the user/user’s manager to create an AR. Make sure to add the CSOps::Action Needed label to the AR once it is created so it will not get lost.
If a user that is not already approved to receive a Gainsight license requests access to Gainsight, work with CS Ops leadership to determine if the user should receive a Gainsight license or not.
A Salesforce account should be automatically created when a user joins GitLab. If you cannot locate the user’s Salesforce account, see the Troubleshooting section below.
Once you have located the user record, follow these steps. Although some of these steps may be already completed by Sales Systems, it is important to confirm that the user’s setup is done correctly in Salesforce before giving access in Gainsight.
Once you have confirmed the user account is set up correctly, you will need to assign a license:
You can see the amount of used and allowed licenses on the Gainsight CSM Package Details page. In a situation where we run out of Gainsight licenses, work with CS Ops leadership to determine a plan - will either need to remove licenses from existing users or purchase more licenses.
Once a license has been provisioned in Salesforce, you will need to perform some additional steps in Gainsight to complete the user setup.
Important: All users in Gainsight are imported from Salesforce, we do not create users directly within Gainsight.
Gainsight uses the a Connector job to sync users and user information from Salesforce. This job is called SFDC User Sync
and can be accessed on this page in Gainsight or by navigating to Administration → Integrations → Connectors 2.0 → Jobs tab.
This job runs once a day and brings in any new users as well as updates any information that has changed in Salesforce.
To confirm that a user has been synced successfully from Salesforce you can search for the user by:
If the user has not yet been synced from Salesforce to Gainsight, you can either 1) wait until the next sync job or 2) trigger a manual sync. You can do a manual sync by clicking the 3 dots by the job name → Run Job → Data modified since last sync date and time.
Note: the SFDC User Sync
job will only sync users that are Active in Salesforce. If the user has not yet been created in Salesforce or if they have not been set to Active, the sync will not bring them over to Gainsight.
You can see the logs/details of a specific sync by navigating to Connectors 2.0 → Activities tab. Then find the sync in the list, click the 3 dots, and select Job Activity. From here you can see the number of successful and failed records. You also have the option to download any failed records to see the specific error messages.
For more information on troubleshooting specific errors, see the Troubleshooting section below.
Once you have confirmed the user has synced from Salesforce successfully, you will need to do the following:
Note: The most important fields that you should confirm are filled out are the User Role field, and for PubSec users the US PubSec User field. These fields are used to automatically add the user to the correct Sharing Group (see more details below in the Data Permissions/Sharing Groups section.
Gainsight bundles give access to specific pages and modules in Gainsight. You can navigate here by going to Administration → Users and Permissions → Permission Bundles.
From here you can assign users to a bundle (can also be done from the user’s record as described above), check which users are in a specific bundle, create new bundles, or change access permissions for a specific bundle.
To add a user to a bundle or see a list of users in a bundle, click the 3 dots next to the bundle name → Assign users.
To change access for a specific bundle, click the 3 dots next to the bundle name → Edit.
Note: If Gainsight releases a new feature that a specific group of users will need access to, you will probably need to go into each applicable group, navigate to the new feature, and check the box. This will not be done automatically.
These are the most used bundles: | Bundle Name | Description | | ————————– | ———————————————————— | | Default | Bundle assigned to GS admins, provides access to all areas of Gainsight. | | GS Admin sans provisioning | This is a GS admin role that has access to everything except for User Management. | | CSM Users | Permission group for CSM Users. Includes access to C360, Dashboards, Home, Timeline, Cockpit, Success Plans, and analytics for surveys and NPS. This is the bundle assigned to most users. | | SAL Users | This is the role for SALs to run and manage their account planning. | | View | Default View User Group allows admin to assign view access to resources for selected users. | | View Analytics | Default permission bundle for Viewer Analytics Licensed Users which gives access to Dashboards, Timeline, and Company 360. |
We use data permissions and sharing groups to grant or restrict access to specific records in Gainsight. This is used at GitLab specifically to protect PubSec data. You can access this by navigating to Administration → Users and Permissions → Data Permissions.
In order for a user to access Gainsight data they need to be assigned to a sharing group. They should be added to a group automatically based on their user role. If the user role is not filled out or wasn’t when the user was synced from Salesforce, you will need to add them to a sharing group manually.
You can see which account records are displayed to which sharing groups by navigating to Data permissions → Company → Rule based.
C360 page layouts allow us to hide or display different C360 views to users in Gainsight. You can view/edit layouts by navigating to Administration → 360 Layouts → C360. Users are automatically assigned to the Default layout unless specified otherwise.
We currently have three main C360 layouts:
Name | Description |
---|---|
Default | The default layout for CSMs and non-SALs. The CSM field is displayed but not editable. |
CSM Edit | An exact copy of the default layout except the CSM field is editable. This is assigned to users when the CSM Edit? field on the User record = Yes. |
Account Planning | Layout specifically for Sales/SALs for account planning. This is assigned to users when the Page Layout field on the User record = Account Planning. |
When a user leaves GitLab or no longer requires access to Gainsight, you can remove deactivate their account and remove their license. For GitLab employees who leave GitLab, an offboarding issue should be created as detailed in GitLab Access Requests and Offboarding Issues.
To deactive a user's Gainsight account:
You may also need to remove the user's Gainsight license in Salesforce:
Users can access Gainsight directly from Okta or through Salesforce.
To access Gainsight through Okta:
To access Gainsight through Salesforce:
Coming soon!