Setting up Customer Success Cloud

Before you can use Customer Success Cloud, you must:

  • Ensure you have carried out the tasks outlined in Preparing to Install.
  • Assign Customer Success Cloud licenses to your users.
  • Assign the relevant permissions to your users.
  • [Optional] Customize Customer Success Cloud Lightning components. For more information, see CS Cloud Lightning Components.
  • [Optional] Set up custom notifications and flows.

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.

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.

CS Cloud Core Analytics

For information about setting up CS Cloud Core Analytics, see the following topics:

Using Customer Success Cloud Components On your Experience Cloud Site

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
  1. Click Setup | Feature Settings | Digital Experiences | All Sites.
  2. Click Builder next to the site you want to update.
  3. Click . The Components panel opens.
  4. Navigate to the Custom Components section.
  5. Drag the CSC Playbook Task Portfolio Grid onto the page.
  6. Click Publish, then Publish again. You will receive an email confirmation when your changes are live on your Experience Cloud site.

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 the "Getting Started with PSA Experience Cloud Sites Summer 2022" PDF on the Certinia Community.

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:

  1. 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.
  2. Select the profiles of the users to whom you want to provide access: Customer Community Plus User or Partner Community User.
  3. Select the following objects to grant users access to them:
    • Playbook
    • Playbook Task
    Note:

    If the Playbook Task object does not display, complete the following steps:

    1. Navigate to Setup | Security | Sharing Settings.
    2. Click Edit next to Organisation-Wide Defaults.
    3. Set the Default External Access column to Private for the Playbook Task object.
    4. Click Save .
  4. 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"
  5. 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