Setting up Customer Success Cloud
Before you can use Customer Success Cloud, you must:
- Assign Customer Success Cloud licenses to your users.
- You must install Foundations Summer 2023 or later.
- Assign the relevant permissions to your users.
- [Optional] Customize Customer Success Cloud Lightning components. For more information, see Customer Success Cloud Lightning Components.
- [Optional] Set up custom notifications and flows.
- [Optional] Enable tracking for recommended objects and fields.
- [Optional] Create Account Customer Success Resource records for existing custom Salesforce User fields.
For more information about setting up the Certinia Help- PSA Connector, see Setting up Customer Success Cloud – PSA Connector
Permissions
You can assign the following permission set groups to users for access to Customer Success Cloud:
|
Permission Set Group Name |
Description |
|---|---|
| Certinia - CSC - Customer Success Manager | Includes the CSC - Customer Success permission set. |
| Certinia - CSC - Participant User | Includes the CSC - Participant User permission set. |
For more information about the permissions included in this permission set group, see Permission Sets and Other Technical Documentation.
Setting Up Custom Notifications and Flows
We recommend that you set up custom notifications and flows, to enable users to receive notifications for the following scenarios:
- When a user is assigned as the Playbook Owner of a playbook.
- When a user is assigned to a playbook task.
For more information, see Setting Up Custom Notifications and Flows.
Setting Up Object and Field Tracking for Activity Tracker
We recommend that you set up object and field tracking, to enable users to see activity history for supported objects and fields with tracking enabled in the Activity Tracker component.
For a list of recommended objects and fields to track, see Customizable Lightning Components.
For more information about enabling object and field tracking, see the Salesforce Help.
CS Cloud Core Analytics
For information about setting up CS Cloud Core Analytics, see the following topics:
Create Account Customer Success Resource Records for Custom Fields
Create Account Customer Success Resource Records for Customer Salesforce User Fields
- Ensure that all users that are customer success managers are correctly linked with a CS Cloud Resource record.
-
To create Account Customer Success Resource records for custom Salesforce user fields on the account record page that surface the account customer success manager, enter and run the following code in developer console.
Copyfinal Integer MAX = 5000;
List<Account> accounts = [
SELECT Id, Your_CSM_User_Lookup__c
FROM Account
WHERE Your_CSM_User_Lookup__c != NULL
AND Id NOT IN (
SELECT csc__Account__c
FROM csc__Account_Customer_Success_Resource__c
)
LIMIT :MAX
];
Assert.isFalse(accounts.isEmpty(), 'No Account Customer Success Resources to create.');
Set< Id> assignedUserIds = new Set<Id>();
for (Account account : accounts) {
assignedUserIds.add(account.Your_CSM_User_Lookup__c);
}
List<csc__Resource__c> resources = [
SELECT Id, csc__Salesforce_User__c
FROM csc__Resource__c
WHERE csc__Salesforce_User__c IN :assignedUserIds
LIMIT :MAX
];
Map<Id, Id> resourceIdByUserId = new Map<Id, Id>();
for (csc__Resource__c resource : resources) {
resourceIdByUserId.put(resource.Salesforce_User__c, resource.Id);
}
List<csc__Account_Customer_Success_Resource__c> accountCSResources = new List<csc__Account_Customer_Success_Resource__c>();
for (Account account: accounts) {
csc__Account_Customer_Success_Resource__c accountCSResource = new csc__Account_Customer_Success_Resource__c();
accountCSResource.csc__Account__c = account.Id;
accountCSResource.csc__Resource__c = resourceIdByUserId.get(account.Your_CSM_User_Lookup__c);
accountCSResources.add(accountCSResource);
}
insert accountCSResources;
For more information about executing Anonymous Apex Code, see the Salesforce Help.
Using Customer Success Cloud Components On your Experience Cloud Site
CSC Playbook Task Portfolio Grid Component
You can add the CSC Playbook Task Portfolio Grid component to your existing Experience Cloud site to enable your customers to view and edit playbook tasks.
When using the Playbook Task Portfolio Grid on your Experience Cloud site the following buttons are not available:
- Add Task
- Delete Tasks
- Flag Tasks
To add the CSC Playbook Task Portfolio Grid to an existing Experience Cloud site:
- Click Setup | Feature Settings | Digital Experiences | All Sites.
- Click Builder next to the site you want to update.
- Click
. The Components panel opens. - Navigate to the Custom Components section.
- Drag the CSC Playbook Task Portfolio Grid onto the page.
- Click Publish, then Publish again. You will receive an email confirmation when your changes are live on your Experience Cloud site.
Setting up Permission Sets
You can configure your Experience Cloud site permissions to control how your customers can interact with playbook tasks. Permissions can restrict some of the functionality, enabling you to protect your data while still enabling the customer to view their tasks, and perform permitted actions enforced by your permission configuration.
For more information about setting up permission sets, see Setting up Permission Sets for Experience Cloud Sites.
Creating Sharing Sets
You can decide which objects to give your users access to. You must create sharing sets to share the records with your users. A user can only see an object if their profile allows them at least read-only access to it.
To create a sharing set, Navigate to Setup | Feature Settings | Digital Experiences | Settings. For information on how to create a sharing set, search for “Set Up Sharing Sets” in the Salesforce Help.
To share records with your users:
- On the Sharing Set Edit page, enter a label in the Label field and accept the default Sharing Set Name. Label is the sharing set label as it appears on the user interface. The Sharing Set Name is the unique name used by the API.
- Select the profiles of the users to whom you want to provide access: Customer Community Plus User or Partner Community User.
- Select the following objects to grant users access to them:
- Playbook
- Playbook Task
- From the Configure Access section, click Edit next to the Playbook object. The Access Mapping for Playbook window opens. Select the following values from the fields displayed:
- User: "Account"
- Target Project: "csc__Account__c"
- Access Level: "Read Only"
- Click Save.
The following table details the minimum required object permissions for a Community user to have access to playbooks and playbook tasks:
| Object |
Minimum Permission |
|---|---|
| Playbook | Read |
| Playbook Task | Read |