# Environment ## # unSkript Environments {% hint style="info" %} NOTE: Environments are only available online, and not in the Docker deployment. {% endhint %} It is pretty common to have multiple environments for your cloud (dev, staging, production, etc.), each using similar infrastructure, but with different credentials. With unSkript environments you can configure your xRunBooks to run in all of your environments with no modifications. This ensures that the XRunBook is the source of truth, and there is no worry about source control across your environments. ### Creating an Environment 1. Navigate to the Proxy you wish to add an environment to. Click "+Add Environment." You'll be prompted to name your environment
Naming your environment
2\. You'll next be prompted to select some of the services that will connect to the environment. In the example below, AWS and Slack are selected:
Connection picker
3\. Your environment will be created. Now, it is time to edit your Connectors. In the list of environments, click your new environment, and "Open Details."
screenshot of a new environment
Now, we will edit each Connection with the credentials needed to connect to the service. We have [detailed instructions](https://docs.unskript.com/unskript-documentation/connnecting/connectors) for each connection type. Additionally, add a ServiceId to each Connection. In this case, we'll use ServiceId with the format "\\_\" - meaning that we'll use 2 ServiceIds here: "test\_aws" and "test\_slack":
connectors with added credentials
Now, you can create a similar environment called "test\_production", and add in different credentials for AWS and Slack (but be sure to use the same ServiceId value):