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 pick the code version
Activate and select the code version
Hover the connection and click its Activate Connection inline action (lightning icon). Use Change Code Version if you need a different 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, and Connection Settings explains every setting a connection holds
Add a connection in JetBrains
Code versions
version1- [Active on instance]
app_custom
Log Files
IMPEX
Temp
Realm Data
Organization Static Content
Catalogs
Content Images (Library)
Velocity Templates
RefArch (3)Open B2C Explorer
Open View → Tool Windows → B2C Explorer, or select its tool window button
Create the target
Click Add... → Add Connection. Enter a Name, paste the instance URL into Hostname and choose the Account. Add an OCAPI client or certificate settings on their tabs if your sandbox needs them
Select the active connection
Click Test Connection and pick the Code Version you intend to work with. Changes save as you type, so close the dialog, then choose the connection in Select Connection in the main toolbar to make it active
Verify remote access
Expand the connection in B2C Explorer. Confirm that the toolbar shows the correct connection and code version, then check the site scope in the status bar for storefront work
See Connections for groups and connection settings, and Actions & Shortcuts for the everyday connection, code-version, and upload controls
Switch targets deliberately
In VS Code, click the Activate Connection inline action on the connection row 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. In VS Code, use Import Connections in the Connections view. JetBrains imports a project's dw.json once, when the project has no saved connections yet. 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