Project A team is able to access project B which belongs to another team.

[Rede Paulo de Tarso]

I have two projects in jira, project A and project B, for a single admin. I created two separate teams for each project. When the user gets the link to work on project A, he gets to see project B as well. I would like the project A team not to have access to project B and the project B team not to have access to project A. Is it possible to hide? What would be the option? It is important to inform that I am using the free version.

[Ravina · Accepted solution]

Hi @Rede Paulo de Tarso Yes it's possible with free version as well.

If I understand your requirement clearly you want to keep the both projects access separate so that users not able to view issues from other projects apart from the one they are working.

So, you can create a new permission scheme which will Role based (In browse project permission add only roles like Administrator, Developers, Users, etc) and associate this permission scheme to both the projects.

Then in Project A add the users or groups who need to access to that project on that specific role i.e Users role and do the same for Project B so that both projects will have different users in those Roles and able to access the projects and when they try to access the other project they will not as they are in that Role in other project.

Let me know if this works for you.

Thanks

Ravina

[Trudy Claspill]

Unfortunately, if @Rede Paulo de Tarso is truly using a Free version of the product as the post tags indicate, then it is not possible to add users to project roles and thereby utilize a Permission Scheme that grants access based on Project Roles.

It also is not possible to customize the Permissions Scheme.

Refer to https://support.atlassian.com/jira-cloud-administration/docs/what-is-the-free-jira-cloud-plan/

[Rede Paulo de Tarso]

Thank you very much for the feedback. As people outside the institution will also access one of the projects, I decided to create a new free access. This way everything is separate and without risk of unnecessary interactions. Thanks a lot @Ravina and @Trudy Claspill