---
title: "Permissions"
canonical: "https://support.appfire.com/space/JCLI/70788334/Permissions"
format: markdown
---
> Macro (aura-html)

# Description

The CLI access to information from JIRA is controlled by JIRA's permission model. The permissions granted to the user (and groups/roles it is a member of) specified on the CLI action determine what information if available and what actions can be run. Similarly, by denying some of these permissions, you can control what users are able to do via the CLI just like they are controlled via the UI. The general rule is that if you can't do something in the UI, then you can't do something via the CLI and vice versa. Even having JIRA administrator or system administrator permissions may not be enough. If you are not seeing the information you think you should in the CLI, check your permissions! Check both your global permissions and project permissions.

JIRA doesn't provide a complete list of what permissions are needed to do specific activities, either on the UI or for remote APIs. This can generally be accurately inferred from the descriptions available. In some cases the error messages will also help, but not always. For instance, in the case of missing access permissions, you will often get a **not found** error message even though the object may exist, but is not visible to the current user.

This page will list a few specific permissions that are common area for tripping up users of the CLI.

> ✅ **Automation user**
> ✅ 
> ✅ If you have an automation user that needs to do everything, then make sure it has all global permissions and all permissions in each project permission scheme!

# Global Permissions

> Macro (table-plus)
> 
> | **Permission** | **Description** | **CLI Implications** |
> | --- | --- | --- |
> | JIRA System Administrators | <span style="color: #505050">Ability to perform all general administration functions. Additional project specific permissions are still needed for project actions.</span> | Make sure all actions are available |
> | JIRA Administrators | <span style="color: #505050">Ability to perform most administration functions (excluding Import & Export, SMTP Configuration, etc.). </span><span style="color: #505050">Additional project specific permissions are still needed for project actions.</span> | Some administrative actions are available |
> | Browse Users | <span style="color: #505050">Ability to select a user or group from a popup window as well as the ability to use the 'share' issues feature. Users with this permission will also be able to see names of all users and groups in the system</span> | User lists and user management actions are available |

# Project Permissions

> Macro (table-plus)
> 
> | **Permission** | **Description** | **CLI Implications** |
> | --- | --- | --- |
> | Administer Projects | Ability to administer a project in JIRA | Make sure all actions are available |
> | Browse Projects | Ability to browse projects and the issues within them | Needed to see projects in a list or issues in a project EVEN for administrators |
> | Issue Permissions | <span style="color: #505050">Various</span> | Determines what actions can be done. |
> | Manage Watchers | Ability to manage the watchers of an issue | May restricts watcher actions |
> | View Voters and Watchers | Ability to view the voters and watchers of an issue. | May prevents this information from showing accurately in list and displays |
> | Comment Permissions | Various | Needed for various comment actions |
> | Attachment Permissions | Various | Needed for various attachment actions |
> | Time Tracking Permissions | Various | Needed for various work related actions |