This article outlines the installation and configuration steps for setting up Backstory within Salesforce.
Configuring the Backstory experience in Salesforce requires four steps.
Upgrading to the latest managed package
Setting up Salesforce as an Identity Provider
Configuring Backstory as a Connect App within Salesforce
Updating the Salesforce user interface with Backstory components for the pilot users
Managed Packaged Installation Instructions
There are no installation prerequisites required; however, the installation must be performed by a System Administrator User.
Install the application using the following link:
Backstory Managed Package v4.16
Production: https://login.salesforce.com/packaging/installPackage.apexp?p0=04tHp000001rZac
Sandbox: https://test.salesforce.com/packaging/installPackage.apexp?p0=04tHp000001rZacSales Solution Only Package v1.9
Production: https://login.salesforce.com/packaging/installPackage.apexp?p0=04t5f000000SaaR
Sandbox: https://test.salesforce.com/packaging/installPackage.apexp?p0=04t5f000000SaaR
Install for all Users
Wait for the installation to complete
Identity Provider-Initiated Single Sign-On Configuration
The following steps are mandatory to complete the Identity Provider-Initiated (IdP) Single Sign-On (SSO) configuration within the Salesforce environment. This approach is used by default.
IdP-initiated SSO enables users to log in to Backstory apps and widgets automatically without manually initiating the flow.
Set up Salesforce as an Identity Provider
Navigate to Setup > Identity > Identity Provider
Configure Backstory Salesforce Connected App
Navigate to Setup > Apps > App Manager
Open the menu for the Backstory Canvas App and click the Manage button
Click the Edit Policies button
Change the Permitted Users field to “
Admin approved users are pre-authorized”Click the Save button
Scroll down to the Profiles section and click the Manage Profiles button
Tick any profile that users should be able to access embedded applications, and click the Save button
Note: Users without access to Connected App but with access to Backstory app components within Lightning Pages / Tabs will receive the following error popup, or may be redirected to the Insufficient Privileges error.
We recommend enabling all the profiles and drive access through the app itself, or access to the components.
Scroll down to the SAML Login Information section
Locate the Subject Type and update it to “Username”
Locate the Metadata Discovery Endpoint (Metadata URL) and Issuer (Entity ID) values
Register a new Provider in the PeopleAI App
In a new window, navigate to PeopleAI app > Settings > Integrations > Single Sign On
Click on the Add Provider button
Enter a name (e.g., 'Salesforce Production Organization')
Paste the Metadata URL and Entity ID values
Click the Next button.
Check the Backstory is Integrated checkbox.
Click the Save button
Publish the new provider
Note: The components will not load properly until the Backstory team confirms that the IDP configuration setup is complete on the Backstory side.
Additional Steps for Sandbox Configuration (Optional)
Sandboxes have affixed usernames by sandbox name by default, which will prevent user authentication.
Change SAML Subject Type:
Navigate to: Setup > Apps > App Manager
Open the menu for
Backstory Canvas Appand clickManageand thenEdit PoliciesChange the Subject Type field value from “Username” to “Federation ID”
Click the Save button
NOTE: You can also use the “Custom Attribute” value. Once selected, you must choose the correct field in the Custom Attribute field. If no selection is available, please create a new Custom Field (Text,255) on the User Object and refresh this page.
Note: Users with access to package components but without a Federation ID set will receive a permission-related error displayed in Salesforce Classic.
Update User Federation IDs:
The Federation ID (or Custom Attribute) must be populated with the original Username from the Production SFDC instance for every user who should have access to Backstory embedded apps.Update Users
Manual Update:
Navigate to Setup > Users > Users
Click the Edit button for every user who should be enabled.
Copy Username without sandbox name affix (user@company.com.sbname)
Paste the value into the Federation ID field
Click the Save button
Or you can execute this script in Developer Console to update all the users at once:
string affix = '.'+UserInfo.getUserName().substringAfterLast('.'); User[] us = [SELECT Username FROM User WHERE FederationIdentifier = '' AND UserType='Standard']; for(User u : us){ u.FederationIdentifier = u.Username.replace(affix,''); } update us;
Service Provider-Initiated Single Sign-On Configuration
As an alternative to the IdP-initiated flow, the application can be configured to use the SP-initiated flow, which requires users to log in manually to use the app. This method does not involve any Identity Provider configuration and requires only administrative intervention by the Backstory team using the Subscriber’s Granted Login Access.
Salesforce User Interface Configuration
The application includes several components that can be embedded into your pages to provide different views.
Embed Full Backstory App [Required]
This tab provides access to the entire Backstory web application and must be added to the ‘App’ of any user who will be using the Backstory Salesforce experience.
It is required because it ensures that any hyperlinks clicked on inside the Backstory Lightning components open a tab to the Backstory web application within Salesforce, rather than outside of Salesforce.
Navigate to Setup > Apps > App Manager
Choose any app to which you want to include the Backstory application, click the caret on the right side, and then click the Edit button
Open the Navigation Items tab in the left narrow column
Find the Backstory item and add it to Selected Items
Click the Save button
Need a hand? Have a question? Drop us a line at support@backstory.ai.










