Service Account Setup

Service Account Setup

A service account is required to allow your Salesforce organization to communicate with ScreenMeet's servers. This guide will outline how to set up your service account.

Create a new User

Create a new user in your organization that will be dedicated to the service account. We recommend minimizing access for this user as a security best practice. 

Assign the following permission sets to this service account: 

• ScreenMeet Service
• ScreenMeet Service System Permissions

The ScreenMeet Service permission set is created automatically during installation. 

You will manually create the ScreenMeet Service System Permissions permission in the next step.

Create the ScreenMeet Service System Permissions Permission Set

1. Go to Setup in your Salesforce organization.
2. Type "permission sets" in the Quick Find, then click on Permission Sets.
3. Click on New to create a new permission set and enter "ScreenMeet Service System Permissions" for the Label. Enter "ScreenMeet_Service_System_Permissions" for the API Name, then click Save.

Enable System Permissions

1. Open ScreenMeet Service Permission Set Overview > System Permissions.
2. Click on Edit.
3. Enable the following permissions:
   1. Apex Rest Services
   2. API Enabled
   3. Password Never Expires
      
   4. Customize Application
4. Click Save.
5. Click Save on the confirmation dialog.
6. Click on Manage Assignments for the Service Account Permission Set and assign it to the ScreenMeet Service user you created in the previous step.

Enable Set Audit Field 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: 

1. Sign in as a System Administrator, then go to Setup.
2. Search for "User Interface" in Quick Find.
3. Click on User Interface from the search results (it will be at the bottom of the list):
   
4. In the Setup section, enable the option called 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 theSet Audit Fields upon Record Creation permission and enable it.
   
9. Click Save.
10. Click Save on the confirmation dialog.
11. Click on Manage Assignments for the service account permission set.
12. Assign it to the ScreenMeet Service user you created in the previous stop

Create Security Token

1. Sign in to your Salesforce instance as the Service Account.
2. Click on your avatar in the top-right and then click on Settings.
3. Click Reset my Security Token from the menu on the left under My Personal Information.
4. Click the Reset Security Token button.

An e-mail will be sent to the address on the user account for the service account with the security token.

Enter Service Account configuration into ScreenMeet Console

1. Open https://console.screenmeet.com.
2. Click on Salesforce if using a production instance, or Salesforce Sandbox if using a sandbox instance.
3. Sign in with either the ScreenMeet Service account credentials or an account with the ScreenMeet Admin.
4. Click accept on the Permission Entitlement authentication dialog for the ScreenMeet app if it appears.
5. Click the Menu icon on the top left to open the menu, then click on Organization.
6. Then click on Organization > Settings and Policies.
7. Click on Salesforce Integration from the menu.

8. Enter your service account username, security token, and password into the corresponding fields then click Save Configuration.

   If you enabled Set Audit Fields upon Record Creation at the beginning of this section, be sure to enable Override CreatedById (Require Permission)
   
9. (Only for v1.12+) After Saving the configuration, click the configure and Validate Org button, This will let you know that the ScreenMeetApi and your Salesforce Org can communicate. This will also update internal encryption keys used to communicate between the platforms.
   

Next: Permission Assignment