A service account is required to allow your Salesforce organization to communicate with ScreenMeet’s servers. This guide explains how to create and configure the ScreenMeet Service Account in Salesforce, then complete the required configuration in ScreenMeet Console.<hr><h3>Create the ScreenMeet Service Account User</h3><ol><li>In Salesforce, create a new user dedicated to the ScreenMeet Service Account</li><li>Name this user: ScreenMeet Service Account</li><li>Document the new user’s username and password as these will be needed later</li><li>Assign the following permission sets to the service account user:<ul><li>ScreenMeet Service (This permission set is created automatically during installation)</li><li>ScreenMeet Service System Permissions (This permission set will be manually created in the next section)</li></ul></li></ol><blockquote>For security reasons, we recommend using a dedicated user account for the ScreenMeet Service Account instead of an account shared with other third-party integrations.</blockquote><hr><h3>Create and Configure the ScreenMeet Service System Permissions Permission Set</h3><ol><li>Go to Setup in Salesforce</li><li>In the Quick Find box, search for Permission Sets</li><li>Click Permission Sets</li><li>Click New</li><li>Enter ScreenMeet Service System Permissions for the label</li><li>Confirm the API Name auto-fills as ScreenMeet_Service_System_Permissions</li><li>Click Save</li><li>From the ScreenMeet Service System Permissions permission set, click System Permissions</li><li>Click Edit</li><li>Enable the following permissions:<ul><li>Apex REST Services</li><li>API Enabled</li><li>Customize Application</li></ul></li><li>Click Save</li><li>Click Save again on the confirmation dialog</li><li>Click Manage Assignments</li><li>Assign the permission set to the ScreenMeet Service Account user</li></ol><blockquote>Note: For ScreenMeet package version 1.26 and older, you must also enable Password Never Expires. This is covered in the version-specific section below.</blockquote><hr><h3>ScreenMeet package version 1.26 and older</h3><h4>Create Security Token</h4><ol><li>Sign in to your Salesforce instance as the ScreenMeet Service Account user</li><li>Click on your avatar in the top-right and click Settings</li><li>Click Reset my Security Token from the menu on the left under My Personal Information</li><li>Click the Reset Security Token button</li><li>An e-mail will be sent to the email address of the ScreenMeet Service Account user with the security token</li></ol><blockquote>NOTE: If there’s no option to Reset My Security Token, check that Login IP Range is not set for the profile. If the Login IP Range is set, append the following after the Organization URL. This will enable you to reset the security token./_ui/system/security/ResetApiTokenEdit?retURL=%2Fui%2Fsetup%2FSetup%3Fsetupid%3DPersonalInfo&amp;setupid=ResetApiTokenFor example:<a target="_blank" rel="noopener noreferrer nofollow" href="https://yourorg.lightning.force.com/_ui/system/security/ResetApiTokenEdit?retURL=%2Fui%2Fsetup%2FSetup%3Fsetupid%3DPersonalInfo&amp;setupid=ResetApiToken">https://yourorg.lightning.force.com/_ui/system/security/ResetApiTokenEdit?retURL=%2Fui%2Fsetup%2FSetup%3Fsetupid%3DPersonalInfo&amp;setupid=ResetApiToken</a></blockquote><hr><h3>ScreenMeet package version 1.27 and newer</h3>Package version 1.27 and newer uses OAuth-based access and does not require the service account password or security token to be entered in ScreenMeet Console.<ol><li>In Salesforce, go to Setup</li><li>In the Quick Find box, search for Manage Connected Apps</li><li>Click Manage Connected Apps</li><li>Select ScreenMeet from the list of connected apps</li><li>Click Edit Policies</li><li>Under Permitted Users, select Admin approved users are pre-authorized</li><li>Click Save</li></ol><h4>Create a Permission Set for the Connected App Access</h4>After updating the connected app policy, extend the assigned application access to ScreenMeet Agents, Supervisors, Beam Group Managers, and Administrators. This allows OAuth logins into <a target="_blank" rel="noopener noreferrer nofollow" href="http://console.screenmeet.com">console.screenmeet.com</a>.<ol><li>Go to Setup</li><li>In the Quick Find box, search for Permission Sets</li><li>Click Permission Sets</li><li>Click New</li><li>Create a permission set named ScreenMeet Console Access</li><li>Click Save</li><li>From permission set overview, click Assigned Connected Apps</li><li>Click Edit</li><li>Move ScreenMeet from Installed Connected Apps to Enabled Connected Apps</li><li>Click Save</li><li>Assign this permission set to ScreenMeet Agents, Supervisors, Beam Group Managers, and Administrators</li></ol><blockquote>For larger teams, we recommend adding this permission set to a permission set group. Alternatively, connected app access can be added at the profile level.</blockquote><hr><h3>Enter the Service Account Configuration in ScreenMeet Console</h3><ol><li>Open <a target="_blank" rel="noopener noreferrer nofollow" href="https://console.screenmeet.com">https://console.screenmeet.com</a></li><li>Select Salesforce for a production instance or Salesforce Sandbox for a sandbox instance</li><li>Sign in with a user account that has the ScreenMeet Admin permission set</li><li>If prompted, accept the Permission Entitlement authentication dialog for the ScreenMeet app</li><li>Go to Organization &gt; Settings and Policies</li><li>Click Salesforce Integration at the bottom of the menu</li><li>Enter the ScreenMeet Service Account username</li><li>If you enabled Set Audit Fields upon Record Creation, enable Override CreatedById (Requires Permission)</li><li>The following fields are only required for version 1.26 and older:<ul><li>ScreenMeet Service Account password</li><li>Security token</li></ul></li><li>Click Save</li><li>Click Configure and Validate Salesforce Org</li><li>If successful, this confirms that the ScreenMeet API and your Salesforce organization can communicate. It also updates the internal encryption keys used for communication between the platforms.</li></ol><hr><h3>Enable Set Audit Fields System Permission (Optional)</h3>In some cases, ScreenMeet sessions will be created on behalf of other users by the service account. In those cases, the&nbsp;Created By&nbsp;field will be populated as the Service Account by default. To have the&nbsp;Created By&nbsp;field display the user who requested the session, follow the steps below:&nbsp;<ol><li>Sign in as a System Administrator, then go to Setup</li><li>Search for&nbsp;User Interface&nbsp;in the Quick Find box</li><li>Click on&nbsp;User Interface&nbsp;from the search results (it will be at the bottom of the list):</li><li>In the&nbsp;Setup&nbsp;section, check the box for Enable&nbsp;“Set Audit Fields upon Record Creation” and “Update Records with Inactive Owners” User Permissions</li><li>Click&nbsp;Save</li><li>From the&nbsp;ScreenMeet Service System Permission Set Overview, open&nbsp;System Permissions</li><li>Click on&nbsp;Edit</li><li>Find&nbsp;Set Audit Fields upon Record Creation&nbsp;permission and enable it.</li><li>Click&nbsp;Save</li><li>Click&nbsp;Save&nbsp;on the confirmation dialog</li></ol><hr><h3>Troubleshooting Configure and Validate Salesforce Org</h3>If Configure and Validate Salesforce Org fails, review the following:<ol><li>Verify that the ScreenMeet Service Account username is correct</li><li>For version 1.26 and older, verify the password and security token are correct</li><li>Review the Salesforce login history for the ScreenMeet Service Account user</li><li>If no login attempts are shown, verify the username and confirm whether the correct production or sandbox option was selected in ScreenMeet Console</li><li>Confirm that the ScreenMeet Service Account user has the required permission sets assigned:<ul><li>ScreenMeet Service</li><li>ScreenMeet Service System Permissions</li><li>ScreenMeet Console Access (Only for versions 1.27+)</li></ul></li></ol>

Salesforce Service account setup

Service Account Setup

ScreenMeet 2025 Release Notes

403 Forbidden while making API request

404 NO_ACCESS

Installing ScreenMeet for Salesforce

Advanced CSS customization

AI Assist

AI Assist Overview

Overview

AI Release Notes Q4 24

Requirements

AI Summarization

AI Summary History

AI Summary Privacy

AI Summary Studio

Android SDK Quickstart

How-to: Setup the app for Laser Pointer

How-to: Display a video stream to the end-user

Egress IP Addresses

AWS S3 File Storage

Configuring ScreenMeet / Microsoft Entra ID integration

Signing into ScreenMeet console with Microsoft Entra ID (Azure AD)

Beam Client: Installation, Deployment, and Configuration Guide

Beam Groups: Setup, Settings, and Access Management

Beam Release Notes Q1 22

Beam Release Notes Q1 23

Beam Release Notes Q1 24

Beam Release Notes Q2 22

Beam Release Notes Q2 23

Beam Release Notes Q2 24

Beam Release Notes Q3 23

Beam Release Notes Q3 22

Beam Release Notes Q4 22

Beam Release Notes Q4 24

New Remote Support Client for Mac

Canvas

Certificate-Based Device Validation

Clone - Remote Support Release Notes Q4 23

Clone - Test ScreenMeet 2025 Release Notes

File Storage on AWS

Configuring Information Security & PII

Creating a Custom UI

Custom Copy

Cobrowse Demo

CoBrowse Deployments

Events

Hotkeys

Localization

CoBrowse Release Notes Q1 23

CoBrowse Release Notes Q1 22

CoBrowse Release Notes Q1 24

CoBrowse Release Notes Q2 22

CoBrowse Release Notes Q2 23

CoBrowse Release Notes Q2 24

CoBrowse Release Notes Q3 22

CoBrowse Release Notes Q3 23

CoBrowse Release Notes Q3 24

CoBrowse Release Notes Q4 22

CoBrowse Release Notes Q4 23

CoBrowse Release Notes Q4 24

Remote Control

Remove End Cobrowse Button

Cobrowse Script

Cobrowse Settings

Starting a Session with a URL

Configuration and validation troubleshooting

Configure API service

Configure ScreenMeet for a New Salesforce Sandbox

Configure ScreenMeet to only show on specified tables

Configuring Environment Variables

Configuring Webhooks for Data Sync

Connecting to ChromeOS devices

Connecting to Mac devices

Connection Information

Create Multiple Sessions

Creating a Replay Recording

Creating a session

Custom Consent Message

Custom permission configuration for ServiceNow

Custom URL

Custom Windows Tools

Deploying a Pre-installed Client

Developer Notes

Developer Notes (3.0.11)

Device Requirements

Enable ScreenMeet for Omnichannel Chat Widget

Enabling features within the Salesforce + ScreenMeet component