Hey @Kate Alexandrov,
for this to happen you must make sure, that all other projects are not accessible for these users, let's call them jira-externals. The others need to be able to access all projects, let's call them jira-internal. In order to remain as flexible as possible without getting entangled with strange permission schemes, it is recommended to grant access to your projects using roles instead of groups.
Therefore, in any group that you want to hide, make sure that the Browse Projects permission is only given to users who are in a certain role of your project (for example the project role users). Then you can use this role to determine, who has access.
You can also give this permission to multiple roles (for example admins, developers and users), this way you don't have to add a person into three roles to give them admin, development and user permissions. But this is a bit more advanced, so don't worry too much about it.
Okay, so to put my explanation in a correct order, here are the steps you can take:
That's it, now you should be all set up. I hope this was what you are looking for.
Andrej from greenique.
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