Configure Issue Security in Jira
Use work-item security levels to restrict sensitive records within a broader space. Board filters and hidden columns are not confidentiality controls.
Step-by-step guide
Check access and scope
A Jira administrator must configure applicable security schemes and authorized level membership. Availability and configuration differ by plan and space type.
Define sensitive categories
Identify sensitive issue categories and required audiences.
Review security levels
Review or create the appropriate security scheme and levels.
- Worked example: A customer incident may be restricted to a small response group while ordinary release tasks remain visible. Verify linked attachments and external documents independently.
Associate the scheme
Associate the scheme with the intended company-managed space.
Protect a sample issue
Apply a level to an anonymized test issue.
Test both audiences
Test access as an included and excluded user before migrating real data.
Verify the result
Intended users can open the test issue and excluded users cannot find or browse its content.
Common mistakes
Check the handoff edge case
A restricted issue can still link to an unrestricted external document. Review that destination before adding sensitive content.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.