ScreenMeetTest logoScreenMeetTest documentationAPI referencescreenmeettest
Salesforce

AIO

Updated Sep 2, 20264 min read

Installing ScreenMeet for Salesforce

Overview

This guide covers the complete installation of ScreenMeet for Salesforce, from AppExchange install through service account configuration and component placement. Follow the steps in order. All steps require a Salesforce System Administrator account.

Prerequisites

  • Salesforce Lightning Experience is enabled. ScreenMeet 2.0 and later do not support Classic. Contact ScreenMeet Support if your org is on Classic.

  • You have Salesforce System Administrator access.

  • You have a dedicated user account available to serve as the ScreenMeet Service Account. Do not reuse an account shared with other integrations.

Step 1: Install the Package from AppExchange

Production Org

  1. Log in to your production Salesforce instance as a System Administrator.

  2. Go to Setup and search for AppExchange Marketplace in the Quick Find box, or navigate directly to the ScreenMeet AppExchange listing.

  3. Click Get It Now and sign in with your Salesforce org credentials.

  4. When prompted:

    • Select Install for Admins Only.

    • Approve third-party access for api-v3.screenmeet.com and qa-v3-api.screenmeet.com.

  5. Click Install. Salesforce will send a confirmation email when complete.

Do Not Install for All Users

Selecting Install for All Users grants administrative privileges org-wide and creates security risks. Always select Install for Admins Only.

Sandbox Org

  1. Log in to your Salesforce sandbox as a System Administrator.

  2. Go to Setup and search for AppExchange Marketplace.

  3. Search for ScreenMeet and click Try It.

  4. Confirm Try in your Sandbox is selected, then click Continue to Installation.

  5. Click Login and Install and enter your sandbox credentials.

  6. Select Install for Admins Only, approve third-party access for the same domains listed above, and click Install.

  7. After installation, go to Setup > Custom Settings.

  8. Click ScreenMeet Settings > Manage > Edit.

  9. Check Is Sandbox and click Save.

Sandbox Org IDs and ScreenMeet Organizations

Each time you create or refresh a sandbox, Salesforce generates a new 18-digit Organization ID. ScreenMeet treats each unique ID as a separate organization. If you are setting up a refreshed sandbox, you will need to create and configure a new ScreenMeet organization after completing this installation.

Step 2: Configure Permissions and Roles

ScreenMeet includes five pre-defined permission sets. Assign them as follows:

Permission Set

Assign To

Notes

ScreenMeet Service

Service Account user only

Created automatically during install. Do not assign to regular users.

ScreenMeet Admin

System admins and project leads

Full control. Assign sparingly.

ScreenMeet Supervisor

Support supervisors

Can barge into sessions. Cannot change configurations.

ScreenMeet Beam Group Manager

Beam group managers

Requires package version 1.24 or later.

ScreenMeet Agent

All agents who create sessions

Standard role for Live, Remote Support, Replay, and CoBrowse.

Do Not Clone Permission Sets

Cloned permission sets do not receive updates when ScreenMeet introduces new role functionality. Use the managed sets directly, or create custom permission sets that extend them.

Connected App Access (Package Version 1.27 and Later)

Version 1.27 introduced an OAuth-based authorization flow. In addition to the permission sets above, you must grant users access to the ScreenMeet Connected App.

  1. Go to Setup > Manage Connected Apps.

  2. Select ScreenMeet and click Edit Policies.

  3. Under Permitted Users, select Admin approved users are pre-authorized.

  4. Click Save.

  5. Go to Setup > Permission Sets and click New.

  6. Name the permission set ScreenMeet Console Access and click Save.

  7. From the permission set overview, click Assigned Connected Apps > Edit.

  8. Move ScreenMeet from Installed Connected Apps to Enabled Connected Apps and click Save.

  9. Assign ScreenMeet Console Access to all Agents, Supervisors, Beam Group Managers, and Administrators.

Permission Set Groups

For larger teams, consider adding permission sets to a Permission Set Group rather than assigning them individually. Connected App access can also be granted at the profile level.

Step 3: Create and Configure the Service Account

The ScreenMeet Service Account allows your Salesforce org to communicate with ScreenMeet's servers.

Create the Service Account User

  1. In Salesforce, create a new user dedicated to this purpose. Name the user ScreenMeet Service Account.

  2. Record the username and password. You will need them in a later step.

  3. Assign the ScreenMeet Service permission set to this user.

Create the Service System Permissions Permission Set

  1. Go to Setup > Permission Sets > New.

  2. Set the label to ScreenMeet Service System Permissions. Confirm the API name auto-fills as ScreenMeet_Service_System_Permissions.

  3. Click Save.

  4. From the permission set, click System Permissions > Edit.

  5. Enable Apex REST Services, API Enabled, and Customize Application.

  6. For package version 1.26 and older, also enable Password Never Expires.

  7. Click Save, then Save again on the confirmation dialog.

  8. Click Manage Assignments and assign this permission set to the ScreenMeet Service Account user.

Generate a Security Token (Version 1.26 and Older Only)

  1. Sign in to Salesforce as the ScreenMeet Service Account user.

  2. Click your avatar (top right) and go to Settings.

  3. Under My Personal Information, click Reset My Security Token.

  4. Click Reset Security Token. The token will be emailed to the service account's email address.

No Reset Security Token Option

If the Reset My Security Token option is not visible, a Login IP Range is likely set on the profile. Append /_ui/system/security/ResetApiTokenEdit?retURL=%2Fui%2Fs

PreviousRequirements