Prod / Dev in Target

Hi @michael_soprano ,

The preset environments include Production, Staging, and Development. You can add new environments and rename your environments, if desired.

One environment, the default environment, is pre-named Production. This default environment cannot be deleted, even if you rename it. Target assumes that this is where you will serve final, approved activities and tests.

When a Target request is received from new websites or domains, these new domains always appear in the Production environment. The Production environment cannot have its settings changed, so unknown or new sites are guaranteed to see only content that is active and ready. Host management also lets you easily ensure the quality of new activities and content in your test, staging, and development environments before you activate the activities.

For more information refer this document for Environment:

https://experienceleague.adobe.com/en/docs/target/using/administer/environments

In Target Premium : An environment can be used to separate the available items in your catalog for different uses. For example, you can use host groups for Development and Production environments, different brands, or different geographies. By default, preview results in Catalog Search, Collections, and Exclusions are based on the default host group. (You can also select a different host group to preview results, by using the Environment filter.) By default, newly added items are available in all host groups unless an environment ID is specified when creating or updating the item.

Enterprise User Permissions

Enterprise User Permissions functionality lets you create different projects (called “Product Profiles” in the Adobe Admin Console for Enterprise). Enterprise User Permissions let you assign different permissions for a single user that dictate that user’s access rights for each project. These distinct projects can be compared to the way that report suites work in Adobe Analytics. Each project can have specific users with specific roles that apply to a set of properties. The result is that customers are able to restrict the view, edit, approval, and publish access to their users. You can restrict users based on region, environment (dev/stage/prod), channel, or other custom criteria.