> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trophy.so/llms.txt
> Use this file to discover all available pages before exploring further.
# Environments
> Learn how to use environments to help you test and review changes before releasing to production.
What are Environments?
Environments are core structures in Trophy that help you isolate data according to your team's development workflows and copy changes between them.
Types of Environments
Trophy supports three types of environments, each with a different use case in your development workflow:
* Production - Each Trophy account has **exactly one** production environment. This is the default environment and is the one that should be used to store live data from your application.
* Staging - Each Trophy account can have **multiple** staging environments. Staging environments can be used to map to different stages of your development workflow, like QA, UAT, or Pre-Production.
* Development - Each Trophy account can have **multiple** development environments. Development environments can be used to test new features or changes to your Trophy account without affecting other environments.
Switching Between Environments
You can switch between environments by clicking the environment selector in the top left of the screen or the dedicated [environments page](https://app.trophy.so/environments).
When you're in a non-production environment, you'll see a banner across the top of the screen reminding you that you're not in production.
This is to remind you that any changes you make in non-production environments are not automatically propagated to production, and to follow the correct [workflow](#change-tracking-and-propagation) for copying changes between environments.
Creating Environments
New environments can be created in the Trophy dashboard through the environment selector in the top left of the screen or the dedicated [environments page](https://app.trophy.so/environments). Either way the process is the same.
Choose a name for the environment that will help you identify it.
Choose a unique key for the environment. This cannot be changed after creation.
* Use Staging for environments you want to use to model your team's official test environments like QA, UAT, or Pre-Production.
* Use Development for environments you want to use to test new features or changes to your Trophy account without affecting other environments.
Choosing to clone an existing environment will create the new environment as an exact copy of the source environment, including all current data and settings.
We recommend cloning new environments from Production to ensure you have a clean starting point and avoid laborious initial data setup.
Save the new environment.
Change Tracking and Propagation
Here we outline Trophy's model for change tracking and propagation across environments and how you can use this to model your team's development workflow.
When using [multi-tenancy](/platform/multi-tenancy), changes are **not** automatically propagated between environments. Instead, environments are treated as totally isolated from each other in order to allow for maximum flexibility in how you can use Trophy.
Environment Priority
Environment priority is fundamental to how change tracking and propagation works across environments in Trophy.
Each [type of environment](#types-of-environments) in Trophy follows a natural priority order based on its use case in your development workflow.
As Production environments represent live data, these have the highest priority. Similarly, Staging environments are used to test and review changes before releasing to production, so they have a higher priority than Development environments.
1. Production (highest priority)
2. Staging
3. Development (lowest priority)
When created, new environments are automatically added as the lowest priority environment of their type. However, you can change the order of Staging environments to control the natural direction in which changes are propagated between them.
You cannot change the order of Development environments. All Development environments in Trophy have the same priority.
Change Tracking
Trophy automatically keeps track of changes made in each of your environments and detects differences between them.
This allows you to work on changes in isolation and only copy them to the next environment in your workflow when you're ready with the confidence that Trophy will keep track of your work.
Changes between environments are detected and tracked from the highest [environment priority](#environment-priority) to the lowest.
If you've ever worked with [git](https://git-scm.com/) before, you'll be very familiar with how environments work in Trophy.
Viewing Changes
When changes are made in non-production environments, they are not automatically propagated to Production. Instead, they are isolated within the environment they were made in until you copy them to another environment.
You can view the changes made in each environment relative to another target environment by clicking the environment selector in the top left of the screen and selecting 'View Changes'.
Here Trophy highlights all the changes detected between your current environment and your target environment. By changing your target environment, you can see changes between your current environment and other environments in your account.
Copying Changes
On the view changes screen you can copy changes to your chosen target environment by clicking the 'Copy All Changes' button. This will apply the changes listed to your target environment. Once the process is complete, your target environment will be up to date with your current environment and you can continue to make new changes.
Reverting Changes
On the view changes screen you can revert specific changes by clicking the 'Revert' icon next to each change you want to revert.
Reverting changes will remove them from your current environment and cannot be undone.
Change Propagation
When a change is made in an environment, it is propagated to all environments with a lower [environment priority](#environment-priority) automatically. This keeps all environments in sync with their natural direction of propagation and saves time in copying changes manually.
This means when you make changes in a Production environment, they will be automatically propagated to all Staging environments and all Development environments.
Similarly, when changes are made in a Staging environment, they will be automatically propagated to all other Staging environments with a lower priority and all Development environments.
Finally, when changes are made in a Development environment, they will not be propagated to any other environments.
Frequently Asked Questions
Here's how many environments you can have based on type:
* Production - 1
* Staging - 4
* Development - 10
If you feel you need more environments, please [get in touch](#get-support) and we'll be happy to discuss your needs.
You can copy changes between environments by clicking the 'Copy All Changes' button on the view changes screen.
Yes, you can delete an environment by clicking the 'Delete' button on the environments page.
Yes, you can rename an environment by clicking the 'Rename' button on the environments page.
Yes, you can clone an environment by clicking the 'Clone' button on the environments page.
Yes, you can change the order of Staging environments by clicking the action menu on the environment you want to move and selecting 'Move up' or 'Move down'.
You cannot change the order of Development environments. All Development environments in Trophy have the same priority.
Get Support
Want to get in touch with the Trophy team? Reach out to us via [email](mailto:support@trophy.so). We're here to help!