MR: Pending ## Description Spin off from: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/196578#note_2602276706 We need to potentially reconsider the strong condition that the user needs to be a developer on the agent project after submitting a create workspace mutation. This is relevant given that we have other domain-level checks on workspace creation and separate auth policies that control mapping access that prevent the user from being able to see agents they are not permitted to use in the first place. consult original design doc: https://gitlab.com/gitlab-org/workspaces/gitlab-workspaces-docs/-/blob/3af65b0683b6659376b58ec1a953925c1023dbe8/doc/tech-designs/2024-01-23-support-group-agent-authorization.md <!-- OPTIONAL: Is this a feature/enhancement? - Please describe the impact this feature/enhancement will have on the user experience and/or the product as a whole. - Provide a user story to illustrate the use case for this feature/enhancement. Include examples to help communicate the intended functionality. --> <!-- OPTIONAL: Is this a bug? Please uncomment and include the following: - **Current behavior:** - **Expected behavior:** - **Steps to reproduce:** - **Additional information:** please include VSCode version, browser dev tool logs, etc that might be helpful to debug the issue! --> ## Acceptance criteria TODO - [ ] [Describe what must be achieved to complete this issue.] - [ ] [If applicable, please provide design specifications for this feature/enhancement.] - [ ] [If applicable, please list any technical requirements (performance, security, database, etc.)] ## Implementation plan [Provide a high-level plan for implementation of this issue, including relevant technical and/or design details.] <!-- NOTE: Feel free to expand with more sections and headers as needed --> <!-- DO NOT TOUCH BELOW -->