Using the latest version?
JFrog Platform User Guide
JFrog Artifactory 6.x Documentation
To get the latest version, go to the JFrog Unified Platform
Creating a Permission Target
To create a Permission Target, in the Permissions Management page click "New" to display the New Permission screen.
Permissions are broken into two types, Repositories and Builds. The artifactory-build-repository is not included in the repositories permissions.
You must provide a unique name for each Permission Target (limited to 64 characters).
Add Repositories and Builds
Select the repositories and/or builds to which this Permission Target applies. You can use the Any Local Repository or Any Remote Repository or Any Distribution Repository and Any Build check boxes as a convenience.
A summary of all the repositories, builds, and include/exclude patterns defined in this permission target.
Include and Exclude Patterns
Using an "Ant-like" expressions, you can specify any number of Include or Exclude Patterns in the corresponding entry field (limited to 1024 characters in total).
For the build info permissions,
When adding a build, an include pattern will be generated for its path in the build info repository. The expression will contain the build name as an Ant pattern.
Adding a build provides, the specified users/groups in this permission target, access to the corresponding path in the artifactory-build-info repository.
Also, the build permission targets define what a user has access to view in the Builds module in the Artifactory UI.
For example: In the permission targets module, if you are adding a build from the list, a corresponding pattern will be created for the relevant path in artifactory-build-info repository.
If providing a read permission to the selected builds (i.e. patterns), the user will also see those builds in the Builds module.
For example, to add a build with the name 'apache' (whether or not it exists in the repository yet), add the following include pattern: "apache/**".
To remove a build, delete its corresponding include pattern.
User and Group Permissions
Using the corresponding tabs, you can set the permissions granted to a user or a group. Double-click the user or group you want to modify to add it to the list of Principals, and then check the permissions you wish to grant.
You cannot add a user or group with admin privileges to a Permission Target
Since an admin is privileged with all permissions, you cannot add a user or group with admin privileges to a Permission Target.
Permissions are additive and must be explicitly granted. If a checkbox is not set for a user, then that user does not have the corresponding permission.
Available permissions for Repository Actions:
|Allows reading and downloading of artifacts|
|Allows annotating artifacts and folders with metadata and properties|
|Allows deploying artifacts and deploying to caches (i.e. populating caches with remote artifacts)|
|Allows deletion or overwriting of artifacts|
|Allows changing the permission settings for other users on this permission target|
Available permissions for Build Actions:
|Allows reading and downloading of build info artifacts and viewing the corresponding build in the Builds page|
|Allows annotating build info artifacts and folders with metadata and properties|
|Allows uploading and promoting build info artifacts|
|Allows deletion of build info artifacts|
|Allows changing build info permission settings for other users on this permission target|
Permission Target Managers
By assigning the Manage permission to a user, you may designate them as the "Permission Target Manager". These users may assign and modify permissions granted to other users and groups for this Permission Target. In the Artifactory UI these users have access to the specific users they are allowed to manage. This can be useful on a multi-team site since you can delegate the responsibility of managing specific repositories to different team members.
Preventing Overwriting Deployments
You can prevent a user or group from overwriting a deployed release or unique snapshot by not granting the Delete permission. Non-unique snapshots can always be overwritten (provided the Deploy permission is granted).
You can examine permissions in the context of repositories, users or groups.
In the Artifacts module, select repository you want to view in the Artifact Repository Browser and then select the Effective Permissions tab to see the permissions granted to users or groups for this repository.
By User or Group
For any user or Group, you can view the list of Permission Targets that it is associated with (whether directly or through membership in a group).
For users, In the Admin module, under Security | Users, select the user you wish to examine. The User Permissions are displayed at the bottom of the user's page.
You can similarly view Group permissions in the Admin module under Security | Groups.