Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Permission schemes allow you to limit or extend users' access of users to information and actions, on . On External Share for Jira, you can benefit from permission schemes on the project and issue levels-level permission schemes.
You can find out more about permission schemes here.

...

On the permissions page, you can enable permission schemes,

...

Jira permission scheme setupset up

  1. Next to your profile, select the settings (⚙️)

  2. Select the “Issues” option

  3. Scroll down the side panel on the left side of the page

  4. Select the “Permission schemes” option

  5. Find the scheme that includes your project

  6. On the “Actions” column, click on the “Permissions” button

  7. Scroll down to the “Issue Permissions” section

  8. Find the “External Share” permissions

...

  • Project Role

    • Administrator

    • Atlassian-addons-project-access - This will grant access to add-ons - More information.

    • Service Desk Customers

    • Service Desk Team

  • Application Access

    • Jira Software

    • Jira Core - This will grant access to Jira only, excluding agile

  • Group

  • Public (Heads up: Anyone on the internet can perform these tasks if you grant permission to the 'Public' group.)

  • Any logged-in user

  • Service Project Customer - Portal Access

  • Reporter

  • Single user

  • Project lead

  • Current assignee

...

Permission schemes help you add permission to different operations for users, ; if you do not need to customize permissions, default permissions will be respected.

...

When Jira Permission Scheme is disabled
When groups and project roles are empty, all users will have access to all operations, including project-level access.

When Jira Permission Scheme is enabled
By default, no users has have access to External Share operations. Project The project admin must first add permissions.

...

Permission schemes in the context of External Share targets target the following user types and three layers of access.

Some permissions are required while ever-present, others may be customized, and some are impossibleunreachable.

Level/ user

Global admin

Project Admin

Non-admin user

Global settings

required

ever-present

impossible

unreachable

impossiblerequired

unreachable

Project setting

required

ever-present

ever-present

customizable

Issue

customizable

customizable

customizable

What permissions can be customized?

Permission

Description

External Share - View shares on issue

Ability to view External Share addon on issue page

Non-global admin and user can view self-created shares from “Apps dropdown menu”.

External Share - Create new share

Ability to create new External Share

If view permission is not given, user can still create shares with this permission but will not be able to preview it after configuration is finalized.

Admins will not be able to create issue shares but can still create filter, board and roadmap shares from project settings.

External Share - Edit share

Ability to edit existing External Share

External Share - Delete share

Ability to delete existing External Share

External Share - Send share by email

Ability to send information about existing External Share by email.

This will allow the user to send a share via External Share email/custom email.
This does NOT limit viewing or copying share link.

External Share - View all shares from project

Will grant user permission to view all shares from the project, if create permission is given, user will be able to create filter, board and roadmap shares.