Permission scheme for external users

[Adrian Bogacz]

Hi,

I have configured default permission scheme in our Jira Cloud instance with browse project permission for team members (defined in project role) and people that reporter issues. In this case people outside team members can only see issues which they created them. Based on reporter field.

How can I configure permission scheme, that above settings still work and new external users can't see name of all our Jira projects?

I tried set permission for user picker custom field, but test external user still see names of projects (this user can't see issues inside, but see name of projects is too much knowledge for external)

I attach a screenshot from configuration of permission scheme now, which work correctly only for internal users.

Best regards,

Adrian

[Trudy Claspill]

Hello @Adrian Bogacz 

You should not need to configure a new permission scheme. You need only make sure that the new external users are not added to the specified project roles nor the site-admins user group.

[Adrian Bogacz]

What you say is only partially true. Based on the "Browse Projects" permission assigned to the "Reporter", we give information about the existence of a project to every person in the organization and therefore also to the accounts of external partners. This question is about how to keep the current level of permissions for people in the company, but limit the visibility of projects to people outside the organization.

Best,

Adrian

[Trudy Claspill]

Based on my experience with Jira Cloud, using the Browse Permissions permission in a project determines who will be able to see that project and all the issues in the project. Restricting which issues can be seen within that project for specific users requires the use of Issue Security Schemes and Levels.

If a users is assigned to a group or project role or issue role that is granted that permission for a project, they should be able to see all issues in that project (unless Issue Security is implemented).

If a user is not assigned to a group or project role or issue role that is granted that permission, then they should not be able to see the issues contained in the project.

Are you trying to prevent the "external partners" only from seeing the content of the project, or that plus not seeing the project in the View All Projects list?

[Adrian Bogacz]

I am trying to prevent external partners from seeing the projects and their names at all. Even if they don't have any permissions to see submissions in those projects. Security levels look like a good target solution for me. Then for specific roles in the project by security level I will restrict myself from seeing the tickets for people with permissions to the project.

[Trudy Claspill]

Hello @Adrian Bogacz 

In this document I found the following statement:

I think the fact that you added Reporter to the Browse Projects permission is why the projects are visible to everybody including your external partners.

If you want to be able to hide the projects and allow Reporters to see the issues in the project then you would need to remove Reporters from the Browse Permission and instead use Issue Security Levels to enable Reporters to see their issues. You might also need to add the people who become Reporters of issues to a Role or User group that has been granted the Browse Project permission. I don't have an environment where I can fully test all that out.