Service Account Setup

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.

Create the ScreenMeet Service Account User

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

2. Name this user: ScreenMeet Service Account

3. Document the new user’s username and password as these will be needed later

4. Assign the following permission sets to the service account user:

   • ScreenMeet Service (This permission set is created automatically during installation)

   • ScreenMeet Service System Permissions (This permission set will be manually created in the next section)

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.

Create and Configure the ScreenMeet Service System Permissions Permission Set

1. Go to Setup in Salesforce

2. In the Quick Find box, search for Permission Sets

3. Click Permission Sets

4. Click New

5. Enter ScreenMeet Service System Permissions for the label

6. Confirm the API Name auto-fills as ScreenMeet_Service_System_Permissions

7. Click Save

8. From the ScreenMeet Service System Permissions permission set, click System Permissions

9. Click Edit

10. Enable the following permissions:

    • Apex REST Services

    • API Enabled

    • Customize Application

11. Click Save

12. Click Save again on the confirmation dialog

13. Click Manage Assignments

14. Assign the permission set to the ScreenMeet Service Account user

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.

ScreenMeet package version 1.26 and older

Create Security Token

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

2. Click on your avatar in the top-right and click Settings

3. Click Reset my Security Token from the menu on the left under My Personal Information

4. Click the Reset Security Token button

5. An e-mail will be sent to the email address of the ScreenMeet Service Account user with the security token

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&setupid=ResetApiToken

For example:

https://yourorg.lightning.force.com/_ui/system/security/ResetApiTokenEdit?retURL=%2Fui%2Fsetup%2FSetup%3Fsetupid%3DPersonalInfo&setupid=ResetApiToken

ScreenMeet package version 1.27 and newer

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.

1. In Salesforce, go to Setup

2. In the Quick Find box, search for Manage Connected Apps

3. Click Manage Connected Apps

4. Select ScreenMeet from the list of connected apps

5. Click Edit Policies

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

7. Click Save

Create a Permission Set for the Connected App Access

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 console.screenmeet.com.

1. Go to Setup

2. In the Quick Find box, search for Permission Sets

3. Click Permission Sets

4. Click New

5. Create a permission set named ScreenMeet Console Access

6. Click Save

7. From permission set overview, click Assigned Connected Apps

8. Click Edit

9. Move ScreenMeet from Installed Connected Apps to Enabled Connected Apps

10. Click Save

11. Assign this permission set to ScreenMeet Agents, Supervisors, Beam Group Managers, and Administrators

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.

Enter the Service Account Configuration in ScreenMeet Console

1. Open https://console.screenmeet.com

2. Select Salesforce for a production instance or Salesforce Sandbox for a sandbox instance

3. Sign in with a user account that has the ScreenMeet Admin permission set

4. If prompted, accept the Permission Entitlement authentication dialog for the ScreenMeet app

5. Go to Organization > Settings and Policies

6. Click Salesforce Integration at the bottom of the menu

7. Enter the ScreenMeet Service Account username

8. If you enabled Set Audit Fields upon Record Creation, enable Override CreatedById (Requires Permission)

9. The following fields are only required for version 1.26 and older:

   • ScreenMeet Service Account password

   • Security token

10. Click Save

11. Click Configure and Validate Salesforce Org

12. 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.

Enable Set Audit Fields System Permission (Optional)

In some cases, ScreenMeet sessions will be created on behalf of other users by the service account. In those cases, the Created By field will be populated as the Service Account by default. To have the Created By field display the user who requested the session, follow the steps below: 

1. Sign in as a System Administrator, then go to Setup

2. Search for User Interface in the Quick Find box

3. Click on User Interface from the search results (it will be at the bottom of the list):

4. In the Setup section, check the box for Enable “Set Audit Fields upon Record Creation” and “Update Records with Inactive Owners” User Permissions

5. Click Save

6. From the ScreenMeet Service System Permission Set Overview, open System Permissions

7. Click on Edit

8. Find Set Audit Fields upon Record Creation permission and enable it.

9. Click Save

10. Click Save on the confirmation dialog

Troubleshooting Configure and Validate Salesforce Org

If Configure and Validate Salesforce Org fails, review the following:

1. Verify that the ScreenMeet Service Account username is correct

2. For version 1.26 and older, verify the password and security token are correct

3. Review the Salesforce login history for the ScreenMeet Service Account user

4. If no login attempts are shown, verify the username and confirm whether the correct production or sandbox option was selected in ScreenMeet Console

5. Confirm that the ScreenMeet Service Account user has the required permission sets assigned:

   • ScreenMeet Service

   • ScreenMeet Service System Permissions

   • ScreenMeet Console Access (Only for versions 1.27+)