UserEvidence for Salesforce — Post-Installation Instructions · UserEvidence Managed Package

Overview

UserEvidence for Salesforce brings your UserEvidence customer content — testimonials, case studies, stats, and videos — directly into Salesforce. Once configured, sales reps see recommended proof content on their Opportunities, can search your full content library without leaving Salesforce, and their content interactions are tracked so your team can measure impact.

Complete the steps below in order for a smooth rollout. A typical setup takes 45–60 minutes.

Step	Task
1	Confirm prerequisites
2	Install the managed package
3	Enter the UserEvidence API key
4	Assign permission sets
5	Set up the secure connection for the UserEvidence platform
6	Add the Lightning components to your pages
7	Verify the setup
8	(Optional) Share the reports and dashboard

1. Prerequisites

Before you begin, confirm the following:

A Salesforce edition that supports managed packages, custom objects, and Lightning Web Components — Enterprise or Unlimited Edition is recommended.
Lightning Experience is enabled (the package's components run only in Lightning Experience, not Salesforce Classic).
Outbound internet access from your Salesforce org to UserEvidence. The package includes the required Remote Site Settings for:
- https://app.userevidence.com
- https://ue-development.s3.us-east-2.amazonaws.com (used for content images)
If your organization uses an outbound proxy or IP allowlist, make sure these hosts are reachable.
A UserEvidence API key for your org. You enter this key in Step 3.
Administrator access to Salesforce with rights to install packages, manage users and permission sets, edit Lightning pages, and (if you connect the UserEvidence platform back into Salesforce) manage External Client Apps.

How to obtain your UserEvidence API key

The API key is issued by UserEvidence and is unique to your organization. If you don't already have one, request it from your UserEvidence account team before Step 3. Keep the key confidential — treat it like a password and share it only with the administrator performing this setup.

2. Install the managed package

Install the package into your production or sandbox org using the installation link provided by your UserEvidence account team.

Production: [Install link — to be provided]
Sandbox: [Install link — to be provided]

Open the installation link and log in to the correct org (production or sandbox) as an administrator.
On the installation screen, choose Install for Admins Only, Install for All Users, or Install for Specific Profiles according to your security standards. You will refine access with permission sets in Step 4, so Install for Admins Only is a safe default.
Approve any third-party access prompts (these authorize the outbound connections to UserEvidence listed in Step 1).
Complete the install and wait until Salesforce reports success.
Confirm the package appears under Setup → Installed Packages as UserEvidence.

Tip: If installation fails, note the exact error message and whether the org is a sandbox or production, then contact your UserEvidence account team.

3. Enter the UserEvidence API key

The API key lets the package retrieve content and recommendations from UserEvidence. It is entered through the package's configuration component in the UserEvidence Admin Panel app.

Open the App Launcher (the grid icon, top left) and search for UserEvidence Admin Panel. Open it.
Open the Home tab. Under Configs, you'll see the configuration panel with an API Key field.
Paste the API key you obtained in Step 1.
Click Save. A success message confirms the key was stored.

Security note: The API key is stored in a protected setting inside your org. Only administrators can view or change it — it is never exposed to end users.

If you don't see the configuration panel on the Home tab: Open Setup → Lightning App Builder, edit the UserEvidence Admin Panel Home page, and confirm the configuration component is present. It ships on that page by default.

4. Assign permission sets

The package includes two permission sets. Assign the one that matches each person's role.

Permission set (label)	API name	Who should get it	What it grants
UserEvidence User	`UserEvidence_User`	Sales reps, marketing, and RevOps — anyone who uses recommendations, the content library, or reports	Access to the UserEvidence Lightning components, ability to create and update their own content engagement records, read access to the UserEvidence fields on Opportunity
UserEvidence Admin	`userevidence`	Salesforce administrators, and the connection account used by the UserEvidence platform (see Step 5)	Everything the User set grants, plus configuration access and full access to integration data and the inbound API

How to assign a permission set

Go to Setup → Permission Sets.
Open the permission set (for example, UserEvidence User).
Click Manage Assignments → Add Assignments.
Select the users, then click Assign.

Repeat for each permission set and each group of users.

Tip: You can select multiple users at once on the Add Assignments screen — assign UserEvidence User to your whole sales team in a single pass, then handle admins separately.

5. Set up the secure connection for the UserEvidence platform

This step lets the UserEvidence platform connect back into your Salesforce org — to read open Opportunities for a rep and to attach customer content to a deal. It uses a secure, industry-standard OAuth 2.0 sign-in through a packaged External Client App.

This step is required. The Based on Recent Calls half of the recommendations component only fills in after UserEvidence writes content back to the Opportunity through this connection. Skip it and that section stays empty permanently, even though the rest of the package looks like it is working.

Complete this step with guidance from your UserEvidence account team.

Create (or choose) a dedicated connection user in Salesforce that the integration will run as, and assign it the UserEvidence Admin permission set (Step 4). Using a dedicated account keeps the integration's access predictable and separate from a real person's login.
Go to Setup, search for External Client App Manager, and open UserEvidence ECA.
On the app's Policies, enable the server-to-server sign-in option and set the Run As user to the connection user from step 1.
Share any credentials the UserEvidence platform needs securely with your account team — never by email or chat, and never store them in a document or source control.

Your UserEvidence account team will confirm the exact policy settings and credential exchange for your environment.

6. Add the Lightning components to your pages

The package ships several Lightning Web Components. You choose where to place them. The recommended layout below gives sellers recommendations on each deal plus a searchable library; adapt it to your org's page design.

Component (label in App Builder)	What it does	Recommended placement
UserEvidence Content Recommendations	Shows recommended proof content for the current deal and logs views/clicks	Opportunity record page
UserEvidence Library Search	Lets users search your full UserEvidence content library	A dedicated app page or Home page
Customer Evidence	Gives reps an Open Deal Page button for the deal, and embeds the microsite attached to it	Opportunity record page

Add recommendations to the Opportunity page

Open any Opportunity record → click the gear icon (⚙) → Edit Page. This opens Lightning App Builder.
From the Components panel on the left, find UserEvidence Content Recommendations (under the custom/managed components).
Drag it onto the page where you'd like reps to see it — a dedicated tab (for example, labeled Recommended Content) works well.
Also add Customer Evidence. This is where reps open the deal's UserEvidence Deal Page, and it embeds the microsite attached to the deal if there is one.
Click Save, then Activate the page and assign it to the appropriate apps, profiles, or record types.

Add the searchable library

Create a Lightning App Page (or use an existing one / a Home page): Setup → Lightning App Builder → New → App Page.
Drag UserEvidence Library Search onto the page.
Save and Activate, giving the page a clear name such as UserEvidence Library so users can find it from the App Launcher.

About the Opportunity Assets field

The package stores the deal's microsite link in an Opportunity Assets field on the Opportunity. You can add it to your page layout, but you no longer need to:

Setup → Object Manager → Opportunity → Page Layouts → drag Opportunity Assets onto the layout → Save.

Use the component instead. Reps reach UserEvidence through the Customer Evidence component's Open Deal Page button, which is easier to find than a field on a layout. It also lets UserEvidence report on who opened the page — a click on the raw field is anonymous, so those visits are missing from your engagement reporting. Leave the field off the layout unless an admin specifically needs to read or correct the stored link.

What the package shares with UserEvidence

When a rep loads the Customer Evidence component, the package asks UserEvidence for a Deal Page link for that rep, sending their Salesforce name and email address. UserEvidence uses this to attribute the visit to the right person in its reporting. Nothing identifying is placed in the link itself, so no personal data appears in browser history or in a link a rep copies. Share this with your privacy or security reviewer if your organization requires it.

About the Admin Panel and support content: The package also includes a UserEvidence Admin Panel app (where you entered the API key) and a support center component that admins can place to surface help content. These are optional to expose to end users.

7. Verify the setup

Run this checklist to confirm everything is working.

Installation & configuration

Setup → Installed Packages lists UserEvidence.
The API key is saved (the configuration panel shows a value with no error on save).
Setup → Remote Site Settings shows the UserEvidence entries as Active.

Access

UserEvidence User is assigned to everyone who should use the components.
At least one administrator has UserEvidence Admin.

Pages

The Opportunity record page is Activated and shows UserEvidence Content Recommendations.
The library search page is reachable from the App Launcher.

Smoke test (as an end user)

Log in as (or temporarily test as) a user who has UserEvidence User.
Open an Opportunity that has an account and a stage.
Confirm the UserEvidence Content Recommendations component loads without an error.
Open the library search page and run a search; confirm results appear.

Reading the recommendations component correctly

The component renders two independent sections. Telling apart the empty state that is normal from the one that means setup is incomplete is the difference between a working install and one that only looks like it works.

Section	Empty is expected when	Empty means setup is incomplete when
Based on this opportunity	The deal is early and has thin account, industry, or amount data. Matches improve as the Opportunity fills in.	An API or authorization error renders in place of the empty state — recheck the API key in Step 3.
Based on Recent Calls	No call has been analyzed for this deal yet. The section says so directly.	The section is empty on every Opportunity, including deals that do have analyzed calls — the Step 5 connection is missing, or its Run As user lacks UserEvidence Admin.

At least one Opportunity with an analyzed call shows content under Based on Recent Calls. If none do anywhere in the org, revisit Step 5 before calling setup complete.

The package ships five reports and a dashboard that turn content engagement into pipeline reporting. Salesforce folder access defaults to restrictive, so they stay invisible to your team until you share the folders — including to users who already have a UserEvidence permission set.

Folder	Contents
UserEvidence Reports	Content Performance · Content Usage by Opportunity · Conversion Rate - With Engagement · Conversion Rate - Without Engagement · ROI Attribution
UserEvidence Dashboards	UserEvidence Attribution & Performance

Open the Reports tab → All Folders → find UserEvidence Reports.
From the row menu, choose Share and grant Viewer (or higher) to the users, roles, or public groups who should see them — typically RevOps, marketing, and sales leadership.
Repeat on the Dashboards tab for UserEvidence Dashboards.

Tip: To customize columns or filters, clone a report into your own folder rather than editing the packaged original — that keeps future package upgrades clean.

Reports stay empty until reps begin interacting with recommended content, so expect no data on day one.

Troubleshooting

Symptom	What to check
No recommendations / component shows an error	Confirm the API key is saved (Step 3) and the user has UserEvidence User. Confirm the Remote Site Settings are Active.
"API key is not configured" or an authorization error	Re-enter the API key in the configuration panel — check for extra spaces. If it still fails, request a fresh key from your UserEvidence account team.
Content images don't load	Confirm the UserEvidence Remote Site Settings are Active and that your network allows outbound access to the hosts in Step 1.
A user can't see the components	Confirm they have the UserEvidence User (or UserEvidence Admin) permission set, and that the Lightning page you edited is Activated for their app/profile.
Permission set not found in Setup	Confirm the install completed (Setup → Installed Packages). Search the permission set list for "UserEvidence".
The UserEvidence platform can't read or update Opportunities	Confirm the connection user has UserEvidence Admin and that the secure connection in Step 5 is configured.
"Based on Recent Calls" is always empty	That section depends on the Step 5 connection. Confirm it is configured and that its Run As user has UserEvidence Admin.
The "Open Deal Page" button doesn't appear on the Customer Evidence component	The button appears once UserEvidence has a deal with recommended content for that Opportunity. If it is missing on every Opportunity, confirm the API key (Step 3) and the Step 5 connection.
Content links open through Salesforce instead of going straight to UserEvidence	Setup → CSP Trusted Sites — confirm `app_userevidence_com` is Active. The package ships this entry; if it was removed, re-add `https://app.userevidence.com`.
Reports or the dashboard aren't visible to RevOps	Folder sharing defaults are restrictive — share the UserEvidence Reports and UserEvidence Dashboards folders (Step 8).

Support

End users: Contact your Salesforce administrator or RevOps team.
Administrators: Contact your UserEvidence account team for API keys, connection setup, and platform questions.

For a deeper look at how the package works day-to-day, share the Manage-Package-User-Guide.md with your end users.

UserEvidence for Salesforce — Post-Installation Instructions