Environments

❗️
Important
Artifactory release 7.125.3 (released at the end of October 2025) introduces the concept of stages as a replacement for environments. This is a gradual change that is being implemented first with Release Lifecycle Management and AppTrust. Existing environments will continue to be supported until further notice. For more information, see Stages & Lifecycle.

Environments are used to aggregate project resources, such as repositories, to simplify their management.

Artifactory contains two default environments - DEV (Development) and PROD (Production), and additional custom environments can be created for specific projects, or for all projects, as needed. Each repository can be assigned to one or more environments, a feature that enables you to allocate repositories in ways that best serve the needs of your organization. Multiple repositories can be assigned to the same environment.

You can create custom environments at the global level, where they are available to users across all projects, or at the project level for the project's members. At the project level, specific roles can be assigned to custom environments, which enable you to implement a more granular permissions model for that project.

Environment Management Workflow

The following workflow illustrates how to create and manage environments.

	Procedure	Using the JFrog Platform UI	Using REST API
1	Create a global environment	Create a Custom Global Environment	Create Global Environment `POST ${baseUrl}/access/v1/environments`
2	Create a project environment	Create a Custom Project Environment	Create Project Environment `POST ${baseUrl}/access/v1/projects/{project_key}/environments`
3	Edit a global role and assign an environment	Assign Environments to Global and Project Roles	Edit a Global Role `PUT ${baseUrl}/access/v1/roles/{role}`
3	Create a custom global role and assign an environment	Create Custom Global Roles	Create a Custom Global Role `POST ${baseUrl}/access/v1/roles`
4	Create a project role and assign an environment	Create Project Roles	Create Role `POST ${baseUrl}/access/v1/projects/{project_key}/roles`
5	Assign repositories to each environment	Configuring a Local Repository	Update Repository Configuration Based on changes made in the Repository Configuration JSON.
6	Delete a custom environment	Delete a Custom Environment	Delete Global Environment `DELETE ${baseUrl}/access/v1/environments/{environment_name}`