How to add a permission scheme in Jira

In the dynamic realm of project management, Jira stands tall as a powerful tool that aids teams in orchestrating complex workflows and achieving seamless collaboration. One of the cornerstones of effective project management within Jira is the implementation of robust permission schemes. In this comprehensive guide, we will delve into the intricacies of adding a permission scheme in Jira, equipping you with the knowledge to fine-tune access controls and safeguard the integrity of your projects.

Understanding the Essence of a Permission Scheme:

Before we embark on the journey of adding a permission scheme, let’s take a moment to understand its significance. In Jira, a permission scheme acts as a guardian, governing who can execute specific actions on issues within a project. This not only streamlines the workflow but also ensures that only authorized individuals can make crucial changes, mitigating the risk of unauthorized alterations that could potentially disrupt the project’s rhythm.

The Role of Permission Schemes in Project Governance:

Imagine a scenario where multiple team members collaborate on a project, each with distinct roles and responsibilities. A permission scheme plays a pivotal role in delineating who can create, edit, delete, or transition issues. By defining these permissions based on user roles, the permission scheme becomes a cornerstone of project governance, aligning the project with organizational policies and best practices.

Jira BigPicture vs MS Project Choosing Your Project Powerhouse

Step-by-Step Guide: Navigating the Labyrinth of Adding a Permission Scheme in Jira

1. Navigating to Project Settings:

The journey begins with logging into your Jira instance and selecting the project where you intend to implement the permission scheme. Once within the project, navigate to the left-hand menu and click on “Project Settings.”

2. Accessing Permission Schemes:

Within the Project Settings, under the “Permissions” category, locate and click on “Permission Schemes.” This is where the magic happens — where you sculpt the rules that will govern your project.

3. Creating a New Permission Scheme:

Click on the “Add Permission Scheme” button, and a new canvas opens for you to craft your permission masterpiece. Provide a name and description for the new scheme, ensuring clarity for anyone who interacts with it.

4. Defining Permissions:

The heart of the permission scheme lies in the meticulous assignment of permissions to each user role. As you tailor these permissions, consider the unique needs and responsibilities of each role within your project. Common permissions include the ability to Create Issue, Edit Issue, Delete Issue, Transition Issue, and more.

5. Associating the Permission Scheme with a Project:

Return to the project settings, and under the “Issues” category, select “Permissions.” Here, you will seamlessly associate the newly created permission scheme with your project, ensuring that the defined permissions come into effect.

6. Testing the Configuration:

A crucial step in the process is to validate that the permission scheme aligns with your project’s requirements. Test various user roles to ensure that the permissions are set up to support a smooth and secure project environment.

Congratulations! You have successfully added a permission scheme in Jira, placing you in the driver’s seat of project management control.

What is a JIRA ticketing system

External Resources

  1. Jira Default Permission Schemes
  2. Configuring Issue Security

FAQs and External Resources:

As you embark on your journey to master Jira’s permission schemes, it’s natural to encounter questions. Let’s address some frequently asked questions and provide external resources to further enrich your understanding.

Q1: What are the default permission schemes in Jira?

Understanding the default settings is fundamental. Atlassian’s documentation on Jira Default Permission Schemes provides insights into the foundational permission structures.

Q2: How can I customize permissions for specific issue types?

For a more nuanced control over permissions, delve into Configuring Issue Security. This resource guides you through setting up issue-level security to control access based on specific criteria.

Q3: Can I delegate administration tasks without compromising security?

Delegated Administration in Jira is a powerful feature. Learn more about it in Atlassian’s guide on Delegated Administration.

Q4: Are there best practices for permission schemes in Jira?

Yes, indeed! Atlassian’s blog on Jira Permission Schemes Best Practices offers valuable insights into optimizing your permission schemes for maximum efficiency and security.


Adding a permission scheme in Jira is not merely a checkbox in your project settings; it’s a strategic move toward mastering project control. Through this comprehensive guide, coupled with external resources and FAQs, you’ve gained a robust understanding of Jira’s permission management capabilities.

As you tailor permission schemes to your project’s unique needs, remember that empowerment goes hand in hand with responsibility. Your newfound knowledge is a key to unlocking the full potential of Jira for your team. Empower them to work efficiently and securely by implementing permission schemes that not only meet but exceed the demands of your dynamic projects. May your projects flourish under the guidance of your finely-tuned permission scheme!

Supercharge Your Collaboration: Must-Have Microsoft Teams Plugins Top 7 data management tools Top 9 project management tools Top 10 Software Testing Tools Every QA Professional Should Know 9 KPIs commonly tracked closely in Manufacturing industry