Enabling the Code IDE for your workspace
Workspace owner master toggle, per-site editor surface choice, and how the two interact.
Two levels gate the Code IDE: a workspace-level master toggle (owner-only) and a per-site editor preference (anyone with design.edit). Both default off — the IDE is opt-in so existing sites don’t change behaviour the moment you upgrade.
Workspace master toggle
- Go to Settings → Code IDE. Owner-only — other members are redirected to their account page.
- Flip the switch on. The activity log records who flipped it and when, so you can audit later.
What changes when it’s on:
- Each Web Design site shows a Code editor button at the top of the editor (for users with design.edit).
- The
/projects/[id]/code/[siteId]route is reachable — without the master toggle, that URL bounces to the legacy workbench.
Flipping it off later doesn’t delete IDE-built content. Every site falls back to the legacy workbench regardless of its per-site preference; the IDE’s files stay on disk and re-appear if you turn the master toggle back on.
Per-site editor surface
Each site stores its own preference (LEGACY_WORKBENCH or CODE_IDE). Once the master toggle is on, you control this per-site via the switcher button on either surface:
- From the workbench: the Code editor button at the top. This move is permanent for a site whose pages are not yet files, and asks you to confirm first.
- From the Code IDE topbar: the Classic button is unavailable once a site’s pages are files, because the workbench cannot edit them.
The switch updates the preference first, then navigates, so a saved bookmark to either address always lands on the editor the site is actually set to use.
What happens to existing sites?
Every site starts on LEGACY_WORKBENCH (the default). Flipping the master toggle doesn’t change any site’s preference — it just makes the choice available. You have to click the per-site switcher to move a site over. That move is permanent once the site’s pages have become files.