<!--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=214615) </details> <!--IssueSummary end--> Currently, when a parent of a fork lowers its repository access level, the forks won't follow it. In https://gitlab.com/gitlab-org/gitlab/-/issues/36662, we are going to copy the repository access level (and related ones) of parent when forking. But the following scenario will still be possible: 1. Parent has repository access level set to `Everyone With Access` 1. A fork of that project is created 1. Parent has its repository access level down to `Only Project Members` ## Proposal 1. Unlink forks when the parent access levels become more restrictive 1. Show a modal to indicate that this is going to happen when the access level becomes restrictive This is just like what we have for project visibility level.