Start here if this is your first project with Intellij SFCC. Pick your IDE and follow its Getting Started guide from installation through the first connection; you do not need to configure every feature at once
Choose your IDE
VS Code extensionVS Code
Install from Visual Studio Marketplace or Open VSX, sign in, and connect your first sandbox
- Install the extension and sign in to your account
- Open your cartridges, link credentials, and choose your sandbox
- Activate a personal subscription or an organization seat
JetBrains pluginJetBrains IDEs
Install from JetBrains Marketplace in WebStorm, IntelliJ IDEA, PhpStorm, or another JetBrains IDE and send your first change to a sandbox
- Install the plugin from JetBrains Marketplace
- Link your cartridges, add an account, and pick your sandbox
- Start the 7-day trial or activate a license
What you will set up
| Step | What you need | You are ready when… |
|---|---|---|
| Install and activate | A compatible IDE and access to your plugin account | The plugin is enabled and its plugin access is recognized |
| Open your project | Your existing source repository with its cartridges | The IDE can see your local cartridge files |
| Add credentials | A sandbox account or an existing team credentials file | The account is available in Credentials |
| Create a connection | Your development sandbox hostname and target code version | The saved connection is selected as active |
| Verify access | Permission to read the sandbox | Explorer can list remote files, and the selected code version is the one you intend to use |
Keep the three kinds of access separate
- Plugin access enables Intellij SFCC features. VS Code uses your Intellij SFCC account with a personal subscription, assigned organization seat, or trial; JetBrains uses its plugin licensing flow
- Sandbox credentials authenticate you to Business Manager, WebDAV, and related services. Store them in Credentials, then select the account in a connection
- API clients are needed for the API features you use. Add the appropriate client and permissions when setting up those features; you do not need every API configured to start editing code
Joining an existing team? Ask for the project repository, development sandbox hostname, intended code version, and your approved credentials setup. Your team's site scope and cartridge path help the IDE resolve overrides correctly
Already installed?
Configure VS Code
Go from an installed extension to a verified sandbox connection
Configure JetBrains
Set up credentials and the active connection in your IDE
Credentials
Create a credentials file or join an existing team setup
Connections
Understand connection fields, switching targets, and imports
Your first development task
Once remote access works, open a local script or ISML template and try completion or navigation. When you are ready to send a change to the sandbox, confirm the active connection, code version, and auto-upload state first
Continue with VS Code cartridge management or JetBrains deployment. For a failing request, use VS Code Log Center or JetBrains log files