- 09 Jul 2025
- 2 Minutes to read
- Print
- DarkLight
- PDF
Configure ScreenMeet for a New Salesforce Sandbox
- Updated on 09 Jul 2025
- 2 Minutes to read
- Print
- DarkLight
- PDF
How to Configure ScreenMeet for a New Salesforce Sandbox
It's important to understand that ScreenMeet identifies each Salesforce instance by its unique 18-digit Salesforce Organization ID, which we refer to as the External Id.
Every time you create or refresh a sandbox, Salesforce generates a new for it. Because of this, ScreenMeet will see the refreshed sandbox as a completely new ScreenMeet organization.
You will need to follow this guide to create and configure a new ScreenMeet organization every time your sandbox is refreshed, even if you are using the same sandbox URL as before.
Step 1: Prepare Your Salesforce Service Account
Before you can connect ScreenMeet, you need a dedicated ScreenMeet Service Account user in your new sandbox. How you prepare this user depends on your sandbox type.
For Full Sandboxes: A copy of your production service account user should already exist though the username may different (example: user@example.com.dev).
You will only need to reset its password and generate a new security token.
For Partial Copy, Developer Pro, or Developer Sandboxes:
The service account user will likely not exist or will not have the correct permissions.
You will need to create a new user account or update the existing one.
For instructions on how to create the service account and assign the correct permissions, please see our Salesforce Service Account Setup guide.
After setting up the user, make sure to set the password and generate a new security token.
Make sure you have the username, password, and security token for this service account user before proceeding.
Step 2: Create the ScreenMeet Organization
A ScreenMeet organization is not created for your new sandbox until the first time a user logs in from that environment. Any user with the "ScreenMeet Admin" permission set can complete this initial login.
From your Salesforce sandbox, identify a user who has the "ScreenMeet Admin" permission set assigned.
Have that user log in to the ScreenMeet Console at https://console.screenmeet.com using the Salesforce Sandbox button.
This initial login will create the new ScreenMeet organization and link it to your sandbox. Users with the "ScreenMeet Admin" permission set in Salesforce will be the administrators of this new org.
Step 3: Configure the Salesforce Integration
Next, you need to connect your new ScreenMeet organization back to your sandbox using the service account credentials you prepared in Step 1.
In the ScreenMeet Console, navigate to Organization and select Settings.
Click on the Salesforce tab.
Enter the Username, Password, and Security Token of your sandbox service account user.
Click Configure and Validate.
If the validation is successful, you will see a confirmation message.
Troubleshooting:
If the validation fails, it is usually because the username, password, or security token is incorrect. It could also mean the service account user is missing the required ScreenMeet permission sets in the sandbox. Please verify these details in Salesforce and try again.
Step 4: Request Settings Import
To save time on setup, you can ask our support team to copy the settings from your production org or another existing organization. This will import product settings and ensure your new sandbox org has the correct product licenses.
Please contact ScreenMeet support and provide the following information:
The Organization ID of your new sandbox org (found in the ScreenMeet Console under Organization > Settings).
The Organization ID of the source org you want to import settings from (usually your production org).