Environments

Environments are partitions within the platform that you can assign Project Releases to.

Each Environment isolates the Project Template's resources such that Subscribers to each Environment see the Projects deployed there, and dashboard submission widgets only include relevant submissions in their data.

As a Tenant Admin you will have the ability to add any additional Environments to meet the needs of your Project deployment workflows.

Environment Types

We have 4 predefined Environment types available for you to select from:

1. Production
2. Pre-Production
3. Test
4. Dev

See the descriptions in the image above for an example of how each of these Environment types could be used.

When a user starts a Project, if they have Project Templates deployed to them from Environments other than Production, the Template will be visually tagged with the Environment name, so that the different stages of the template deployment process do not get mixed up. Production is left blank so that users who only see production-environment deployments don't see any unnecessary information.

Environment Configuration

Before you start releasing project templates, you should make sure you have set up your environments correctly to allow you to release the project templates in the way you want.

Creating a new environment is simple:

1. Click on project Environments
2. Click Create New Project Environment 
3. Give your Environment a name and description
4. Select an environment type and click save

You have the ability to create multiple environments per type, so if you want to separate development type environments per developer, have different test type environments for different legal areas or different production type environments for data collection purposes - you can.

Any outside tenancies you release to will be able to see the name of the environment the template was released to, but not the type. For cases where there are multiple environments per type, we suggest adopting a naming convention that includes reference to the type to ensure your subscribers are clear about what stage in your development and release process the template is currently at.

You now have the ability to link a Project Template Release to an Environment. This allows you to set subscribers per environment per template, so that only the relevant tenancies and their own particular sets of users are able to receive your template deployments.

You can find out more about subscribers, releases and deployments in our articles:

• Project Release Management
• How do I make a deployed template accessible to my users?