Workspaces in development mode allow you to link, publish, and install apps. These workspaces provide greater development freedom since they do not handle traffic from any user except yourself.

Because development workspaces do not have any level of user traffic, you should use them whenever you want to perform changes in your code. Note: Development workspaces cannot be promoted to Master nor used for A/B testing. Only Production workspaces have these capabilities.

1. Log in to the desired VTEX account.
2. Run the following command:

Remember to replace the value in the curly brackets according to your store scenario and needs.

Once created, the Developer workspace has no expiration date, which means that settings will remain stored in it unless there is a conflict with the store's master workspace configurations. In these cases, the master settings will always prevail over the settings of other account workspaces, including the Developer one in which you are working, since account workspaces work as a copy of the version available to end users.

Stick to the list of workspaces created for your account and keep a shortlist for two reasons:

• Organizational purposes.

• Spare platform infrastructure resources.

Currently, there is no automated service responsible for deleting unused workspaces from an account. This means you must manually delete workspaces that are no longer in use by running the command vtex workspace delete {workspaceName}.

Be aware: once you delete a workspace, it is not possible to restore it and its content.

Once you are sure of the changes performed in the development workspace, it is time to create a production workspace to test your changes with some user traffic.

The production workspace does not inherit the changes made in the development workspace. Any changes made in the development workspace will need to be replicated in the new production workspace.

Creating a development workspace is one of the steps to make your code new version publicly available, allowing it to be accessed by your end users. For more details on the next steps and to better understand the complete flow, please refer to the documentation on making your new app version publicly available.