<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=332943) </details> <!--IssueSummary end--> Let's improve on the UX for the restricted visibility settings: | header | header | | ------ | ------ | |  |  | 1. The double negative of restricted visibility settings is confusing. Let's re-think how to make this less confusing. 2. Explore the idea of forcing a single selection. ## More Info The following discussion from !62340 should be addressed: - [ ] @mnichols1 started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/62340#note_593491792): (+2 comments) > Side note, I don't love the double negative of restricted visibility settings, with check meaning it is off and I think we should probably force at least a single selection, but those are follow issues for sure.