### Problem to solve We have gotten all customers off of Group Managed Accounts. Now that no one is using the feature, we need to remove it from the code base and remove it from the documentation. ### Documentation https://docs.gitlab.com/ee/user/group/saml_sso/group_managed_accounts.html (already removed) # Clean up approach for Group Managed Accounts ## Feature flags cleanup - [x] `convert_user_to_group_managed_accounts` - [x] `remove_non_gma_memberships` - [ ] `group_managed_accounts` ## Group Signup is no longer needed - [x] We can get rid of `Group sign up feature` which was particularly designed for `Group Managed Accounts` We can refer to following commit to figure out what changes need to be made : - [Introduce new sign up page for group SSO commit](https://gitlab.com/gitlab-org/gitlab/-/commit/aa688b2adb87ab58f5b1365ffda321594a80f2fd) ## Clean references to these methods in backend code. - [ ] `User#group_managed_account?` - [ ] `SamlProvider#enforced_group_managed_accounts` - [ ] `ee/lib/gitlab/auth/group_saml/gma_membership_enforcer.rb` can be removed entirely - [ ] `ee/app/services/group_saml/group_managed_accounts` can be removed entirely - [x] `ee/app/services/group_saml/group_managed_accounts/transfer_membership_service.rb` can be removed entirely ## UI Level changes - [x] Sign up form changes for user to be added to GMA needs to be removed - [x] `ee/app/views/groups/saml_providers/_form.html.haml` page will change to remove options for `enforced_group_managed_accounts` ## Database change - [ ] Remove column `managing_group_id` from `users` table. - [ ] Remove column `enforced_group_managed_accounts` from `saml_providers` table. ## Order in which changes should be made - [x] View level cleanups - [x] Controller cleanups - [ ] Entity/model cleanups - [ ] Remove Feature flags - [ ] Database level cleanups ### Availability & Testing <!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier. What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance. * Unit test changes * Integration test changes * End-to-end test change See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning --> Ensure the `package-and-qa` job is run and all tests are fine.