Editor access in only one project

[Caue Fajoli]

People external to the organization (domain.com.br) need to have access to read and edit certain projects, but cannot have visibility of the other projects in the account.
How do I do?

[Mikael Sandberg · Accepted solution]

Hi @Caue Fajoli,

Welcome to Atlassian Community!

You do this by creating a new permission scheme that you apply to all your existing project and then I would recommend that you allow users to browse the project and edit issues based on project role instead of the group. You can then control who have access to a project on each project instead of having to add and remove users from groups. You can learn more about permission schemes here.

[Ronald Hipol]

Hi @Caue Fajoli 

I agree with @Mikael Sandberg 's solution. You can create a Permission scheme that will not grant Browse and Edit permissions to external users. If the external users' default group is Jira users, you can create a custom group for the members of your organization (in my sample, Project Agile) then add it to the new Permission scheme. Do not grant access to the Jira users group. You can do this the other way too, external users' group name: External, your organization: Jira users.

You can now associate the projects that need to be private to the new permission scheme. It may take an hour or two to do it since you have a hundred projects.

[Ronald Hipol]

Hi @Caue Fajoli 

You can configure the issue security scheme to "hide" the other projects from a particular user or group. Create the scheme first then associate all the projects that are off limits.

[Mikael Sandberg]

Note that issue security does not hide projects, but you can use that together with permission schemes to hide issues within a project.

[Caue Fajoli]

From what I've seen, this setting limits views to specific issues, but I want access to be limited to the project only.
The corporate account has hundreds of projects and it is impossible to hide one by one.