How to restrict project access to different isolated user groups

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

この記事はアトラシアンのサーバー製品にのみ適用されます。クラウドとサーバー製品の違いについてはこちらをご確認ください。

目的

This how-to will explain the steps needed to separate projectaccess,while granting read-only access to particular external user groups working on the project.

The example is written incontextof granting access to different Client groups.

Solution
Created the users in JIRA. We'll assume that a JIRA Administrator has already: 

  1. Populated these users into client-specific groups (i.e. all users from 'Company A' are grouped into the 'Client A' group) 
  2. Granted these groups JIRA access by:

    1. adding the groups to JIRA Users global permission for JIRA 6.4 and below

    2. adding the groups to a JIRA application at  > Applications > Application access for JIRA 7.0 and above
    3. granting the groups access to your instance at  > User management > Application access and clicking the View configuration button for JIRA Cloud users.
  3. Removed Internal Project access to client-specific users by removing the users from the default JIRA Users global permission. (i.e. removing them from the jira-users group)

ProTip: a group external-users can be created to group all Client users so adding external-users to JIRA Users global permission will grant them access to JIRA and enable more configuration benefits.

User Groups:

  • Clients: External users that can't see private Project or other Clients information (groups: ClientAClientB, etc)
  • External Users: Group of clients that can't see private projects (external-users group)
  • Internal Users: company members that have access to private company content and some or all Client projects (jira-users group)

You will then be able to set up these 4 roles:

  1. Internaluser that doesn't see clients projects (group:jira-users)
  2. Internaluser that works on Clients A and B only (groups:jira-users, ClientA, ClientB)
  3. Internaluser that Administers every Client project (groups:jira-users, Administrator)
  4. Externaluser that belongs to ClientA (groups: external-users, ClientA)

Access and Privacy configuration notes:

  • Set JIRA Users Global Permission to jira-users and external-users only to control groups that have access.
  • Add External User to external-users and a ClientX groups only to restrict private content.

Create a project role for Client groups.

Creating a project role that maps to your client groups will allow you to reuse your permission scheme across projects where the Client group will differ project to project. Project Roles makes it easier to manage your users rather than using groups all the time. Since group membership is global, whereas project role membership is project-specific, project admins will effectively be able to change the members of project role, even without the global JIRA Administrator permission. 

  1. Choose the cog icon  at top right of the screen, then choose System, then select Project roles to open the 'Project Role Browser' page.

    tip/resting Created with Sketch.

    Keyboard shortcut'g' + 'g' + start typing 'roles'

  2. Create a project role called 'Client', which will represent read-only client groups in a project.

Create a new permission scheme. 

  1. Choose the cog icon  at top right of the screen, then choose Issues. Select Permission Schemes to open the 'Permission Schemes' page. 
  2. Since this will only require one change to the default scheme, we can simply copy the default permission scheme. Select Copy in the row of "Default Permission Scheme."

  3. Rename the newly created (copied) permission scheme by selecting Edit in "Copy of Default Permission Scheme" row. Something identifiable such as 'Client Facing Permission Scheme' will do. 

    From the newly created scheme, remove all Application access (Any logged in user) entries and replace it with a Project role, for example Project role (Users), or a group

    to "hide" all remaining projects, the Application access (Any logged in user) entry must also be removed from the Browse Projects permissions, in all used permission schemes

Configure read-only permissions in the scheme. 

  1. On the Permissions Scheme page, select Permissions in the 'Client Facing Permission Scheme' row.  
  2. Select Add (Cloud Users click Edit ) in the Browse Projects permission row, click Project Role and select the 'Client' project role from the dropdown. Click Add/Grant to apply. 
  3. Add additional internal groups to the Browse Projects permission to ensure that internal users can also view the project. 
    1. By default, all JIRA users can access ('Browse') the project. Remove the 'jira-users' group from the 'Browse Projects' permission, leaving only your internal groups and the Client role. 

Add the client group to the project role. 

  1. Choose the cog icon  at top right of the screen, then choose Projects.
  2. Select the appropriate project from the Project List. 
  3. In the Roles section, select View Project Roles.  (Cloud Users select People)
  4. In the Clients row, select Add Group by hovering over the Groups column.  (Cloud Users click Add people)
  5. Add the Client Group(s) who will be accessing the project. 

Apply your permission scheme to an individual project. 

  1. Go to the Permissions section of the project Administration screen.
  2. Click the Actions dropdown in the upper-right hand corner. Select Use a Different Scheme.
  3. Select the 'Client Facing Permission Scheme'. Click Associate.

Related articles and guides:

Share JIRA with external partners
Configuring Issue-level Security to manually restrict issues individually 


説明

This how-to will explain the steps needed to separate project access while granting read-only access to particular external user groups working on the project. The example is written in context of granting access to different Client groups.

製品Jira
最終更新日 2018 年 11 月 19 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.