<!--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=377554) </details> <!--IssueSummary end--> <!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "type::bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=type::bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary <!-- Summarize the bug encountered concisely. --> If a user with `Reporter` access attempts to open the Web IDE, we automatically prompt them to fork the project. This prompt will automatically attempt to fork the project to their personal namespace, but if the group has outside group forking disabled, the page is forwarded to a 404. ### Steps to reproduce 1. Create or use an existing test group. 2. Check "Prevent forking outside of the group" within the groups Settings >> General >> Permissions and group features area. 3. Add a secondary user as a Reporter to the group. 4. While signed in as that secondary user, attempt to open the web IDE on a project and accept the fork prompt. ### What is the current *bug* behavior? <!-- Describe what actually happens. --> Fork prompt forwards to a 404 page when outside group forking is disabled. ### What is the expected *correct* behavior? Ideally we should forward to the normal forking page for that project, as reporters ARE able to fork projects within the group. ### Output of checks This bug happens on GitLab.com.