# Use Deployment

The Deployment area lets developers manage deployments of your commercetools Frontend project.

From **Deployment** in the **Developer** area, you can deploy a build and roll back to a previous build.

For further information on deployment, see [Deployment overview](/frontend-development/deployment.md).

![Deployments page in the Studio](https://docs.commercetools.com/frontend-studio/images/deployment-area.png)

## Deploy a build

To deploy a build version, follow these steps:

1. From the Studio home page or from the left menu, go to **Developer > Deployment**.
2. In the **Staging** or **Production** section, click **Deploy frontend and backend**: the **Builds available** dialog opens. The dialog displays the builds that you can deploy for that environment based on your Netlify settings. If a build cannot be deployed in production, it appears in the list of the production builds but it is greyed out.
3. Click the build you want to deploy. When you confirm the deployment, it is added to the queue and the short commit hash and the deployment status are displayed. You'll receive a notification in the Studio when the deployment is complete.

Do not deploy directly from Netlify. It causes issues with your deployment due to inconsistencies between builds.

## View deployment details

To view the details of the latest deployment, follow these steps:

1. From the Studio home page or from the left menu, go to **Developer > Deployment**.
2. In the **Staging** and **Production** sections, you will find the URL, short commit hash, and date and time of the build release for both frontend and backend builds. For backend builds, up to three short commit hashes are displayed.

You can view the status of deployments initiated by the Studio or the [CLI](/frontend-development/deployment#deploy-using-the-command-line) by clicking the **Deployments history** icon. A **Successful**, **Failed**, or **Scheduled** status is displayed next to each deployment.

The **Deployments history** does not display automatic deployments triggered by the Frontend development pipeline.

Do not deploy directly from Netlify. It causes issues with your deployment due to inconsistencies between builds.

A version mismatch error message appears next to the **Short commit hash** field if you trigger a deployment from the Netlify dashboard or if the [auto publishing lock](https://docs.netlify.com/site-deploys/manage-deploys/#locked-deploys) on Netlify is not active. You can resolve the problem by [creating a new deployment from the Studio](/frontend-studio/using-deployment-in-the-studio#deploy-a-build).

## Roll back deployment

To roll back a deployment, follow these steps:

1. From the Studio home page or from the left menu, go to **Developer > Deployment**.
2. In the **Staging** or **Production** section, click **Deploy frontend and backend**: the **Builds available** dialog opens. The dialog displays the builds that you can deploy for that environment based on your Netlify settings. If a build cannot be deployed in production, it appears in the list of the production builds but it is greyed out.
3. Click the build you want to roll back to.

## Related pages

- [Area overview page with navigation](/frontend-studio.md)
- [Previous page: Use Schemas](/frontend-studio/using-schemas-in-the-studio.md)
- [Next page: Use API keys](/frontend-studio/using-the-api-keys-area.md)