You have created your help documentation. You have tested how they look in record pages. Now you need to make them available to your end users.  There are few steps to make sure it is seamless for them.

Important: Your Org requires the Elements Catalyst managed package to provision users and make in-app help available to them. 

Article outline:

  1. Purchase the Enterprise license
  2. Install Chrome Extension for all end users
  3. Setup Elements access for all Salesforce users by Profiles (3 steps)
  4. Grant user access to the Org Model

Purchase the Enterprise license

Users with editor licenses on a Space can access the in-app Salesforce help at anytime. However, in order to make help documentation available inside Salesforce for all your viewers in your Space you need to purchase the Enterprise license.  Contact Here is the pricing of the licenses

Install Chrome Extension for all end users

All your end-users need to have our Chrome Extension installed.  You can get them all to do it by going to the Chrome Extensions store.  Here is the LINK to the extension.  

Or if you are able to, then you can push the extension to every user.  Here are the instructions on how to do that.

The Chrome Extension will automatically update when we release improvements, but it can take up to 5 hours to propagate.  If you close the Chrome browser and restart it will be automatically updated. If you are using the automated push approach, you can use that to force the update.

Setup Elements access for all users and Profiles

Salesforce users are now Elements users, but you need to automatically log them into the Chrome Extension.  Luckily there is a standard Salesforce feature called Login Flow to do this.

There are 3 steps. 

  1. Create a VisualForce Page
  2. Create a Login Flow for each Profile referencing the VF Page
  3. Connect Salesforce users to Elements

1.Create a Visualforce Page

In Salesforce, go to the Elements app, selects the Elements Settings tab and the Elements Login Flow sub tab. 

Create a new VF Page. 

Give it a name and check the "Available for Lightning Experience... " check box

Delete the code that is in the empty VF Page and paste in this code below :

<apex:page controller=”Q9.ElementsGenericExtensionController” action=”{!setElementsLoginTokenToCookie}”></apex:page>

Save the VF Page.  
From the list of VF Pages, set up Security for each Profile.

2. Create a Login Flow for each Profile referencing the VF Page

If you don't set up the Login Flow for Profiles the user needs to login into Chrome Extension  - which they won't do.  So it only takes a moment to set this up for each Profile.

Did you know that you can run the Org Analytics report to see which Profiles have users?

For each Profile:

  • Create a new Login Flow
  • Select the VisualForce Page you have just created.
  • Select the user license and Profile to apply this to Login Flow to.

3. Salesforce users need Elements account (SSO)

The help documentation is hosted by Elements, so every Salesforce user needs to be an Elements Viewer or Editor. They do not need to register, because you can add them from the Elements Setting app. This provided SSO so it is seamless for the end users. They don't even need to know Elements is behind it all.

In Salesforce, go to the Elements app, selects the Elements Settings tab and the Connect Users (SSO) sub tab.  Select the users you want to connect and click the "Connect " button.  At the bottom check the box "Assign new users" so that any new users added to Salesforce are automatically connected.

Read this article on Salesforce SSO for further details. 

Grant user access to the Org Model 

You need to make sure users have access to the help documentation in the Catalyst app in order for them to be able to see it inside Salesforce. Since all documentation is added in the context of an Org Model you need to make sure users have access to the Org Model. 

You need to invite them to the appropriate Org Model to see the right panel content. Read this article for further details on how to grant access to the Org Model.

Did this answer your question?