In Data360 DQ+, an "Environment" is the space in which data definition, data visualization and data analysis take place. Your organization might want to create multiple environments for different use cases, with each environment containing only what its users need. You can enforce security within an environment by limiting access to certain sets of data. For example, an organization could have two types of Data360 DQ+ users: developers and business users. The developers are responsible for creating new dashboards and analytics, while business users are only interested in using them. You could create a Development, Testing, and Production environment and then restrict the access to each environment by creating environment groups, so that developers only have access to the Development and Testing environments and business users only have access to the Production environment.
The majority of Data360 DQ+ items are environment specific, meaning that if you create the item in one environment it will not exist in another environment, unless the item is promotable and you promote it. For more information about promotion, see Pipelines. There are two exceptions to this rule:
- Users and groups automatically exist across environments, see Users.
- Environment groups can be configured to exist across environments by giving different environment groups in separate environments the same name, see Managing environment groups.
The currently selected environment is shown in the top right corner of the screen.
Administering across environments
The following diagram gives an example of how a user might work across multiple environments and pipelines, illustrating the relationship between incoming data and all the different types of data stages that can be produced.
Data360 DQ+ overview diagram
Next, see Managing environment groups.