Correct me if I’m wrong but, if I set “Default repository permission” to None then nobody in the organization will not be able to see the contents of repository, unless specifically granted read (or higher) privileges.
This kind of behaviour is problematic for my use-case (assuming that my understanding is correct).
I’m admin of university laboratory organization and our members are divided into two teams: students and phd+, where phd+ team consists of “higher ranking” members of laboratory which need to have read access for all repositories, while students team needs to only have read access to repositories created by the members of students team.
The only way I see of enforcing this structure is by setting “Default repository permission” to None and then manually adding teams to each repository. Using this kind of workflow means that every time a student creates a new repository, that student needs to set read access to the students and phd+ teams. As a consequences, phd+ team needs to be made visible, which I would much rather like it to be secret.
I would much rather be able to use “Default repository permission” of read and then for some repositories place role to None for students team. If this would be possible then I would be also able to make a phd+ team secret.