Creating a new group restores previous configurations on the units (teams - content groups)

Expected Behavior

The unit configuration is maintained independently of the Groups created.

Actual Behavior

The unit configuration is restored when I create a new Group.

Steps to Reproduce

1. Create a Waffle Flag for your course in {lms_domain}/admin/waffle_utils/waffleflagcourseoverridemodel/

   • Waffle Flag: teams.content_groups_for_teams
   • Course id: [Your Course ID]
   • Enabled: ✅

2. Enables Teams in the platform using the teams.enable_teams_app flag.

3. Enable teams for your course in Studio > [Your Course] > Content > Pages & Resources > Teams > Teams toggle

4. In the same modal of Configure teams, create a few Groups.

5. Then, go to the LMS > [Your Course] > Teams and create a few Teams within those Groups (topics/team-sets)

6. In Studio, create a new Unit, and configure it to Restrict access to some Team.

7. As a student, join the Team previously configured. You'll be able to see the content.

8. Now, as staff create a new Group, similar to step 4.

9. See again the Unit configured; the configuration is missing.

10. As a student, you'll not be able to see the unit, even if you belong to the initially configured Team. Only the Staff can see the Unit.

https://github.com/user-attachments/assets/04410567-4b24-4e07-b90e-c80919897360

Additional Information

• Implementation PR: https://github.com/openedx/edx-platform/pull/33788

Notes

• The bug also occurs when using the Legacy Interface.
• This issue was originally reported in edx-platform, however, the bug comes from the MFE.

Start in the frontend-app-authoring repository by reproducing the Studio workflow described in the issue, then review the implementation PR linked in the report for the affected teams and unit-access configuration flow. Done means creating a new Group no longer removes an existing Unit's Team restriction, including when the Legacy Interface is used.