Before you start
What you need
- A user of the Salesforce org you want to connect, for example the UAT sandbox. Use a Salesforce admin, or a user who may approve apps that are not installed in the org yet.
- Admin rights in your UAT Studio workspace.
- Does your org only allow its own sign-in page? Then have its My Domain address at hand, for example yourcompany--uat.sandbox.my.salesforce.com.
No password or tokenYou sign in on the page of Salesforce itself. UAT Studio never sees your Salesforce password; Salesforce gives it access that you can revoke at any time.
Set up · once per org
Connect an org
1
Add Salesforce in UAT Studio
In UAT Studio, open your workspace and click Connections. Under Add a connection, choose Salesforce and click Add. Give the connection a name that says which org it is, for example Salesforce · UAT sandbox, and click Save settings.
2
Sign in to Salesforce
- Under Where to sign in, choose Sandbox (test.salesforce.com) for a sandbox, Production or Developer Edition (login.salesforce.com) for production, or My Domain address of the org and fill in that address.
- Click Connect Salesforce. The sign-in page of Salesforce opens.
- Sign in with a user of that org. Salesforce asks whether UAT Studio may have access: click Allow.
- You come back to Connections. The card shows Connected, the name of the org, Sandbox or Production, and the user who connected.
Test more orgs, for example a UAT sandbox and a training sandbox? Add Salesforce once more for each org.
3
Choose the org per project
Open the project and go to Setup. Set CRM to Salesforce, then choose the org under Salesforce org. The choice is saved straight away.
Using it
Test, connect again, disconnect
| Button | What it does |
|---|---|
| Test connection | Signs in to the org again and shows its name. The card shows when the connection was last used. |
| Connect again | Signs in again, for example with another user or after the access was revoked. |
| Disconnect | Revokes the access in Salesforce and forgets it in UAT Studio. The projects keep their choice, so connecting again brings everything back. |
| Remove | Deletes the connection; the projects that used it no longer have an org. |
What UAT Studio readsThe name of the org and the user who connected; with Release readiness, the counts of what the org has, such as leads, cases and active flows, never the content of records; and the user stories you choose to read. It never changes data in Salesforce.
Roles
Who can do what
Workspace adminAdds, connects, tests, disconnects and removes the org, and chooses it per project.
Salesforce adminSigns in and allows the access, and can revoke it in Salesforce at any time.
Testers and stakeholdersTest as always. They don't see the connection.
Help
If something goes wrong
| You see | What to do |
|---|---|
| Salesforce says the user may not approve the app | Your org only lets some users approve apps that are not installed yet. Sign in with a Salesforce admin, or ask your admin for the permission Approve Uninstalled Connected Apps. |
| Salesforce was not given access | You clicked Deny or closed the page. Click Connect Salesforce and choose Allow. |
| The sign-in page says the address is not valid | Choose the right place under Where to sign in: a sandbox signs in at test.salesforce.com. With My Domain, fill in the address without the path, such as yourcompany.my.salesforce.com. |
| Connection lost | Salesforce no longer accepts the access: it expired, or someone revoked it in Salesforce. Click Connect Salesforce to sign in again. |
| The sign-in took too long | Start again with Connect Salesforce and finish the sign-in within 15 minutes. |
Still stuck? Mail [email protected] with the message you see. Never send us a password.
Security
How we handle the access
- You sign in on the page of Salesforce itself (OAuth with PKCE). UAT Studio never sees your Salesforce password.
- UAT Studio asks only for access to the Salesforce API and to stay connected, so you don't have to sign in again every time.
- The access is stored encrypted (AES-256) on our server, never in the browser. The key to decrypt it is kept separately from the database. Nobody can read it back: not in the app, not through support.
- Your Salesforce admin sees UAT Studio in Salesforce under Setup › Connected Apps OAuth Usage and can revoke it there; Disconnect in UAT Studio does the same.