I have a group of Freelancers. I want them to have access only to certain projects and in those projects I want them to be able to mention other people. However, I don't want them to see all the other projects I have in Jira.
Is this possible? Thank you.
Hi @Angelica Agud,
Yes this is possible. There is no such thing as a browse all project permission though. Browse project is a permission specific to each project, and therein lies the foundation for the solution you are looking for.
If you are using company-managed projects, the default permission scheme used for creating projects out of the box unfortunately grants browse project access to all logged in users, as you can see here:
To mitigate that, you should remove that permission from the permission scheme of all projects where you want to apply more control over who can access them. Assign roles to the permission and then, associate users or groups with those roles on a per project basis.
For more details, see this support article.
Be careful though when you start modifying this. Removing the application access from the permission scheme may cause many of your current users to lose the access they currently have. So plan ahead and look at who should access each project and preferably assign users to the correct roles first in your project to ensure continuity.
Hope this helps!
Thanks a lot for your help. I managed to do it, however, not by adding the newly-created group to the permission scheme attached to the project (under Browse Projects). That didn't fully work... The group members would have access to that project only, however, they weren't able to mention other people. The only way I managed to enable mentioning was by adding the group to the global permissions 'Browse users and groups'.
Luckily in our Jira, we don't have the 'Application access (Any logged in user)' as default, so the newly-created group doesn't have access to any projects, unless people in the group are added manually to the project by the manager :)
Thanks for your help!
@Angelica Agud it is!
I couldn't say it any better than in this article here. https://confluence.atlassian.com/cloudkb/how-to-restrict-project-access-for-teams-in-jira-cloud-953142266.html
It does require getting a good understanding of permission schemes, groups and project roles but once you have followed this - it should (ideally) make it a lot clearer.
We are excited to announce the open beta program for self-hosted runners. Bitbucket Pipelines Runners is available to everyone. Please try it and let us know your feedback. If you have any issue...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events