Learn how to prepare your Salesforce Knowledge integration for receiving content from Paligo.
Paligo can only connect to Salesforce Knowledge if certain things are in place in your Salesforce instance. Here, we summarize what you need to set up. We have included links to the official Salesforce documentation where you can find detailed instructions.
-
Make sure you are on the appropriate plans for Paligo and Salesforce:
-
Paligo - You need to be on the Enterprise plan.
-
Salesforce - You need to be on a plan that supports:
-
Salesforce Knowledge in the Lightning Experience.
-
API access.
-
-
-
Make sure you have the appropriate Salesforce Experience Cloud licenses.
-
Enable these features:
-
Salesforce Knowledge in the Lightning Experience.
-
[Optional] Set up Data Categories. We recommend that you set up Data Categories as they allow you to organize your articles. For details, see the official Salesforce documentation.
You can only set up Data Categories in Salesforce. But once they are in place, you can choose which Data Categories to use from the publishing settings in Paligo.
-
Set up the Salesforce Digital Experience and choose a theme. The Digital Experience is the presentation part of Salesforce Knowledge, where your audience is presented with your articles.
Typically, Paligo users choose the Help Center theme in Salesforce Knowledge, see Prebuilt Experience Builder Themes.
-
To publish to multiple languages, make sure you have enabled those languages in Salesforce Knowledge.
-
From Setup, enter "Translate" in the Quick Find box.
-
Select Translation Language Settings.
-
Select Add.
-
Add the language(s) and translators.
-
Select Save.
For details, refer to the official Salesforce documentation.
-
-
[Optional]. We recommend that you set up a generic user in Salesforce Knowledge for the Paligo integration. This user will be available even if people leave your organization.
Now that you have prepared your Salesforce Knowledge instance, you can proceed to the next step: Connect Paligo to Salesforce Knowledge.
Comments
0 comments
Article is closed for comments.