[POC] feat: implement content restriction based on new user groups

[BryanttV]

Description

This is a Proof of Concept (POC) for the following Architectural Decision Records (ADR's):

• docs: add arch decision record for the migration path for legacy user grouping mechanisms #4
• docs: add arch decision record for the replication-based migration of legacy user grouping mechanisms #5

This implementation adds support for the content restriction functionality currently available with Cohorts, Teams, and Enrollment Track Groups.

Related PRs

• [POC] feat: implement content restriction based on new user groups edx-platform#36953

Supporting information

User Groups Confluence Page

Testing instructions

1. Use the changes in the related PRs.
2. After creating your course, you'll need to turn on a course-level flag that enables user groups. Go to /admin/waffle_utils/waffleflagcourseoverridemodel. Add a new flag using your new course ID and this Waffle flag: user_groups.enable_user_groups
3. Create user groups and add users to each one.
4. As course staff from Studio > [Your Course] > Course Outline > + New unit.
5. Configure the unit to restrict access using User Groups. Select the user groups for which you want to display the unit.
6. As a student from LMS > [Your Course] > Course Outline.
7. If you belong to any of the user groups that have access to the content, you will be able to see it.
8. If you don't belong to any of the user groups that have access to the content, you will not be able to view it.

user-groups-content-restriction-poc.mp4

Deadline

None

[openedx-webhooks]

Thanks for the pull request, @BryanttV!

This repository is currently maintained by @openedx/committers-user-groups.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.