Table of Contents

    Permissions and Roles

    Rumman Ansari June 03, 2026 21 views Subject Details

    Jira for Scrum Masters: Permissions and Roles

    Permissions and Roles in Jira control who can view, create, edit, assign, transition, and administer issues and projects. Proper permission management ensures security, governance, and smooth collaboration within Agile teams.

    Key Idea:
    Roles define who users are in a project, while Permissions define what users can do.

    What are Jira Roles?

    Project Roles are groups of responsibilities assigned to users within a Jira project. Roles simplify permission management because permissions can be assigned to roles instead of individual users.

    Common Jira Project Roles

    Role Responsibility
    Administrator Manages project settings and permissions
    Project Lead Oversees project execution
    Developer Works on Stories, Tasks, and Bugs
    Tester / QA Validates completed work
    Product Owner Manages backlog and priorities
    Scrum Master Facilitates Agile processes
    Stakeholder Views project progress and reports

    What are Jira Permissions?

    Permissions determine the actions users can perform within a Jira project. Permissions are managed through Permission Schemes.

    Common Jira Permissions

    Permission Purpose
    Browse Projects View project and issues
    Create Issues Create Stories, Tasks, Bugs, etc.
    Edit Issues Modify issue information
    Assign Issues Assign work to team members
    Transition Issues Move issues through workflow stages
    Delete Issues Remove issues from project
    Manage Sprints Create and manage Sprints
    Administer Project Manage project configuration

    How Roles and Permissions Work Together

    Example:

    Role: Developer
    Permissions:
    • Create Issues
    • Edit Issues
    • Assign Issues
    • Transition Workflow Statuses
    The Developer role receives permissions through the project's Permission Scheme.

    Permission Scheme Architecture

    Structure:

    Users
    ↓
    Project Roles
    ↓
    Permission Scheme
    ↓
    Allowed Actions

    Typical Permissions for Scrum Roles

    Role Typical Permissions
    Scrum Master Manage Sprints, View Reports, Edit Issues
    Product Owner Create/Edit Backlog Items, Prioritize Stories
    Developer Create, Edit, Assign, Transition Issues
    QA Engineer Update Bugs, Verify Issues, Transition Testing Status
    Stakeholder View Boards, Dashboards, Reports

    Managing Project Roles

    1. Open Project Settings
    2. Select People
    3. Add User
    4. Select Project Role
    5. Assign User to Role
    6. Save Changes

    Managing Permissions

    1. Navigate to Jira Administration
    2. Open Permission Schemes
    3. Select Project Permission Scheme
    4. Configure Permissions
    5. Assign Permissions to Roles or Groups
    6. Save Configuration

    Role of Scrum Master

    • Ensure team members have required access
    • Promote transparency while maintaining security
    • Coordinate with Jira Administrators
    • Support Sprint and backlog management permissions
    • Prevent permission-related blockers

    Security Best Practices

    • Follow the Principle of Least Privilege
    • Grant only necessary permissions
    • Use Roles instead of assigning permissions directly to users
    • Review permissions regularly
    • Remove inactive users promptly
    • Restrict administrative privileges

    Common Permission Challenges

    Challenge Impact
    Too Many Permissions Security risks and accidental changes
    Insufficient Permissions Work delays and blockers
    Role Confusion Unclear responsibilities
    Direct User Assignments Difficult maintenance and administration

    Real-World Example

    Scenario:

    A Product Owner needs to prioritize backlog items but should not modify project configurations.

    Solution:
    • Assign Product Owner Role
    • Grant Create/Edit Issue Permissions
    • Restrict Administrative Permissions
    This ensures appropriate access while maintaining project security.

    Best Practices

    • Define roles clearly
    • Use permission schemes consistently
    • Review access periodically
    • Document role responsibilities
    • Keep permission structures simple
    • Align permissions with organizational policies

    Common Mistakes

    • Giving administrator access to everyone
    • Not reviewing permissions regularly
    • Assigning permissions directly to users
    • Creating unnecessary custom roles
    • Ignoring security governance

    Example Interview Answer

    Answer:
    In Jira, Roles define who users are within a project, while Permissions define what actions they can perform. Permissions are managed through Permission Schemes and are typically assigned to project roles such as Scrum Master, Product Owner, Developer, and Stakeholder. Proper permission management ensures security, governance, and effective collaboration.

    Conclusion

    Permissions and Roles are fundamental to Jira administration. They ensure that users have appropriate access, protect project data, and support efficient Agile collaboration while maintaining security and governance standards.

    Scrum Master Complete Bootcamp: From Beginner to Professional