How Environments work in Jet Admin
Environments allow you to have multiple configurations of your project within Jet Admin. If you want to update the resource, add a new one, change the settings or alter the UI, you can do it safely in a separate environment, whether it's staging or dev, and after the changes are reviewed and approved you can merge this new configuration into the production version. You also can create separate environments to control the updates: test the update on the staging environment and then push it into production.
By default, any new project is created in the production environment. To quickly add a new environment you need to click Add Environment button in project settings and then merge from the existing production environment into the new one.
Now you have a full copy of your production version where you can change, test, and troubleshoot without affecting the production version of the project.
To make sure your users always use a stable version of Jet, you can lock the production version of the project in the Production environment, and set the project version to "Latest" in the staging environment. This will keep the staging version up to date and allow you to test any new update prior to approving it for production.
Once you've made the changes in the staging or development environment, you can transfer those changes onto the production or any other environment. For that, in any environment click Merge environment. Then select the environment you'd like to apply changes from and the environment you'd like to apply those changes for and click Merge.
Any user who is invited into an existing environment can switch between environments. Hover your mouse over the project icon (top right) and then select an environment from the drop-down.