--- schema_version: "1" id: 1966df4fc5f192bba5680e632c96ed316cba667526a61fe9097d3f79dcb708be title: Migrate to the Storefront Developer Workspace (Beta) collection: developer version: current locale: en-us portal_url: https://docs.salesforce.com/developer/current/en-us/commerce-cloud/sfnext/guides/sfnext-mrt-migration.md canonical_url: https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/sfnext-mrt-migration.html source_site: developer.salesforce.com content_type: documentation content_hash: 77f661e4b02e83f42524cd2cf73fa2057df6d6ffbfbc8ce3e56521478b029df9 products: - Composable Storefront - Salesforce APIs --- # Migrate to the Storefront Developer Workspace (Beta) To manage the storefront development lifecycle in one interface, enroll in the Developer Workspace beta. Developer Workspace includes Managed Runtime resources in Business Manager for Storefront Next and Composable Storefront projects that are linked from Managed Runtime. For each storefront, the admin selects Business Manager or Runtime Admin as the tool to use to manage storefront development. Also, the admin also selects the API for that storefront: the SCAPI-based API or the MRT API. **important:** Developer Workspace is a pilot or beta service that is subject to the Beta Services Terms at [Agreements - Salesforce.com](https://www.salesforce.com/company/legal/agreements/) or a written Unified Pilot Agreement if executed by Customer, and applicable terms in the [Product Terms Directory](https://ptd.salesforce.com/). Use of this pilot or beta service is at the Customer's sole discretion. ## Step 1: Enroll in the Developer Workspace Beta To turn on the Developer Workspace beta in Business Manager: 1. In the Search box, enter `Feature Switches`, and then select **Feature Switches** from the suggested result. 2. Click **Enable Developer Workspace (Beta)**, and then click **Apply**. ## Step 2: Set Up Admin Permissions The storefront admin must have write access for the **UI and API Access** permission for the storefront. The Administrator role has this permission by default. During the beta, the admin must also have admin permissions for the corresponding Managed Runtime project. See [Users, Abilities, and Roles](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/mrt-overview.html#users-abilities-and-roles) in [Managed Runtime Overview](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/mrt-overview.html). Set up these permissions before you manage the storefront. ## Step 3: Choose an Admin User Interface and API 1. In Business Manager, select **Administration > Sites > Storefronts**, and then click your storefront. 2. Click **Storefront Settings > Management Interface**, and then click **Edit**. **important:** This user interface and API selection applies to the whole storefront and to its Managed Runtime project, if the storefront has one. The selection also applies to every environment and to the B2C Commerce instance. 3. Select the admin user interface for the storefront. - To use the developer tools in Business Manager as part of the beta, select **Business Manager**. - To switch a storefront from Business Manager back to Runtime Admin, select **Runtime Admin**. 4. Under **Storefront APIs**, select the option for your setup. Follow the on-screen instructions to create a SCAPI client and to update your continuous integration and continuous delivery (CI/CD) tools to use the new credentials. - **SCAPI**: Select this option to use the SCAPI-based API for Managed Runtime. This option uses the same B2C Commerce (SCAPI) authentication as other B2C Commerce APIs. - **SCAPI and MRT**: **(Recommended)** Select this option when you migrate an existing storefront. This option uses the MRT API and the SCAPI-based API. The SCAPI-based API uses SCAPI authentication. If your CI/CD tools use the MRT API, keep both APIs enabled so that automation keeps working while you move that automation to SCAPI. - **MRT**: To turn off SCAPI access and use only the MRT API, select this option. 5. Save your changes. ## Step 4: Grant Storefront Permissions to Users Grant these permissions before users work with storefront environments and deployments. - Business Manager access to the B2C Commerce instance. An admin grants this access in Account Manager. Add the Business Manager role that includes a filter for the B2C Commerce instance. See [Step 1: Give Users Business Manager Access](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/sfnext-users.md#step-1-give-users-business-manager-access). - Storefront module permissions in Business Manager, and per-storefront management permissions for environments, deployments, environment variables, and URL redirects. See [Step 2: Add Storefront Permissions in Business Manager](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/sfnext-users.md#step-2-add-storefront-permissions-in-business-manager). - A Managed Runtime project role for the corresponding Managed Runtime project during the beta. See [Users, Abilities, and Roles](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/mrt-overview.html#users-abilities-and-roles) in [Managed Runtime Overview](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/mrt-overview.html). ## Step 5: Create a SCAPI Client and Update Automation If you chose an API option that includes SCAPI: 1. In Account Manager, create an API client with the `SALESFORCE_COMMERCE_API` role and the `sfcc.storefront.*` scopes. See [Add an API Client in B2C Commerce](https://help.salesforce.com/s/articleView?id=cc.b2c_account_manager_add_api_client_id.htm&type=5) in _Salesforce Help_. 2. Update your CI/CD pipelines, scripts, and developer access to use the API that you selected. Point `b2c mrt` commands at that API. See [Automate Environment Administration with the Managed Runtime API](https://developer.salesforce.com/docs/commerce/sfnext/guide/sfnext-mrt-api.html). 3. Configure the `b2c mrt` commands to use SCAPI mode. See [MRT Commands: Authentication](https://salesforcecommercecloud.github.io/b2c-developer-tooling/cli/mrt.html#authentication). ## Frequently Asked Questions **Is switching the management interface to Business Manager reversible?** Yes. Switch a storefront back to Runtime Admin, or change the API option, at any time. Runtime Admin always stays available. **Is this a per-storefront choice or an all-or-nothing switch?** Per storefront. Each storefront is one Managed Runtime project, so the selection applies to every environment for that storefront (development, staging, and production). It doesn't apply to your other storefronts. Move one storefront at a time. **Do I log in to Runtime Admin?** Yes. Some capabilities remain in Runtime Admin. See the next question. **What remains in Runtime Admin during the beta?** These stay in Runtime Admin: - Managed Runtime CDN certificates and hostname (custom domain) management - Project notifications - User, API key, and notification management Everything else (environments, deployments and history, environment variables, URL redirects, and performance monitoring) is available in Business Manager. **Are Managed Runtime (Account Manager) roles still needed during the beta?** Yes. Business Manager permissions control which actions a user takes in Business Manager. Managed Runtime runs the operation, so assign each user a Managed Runtime project role in Runtime Admin that matches their Business Manager storefront role. Storefront operations require that Managed Runtime role in addition to the Business Manager permissions. This dependency is expected to be removed at GA. **Who can change a storefront's management interface?** During the beta, a user with **UI and API Access (Write)** in Business Manager and the Admin role on the Managed Runtime project can change the management interface. Business Manager Administrator status in the user's own instance isn't enough. This dependency is expected to be removed at GA. **Will opting in break my existing CI/CD or scripts?** Existing CI/CD and scripts keep working if the MRT API stays enabled. Select `SCAPI and MRT` so that existing automation keeps working. After your pipelines use SCAPI, switch to `SCAPI`. Only the APIs that you enable can change the storefront, so a pipeline that targets a disabled API stops working. **Is there an automated way to migrate my Managed Runtime roles to Business Manager?** No. Recreate each role as a Business Manager role. Use the permission model in [Set Up Roles and Permissions for Developer Workspace](https://docs.google.com/document/d/1Ekj9xADPUPoHOTufK8O3WMrYjDsEtDgbrttBP8DtCmM/edit?tab=t.0#heading=h.nu71dd9j2ecr). **Can I limit a user's access to a single environment?** No. Storefront permissions apply to every environment for a storefront. Scope a role to one storefront or to a group of storefronts in an instance. You can't scope a role to one environment in a storefront. This matches Managed Runtime, where roles apply to the whole project. Scope roles and API clients per instance. For example, withhold production so that a user can't reach its environments. **Why can't a user see the full storefront list?** The all-storefronts context controls whether a user lists every storefront. Grant the `Storefront` permission (Read) with the context set to all storefronts for roles that browse the complete list. A role scoped only to specific storefronts shows only those storefronts. ## See Also - [Manage Roles and Permissions for Your Storefront in Business Manager (Beta)](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/sfnext-users.md) - [Salesforce Help: Roles and Permissions in Business Manager](https://help.salesforce.com/s/articleView?id=cc.b2c_roles_and_permissions.htm) - [Link an Existing Storefront to B2C Commerce](https://developer.salesforce.com/docs/commerce/sfnext/guide/sfnext-link-storefront.html) - [Managed Runtime Overview](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/mrt-overview.html)