Required permissions

This article describes the Jira permissions required for GitProtect.

By understanding the scope of resources that need protection, you can determine whether full Jira admin access or project-level administration is the appropriate level of permission.

---

Jira permissions

A Jira admin is needed to secure a company-managed space and any global resources that team-managed spaces might use. If you only need to secure certain team-managed spaces that do not rely on global resources, project-specific administrative permissions are sufficient.

A Jira admin is required to secure not only a specific space but also the broader set of global resources and company-managed spaces that may be accessed or shared by team-managed spaces. This includes configuring permissions, controlling access to issue types, workflows, and schemes, and ensuring that any global configurations—such as shared dashboards, filters, or automation rules—are properly protected. Granting Jira admin permissions allows a user to manage these settings comprehensively, ensuring consistent security and governance across all company-managed and team-managed spaces that rely on shared resources.

If your requirement is limited to securing only certain team-managed spaces that do not use global resources, assigning administrative permissions at the project level is typically sufficient. In this case, the administrator can manage roles, permissions, and settings specific to that project without needing access to global configurations. This approach minimizes the risk of accidental changes to other parts of the Jira instance while still providing the necessary control over the selected spaces.