# How to manage the dev and live environments with Batch?

A staging environment refers to a parallel server environment for testing websites and software applications in conditions as close as possible to the live environment, without compromising the organization's current data or interrupting its operations.

You should always integrate Batch in a development environment and then go into production mode after everything has been tested and validated.

For this matter, we strongly recommend:

{% stepper %}
{% step %}
Creating **two applications per OS** (Android, iOS, Web) on the dashboard: one for tests and one for production (e.g. *MyApp* and *\[DEV] MyApp*).
{% endstep %}

{% step %}
These apps will then be grouped into **two Omnichannel projects**.
{% endstep %}
{% endstepper %}

For instance:

<figure><img src="https://38998153-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCL8wF0y1T2vLnm3yR2MW%2Fuploads%2FOnWV8i5ojTdvaTjdadTQ%2Ftechnical-guides_dev-live-env_02052025.png?alt=media&#x26;token=3b9efe5c-9054-44d9-b737-e5ed994ece61" alt="Screenshot of the Batch dashboard showing two omnichannel projects in a dropdown menu (&#x22;The Store&#x22; and &#x22;[DEV] The Store&#x22;)"><figcaption></figcaption></figure>

{% hint style="info" %}
Thereafter, DEV projects can only be displayed to developers so as not to disturb your operational teams on the dashboard (refer to the [Project-level Permissions documentation](https://app.gitbook.com/s/UIK868wiiK9XOVyETGZS/features/customer-engagement-platform/settings/manage-team#project-level-permissions) for more details).
{% endhint %}