Skip to main content
Skip table of contents

Permissions for Working With Issue History

Note: We’ve updated the app’s Permissions page. Detailed information about the new permissions is available on this page. To access the updated experience, please upgrade to version 10.15.0 or later.

Why do you need permissions? This option allows you to restrict/grant access to the app features for certain user groups.

You can set permissions for:

  1. Access to all app views.

  2. Access to Security Scanner View.

  3. Access to “Deleted Work Items” option.

  4. Access to the app's Permissions page.

How to configure permissions

To manage access:

  1. Open the app’s main page.

  2. Click More (⋮) in the top-right corner.

  3. Select Permissions.

Frame 624675.png

You’ll see a list of all app sections where permissions can be configured. You can change access for four different sections: Report, Security Scanner, Deleted Work Items, and Permissions.

Frame 13.png

In the Permissions section, you can manage who has access to the app's Permissions page. A user from a group with Permissions menu restrictions will not be able to access this page.

In the Report section, you allow/restrict permissions to see all app views (except Issue History Panel View and Permissions page). If users in a group do not have permission to access the app’s views, they will see a message indicating they cannot access the reports.

In the Security Scanner section, you can control which user groups can see Security Scanner View results and access sensitive data detection (PII & DLP findings).

The Deleted Work Item section allows you to control the activation and display of data for deleted work items. If users from a group do not have access to the "Deleted Work Items” option, they cannot activate the toggle and view deleted tasks.

Frame 624674.png

Note that administrative groups (org-admins) have all rights by default and therefore cannot be disabled.

How permissions work

Each section has its own access rules.

Access levels:

  • My organization - all users have access.

  • User group - only selected groups are restricted or have access.

When using User group, you can choose:

  • Allowed - only selected groups have access.

  • Restricted - all users have access except selected groups.

64aead81-1447-4df2-b2aa-f142bb304f9b.gif

How to set access

  • Click Edit next to the needed section.

Frame 16.png
  • Select My organization or User group.

Frame 11 (1).png
  • In case of selecting User group, choose Allowed or Restricted.

Frame 4 (1).png
  • Then, select one or more groups.

Frame 6.png
  • Click Save. Changes apply immediately.

Note: Users in restricted groups will not see the feature and will not be able to use it. Admins (org-admins) always have full access

Understanding Type and Level Columns

In the Permissions table, Type and Level work together to define access.

The Type column defines the access mode (Allowed or Restricted).

The Level column shows who this rule applies to.

Example 1: In the Report section, the Type: Allowed and Level: Management, Developers. That means only these groups have access; everyone else cannot see all app’s views (except Issue History Panel View and Permissions page).

Frame 17.png

Example 2: In the Report section, the Type: Restricted and Level: Marketing, Designers. That means that these groups do not have access to see all app’s views (except Issue History Panel View and Permissions page). Everyone else has access to all app’s views.

Frame 18.png

Example 3: In the Report section, the Type: Allowed and Level: My organization. That means all users in Jira can see all app’s views.

Frame 20 (1).png
Permissions Page in Versions Prior to 10.15.0

Why do you need permissions? This option allows you to restrict/grant access to the app features for certain user groups.

You can set permissions for:

  1. Access to the Main dashboard of reports.

  2. Access to Security Scanner View.

  3. Access to deleted work items

  4. Access to the management system itself for Jira user groups.

How to configure permissions

Open the app’s main page, click the More (⋮) menu in the top-right corner, and select Permissions (if you have administrator access) to manage access.

Frame 624675.png

On the left side, you will see a list of your Jira user groups that have access to certain sections of the app.

Frame 624666 (1).png

Note that administrative groups (org-admins) have all rights by default, so they cannot be disabled.

You can change access for four different sections: Report, Security Scanner, Deleted Work Items, and Permissions. By clicking on the checkbox near the column’s header, you grant or restrict permissions for all groups. Or you can do it separately for each user group.

Frame 624667 (3).png

After selecting the groups that should have access, click Save changes.

Report section

In the report section, you grant/restrict permissions to see the main work item history report.

Frame 624670 (4).png

If users in a group do not have permission to access the app’s main page, they will see a message indicating they do not have access to the reports.

Security Scanner section

This section lets you control which user groups can view Security Scanner results and access sensitive data detection (PII & DLP findings).

Frame 624671 (1).png

Deleted Work Items section

This section allows you to control the activation and display of data for deleted work items.

Frame 624672 (3).png

The "Deleted Work Items” option is available in the table header on the main page or in the menu.

Frame 624674.png

If users from a group do not have access to the "Deleted Work Items” option, they cannot activate the toggle and view deleted tasks on the main page.

Permissions section

Here you can manage who has access to the Access Control section at the Jira group level.

Frame 624673 (1).png

A user from a group with Permissions menu restrictions will not be able to access this section.

If you do not have access to a section, contact the administrator for help.

Haven't used this app yet? 👉 You’re welcome to try it now 🚀

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.