A connection combines a sandbox hostname with an account, a target code version, and optional API and site settings. The active connection is the target used by workspace actions such as upload, logs, and debugging.
Before adding one, set up Credentials. Keep the project you want to configure open in the IDE.
Prepare the connection details
| Field | How to choose it |
|---|---|
| Name | A recognizable label such as Development. |
| Hostname | The sandbox hostname provided by your team, without a URL path. |
| Account | An existing Business Manager account from Credentials. |
| Code version | The version your team uses for development. Selecting an upload target and activating a version on the server are separate actions. |
| API clients | The stored clients needed by the API features you plan to use. |
| Site scope and cartridges | The site and cartridge path for the storefront you are working on. |
| Certificates | Configure these only if the sandbox requires certificate authentication. |
| Auto-upload | Check this before editing files. Keep it off while verifying a new target. |
Add a connection in VS Code
Open Explorer
Select Intellij SFCC in the Activity Bar, then open Explorer. This is the plugin's connection panel, separate from VS Code's file Explorer.
Add the target
Run Add B2C Connection from the panel or Command Palette. Enter a name and hostname, select the account from Credentials, and save the connection.
Activate and select the code version
Right-click the connection and choose Activate Connection. Use Change Code Version to select the intended version. Confirm the active target in Explorer and the status bar.
Verify remote access
Expand the connection and browse a remote folder. A successful listing confirms that remote access works; it does not require uploading a file. Check the selected site scope before using site-specific actions.
The VS Code Connections reference covers groups, certificates, code versions, and remote actions in detail.
Add a connection in JetBrains
Open B2C Explorer
Open View → Tool Windows → B2C Explorer, or select its tool window button.
Create the target
Use the Explorer connection controls to add a connection. Fill in its hostname and account reference; add API clients or certificate settings if required by your sandbox.
Select the active connection
Save, then use Select Connection in the toolbar or the Explorer context menu to make it active. Refresh code versions and select the version you intend to work with.
Verify remote access
Expand a remote folder in B2C Explorer. Confirm that the toolbar shows the correct connection and code version, then check the site scope for storefront work.
See Toolbar and Status for the everyday connection, code-version, and upload controls.
Switch targets deliberately
In VS Code, choose Activate Connection from the connection context menu or use the active connection status-bar picker. In JetBrains, use Select Connection. Selecting a row or using Focus Active Connection to reveal a row is not a substitute for activating it.
Before your next upload, confirm the new hostname, code version, and auto-upload state. Remote logs, debugging, and other connection-dependent views now use the selected target.
Import an existing team setup
Link the matching credentials file first, then import the connection metadata using your IDE's connection controls. Select the intended account and API clients if their references are missing. Review the imported hostname and code version before activating a connection.
Exports contain metadata and credential references, not the passwords or client secrets. They may still contain private hostnames or usernames; share them only with the intended team.
If verification fails
| What you see | What to check |
|---|---|
| The account is missing | Open Credentials and sync or add it, then select it again in the connection. |
| Authentication is rejected | Verify the account, host access key, and permissions expected by this sandbox. |
| The sandbox cannot be reached | Check the hostname and whether your organization requires a VPN or permits access on port 443. |
| Files are visible but API actions fail | Check the API client reference and its permissions separately from WebDAV access. |
| Local overrides or routes are unexpected | Confirm the project root, selected site, and cartridge path. |
Once the remote listing works, continue with VS Code cartridge management or JetBrains deployment.