Data Quality user documentation
home/Data quality/Aperture Data Studio v2/Collaborate and re-use data/Manage Environments

Manage Environments

An Environment is the highest level of segregation, only sharing the hardware, license entitlements, system settings, plus any custom steps/parsers and address reference files installed.

A user will only be able to access an Environment once they have been assigned a Role in that Environment.

Multiple Environments might be used for development and test processes. Changes to Workflows, Functions, and other objects can then be synched to an Environment with limited user access when ready.

Managing Environments

1. Create an Environment

Only the Super admin, or a user with the Installation manager setting enabled on their user profile can create new Environments.

  1. Click the user icon in the top right corner and select Manage Environments.
  2. Click on Create Environment.
  3. Fill in the Name and the External label.
  4. Set the configuration options and settings.

2. Switch between Environments

This is only applicable for users with access to more than one Environment (i.e. at least one role in two or more Environments). These users also have the option to select an Environment at the login screen.

  1. Click the user icon in the top right corner and select Manage Environments or click the Environment label in top right corner if it is being displayed.
  2. On the Environment list screen, click on the URL of the Environment you want to access.

Environment level configurations and settings

The Super admin, or a user with the Installation manager setting enabled, can set default configurations and settings for each Environment.

Setting Description
Show Environment display name in main navigation header bar When checked, Environment name is displayed next to the Space name in the top menu.
Reduce system auditing Provides the option to limit the captured events in the audit log to security configuration events.
Audit retention period (days) Sets the retention period (in days) for the audit logs. Older logs will automatically be deleted upon startup of the Database Server.Job detail retention limit (days)
Maximum days for API Keys Sets the maximum days for the API keys expiry. Once set, all API keys created in this environment cannot have a larger Number of days to expiry than the defaulted value.
Apply default data retention for all new Datasets Allows you to set the default number days for the Automatically delete older batches after N days setting for datasets that are newly created.
Allow users to update retention days Used in conjunction with the previous setting, this allows users to overwrite the defaulted value as required for each newly created dataset.
Aperture Data Studio v2

Collaborate and re-use data