Before you connect Salesforce

Use this checklist before connecting Salesforce to DOE. It helps avoid connecting the wrong org, skipping package setup, or starting mapping before the workspace is ready.

Confirm access

You can administer the Salesforce org that will be connected.
You can install or upgrade managed packages in that org.
You can approve the Salesforce OAuth consent flow.
You can access the target DOE space.
Your DOE email is verified if you will own re-authentication and disconnect actions.

Confirm the install lane

Salesforce package installation and DOE OAuth authorization must belong to the same release lane. The package install URL, Salesforce org, OAuth app metadata, callback URL, and backend environment should all point to the intended environment.

Do not treat a successful Salesforce sign-in as proof that the package, backend secret, callback, and token exchange all belong to the same lane. Verify the details panel after connection.

Recommended setup order

Open the Salesforce card in DOE Settings -> Integrations.
Install or upgrade the Salesforce package from the package link.
Confirm package access for admins, all users, or selected profiles.
Return to DOE and start Salesforce connection.
Choose the correct Salesforce username and org.
Review status, setup warnings, media sync, and polling.

What can wait

Record mapping, import, export, and widget rollout can wait until after Salesforce shows as connected. Start with a clean connection and a known integration owner, then run mapping in a controlled rollout.