Member Base Permissions #3
jrpearson-nhs
started this conversation in
General
Replies: 1 comment
-
Given no objections I've:
This means that current access hasn't changed but there is now an option to create a repo in the organisation that only a sub team and admins can see. This also means that if you want everyone to see your repo you will need to add the everyone team to your repo permissions in the future. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Dear all,
Considering downgrading the base member privileges from Read to none.
Currently having read permissions means that every repo made in the NHS England organisation can be read by all members. I've had multiple requests for teams to create repos which can't be viewed by all but only those explicitly specified. To do this we would turn off this base permission and you would only be able to see your repos and public ones. We would then use the "Everyone" team. All members are already assigned to an everyone team. This team could be added with read permissions to any repo enabling controlled organisation wide sharing of the work.
Please let me know thoughts on this.
Beta Was this translation helpful? Give feedback.
All reactions