Documentation for JIRA 4.3. Documentation for other versions of JIRA is available too.
Global permissions are system wide and are granted to groups of users.
See also project permissions, which apply to individual projects.
This table lists the different global permissions and the functions they secure: Global Permission Explanation JIRA System Administrators Permission to perform all JIRA administration functions. JIRA Administrators Permission to perform most JIRA administration functions (see list of exclusions below). JIRA Users Permission to log in to JIRA. Browse Users Permission to view a list of all JIRA user names and group names. Used for selecting users/groups in popup screens (such as the 'User Picker'). Create Shared Object Permission to share a filter or dashboard globally or with groups of users. Manage Group Filter Subscriptions Permission to manage (create and delete) group filter subscriptions. Bulk Change Permission to execute the bulk operations within JIRA:
does not include JIRA Users permission. A user with JIRA System Administrators will be able to log in to JIRA without the JIRA Users permission, but may not be able to perform all regular user functions (e.g. edit their profile) unless they also belong to a group that has the JIRA Users permission.
does not include JIRA Users permission. A user with JIRA Administrators will be able to log in to JIRA without the JIRA Users permission, but may not be able to perform all regular user functions (e.g. edit their profile) unless they also belong to a group that has the JIRA Users permission.
Granting the JIRA Users permission to a group also means that all newly created users will be automatically added to that group, unless the group has the JIRA System Administrators permission (as it would be unwise to automatically grant the JIRA System Administrators permission to all new users).
- Bulk Edit *
- Bulk Move *
- Bulk Workflow Transition
- Bulk Delete *
( * subject to project-specific permissions.)
The decision to grant the Bulk Change permission should be considered carefully. This permission grants users the ability to modify a collection of issues at once. For example, in JIRA installations configured to run in Public mode (i.e. anybody can sign up and create issues), a user with the Bulk Change global permission and the Add Comments project permission could comment on all accessible issues. Undoing such modifications may not be possible through the JIRA application interface and may require changes made directly against the database (which is not recommended).
People who have the JIRA System Administrators permission can perform all of the administration functions in JIRA, while people who have only the JIRA Administrators permission cannot perform functions which could affect the application environment or network. This is useful for organisations which need to delegate some administrative privileges (e.g. creating users, creating projects) to particular people, without granting them complete rights to administer the JIRA system.
By default, the jira-administrators
group has both the JIRA Administrators permission and the JIRA System Administrators permission. If you need some people to have only the JIRA Administrators permission (and not the JIRA System Administrators permission), you will need to use two separate groups, e.g.:
jira-system-administrators
).jira-system-administrators
group everyone who needs to have the JIRA System Administrators permission.jira-system-administrators
group.jira-administrators
group.jira-administrators
group everyone who is a member of the jira-system-administrators
group.People who have the JIRA Administrators permission (and not the JIRA System Administrators permission) cannot do the following:
It is recommended that people who have the JIRA Administrators permission (and not the JIRA System Administrators permission) are not given direct access to the JIRA filesystem or database.
If you have a user limited license (e.g. personal license) and have reached your user limit, you will not be able to grant login permissions (i.e. jira-users permission) to any further groups without first reducing the number of users with login permissions.