ARTIFACTORY: Best Practices for Handling Permissions and Establishing Separations Between Your Development Teams

Knowing how to best implement and manage permissions for organizational teams is an
indispensable skill. Knowing how to handle these permissions in Artifactory will allow you to:

1. Right size access to projects by granting permissions to relevant teams only.
2. Prevent deletions/overwriting of one team's files by another.
3. Optimize individual team performance by preventing them from seeing projects that are irrelevant to their current assignments.

To achieve these objectives, it's important to follow best practices for structuring and naming
Artifactory repositories. After implementing a repository naming convention in Artifactory, you can
begin creating groups and dividing your users into them. Doing so lets you quickly assign permissions
to entire teams, which is far more efficient than always having to manage individual users.

Thereafter, we recommend the creation of permission targets for each team represented in a given
a repository. If you'd really like to establish a highly organized and practically invulnerable
environment, create separate repositories for each of your teams and extend to those teams only
the permissions they need to fully and competently execute their tasks and goals.