Skip to content

Add Group Community TA to audience for content_reported notifications in cohorted courses #489

@pavanhalesh

Description

@pavanhalesh

Add Group Community TA to audience for content_reported notifications in cohorted courses

Summary

The content_reported notification currently includes Discussion Admins, Discussion Moderators, and Community TAs in its audience. However, Group Community TAs are not included, even though they have moderation visibility within their assigned cohorts in cohorted courses.

This issue proposes adding Group Community TAs to the content_reported notification audience in a cohort-aware way.


Background / Problem

In courses that use cohorts and divided discussions, Group Community TAs are responsible for moderating content within specific cohorts. When content is reported in a cohort-specific context, Group Community TAs for that cohort should be notified so they can take timely action.

Today:

  • Discussion Admins, Discussion Moderators, and Community TAs receive content_reported notifications.
  • Group Community TAs do not receive these notifications, even when the reported content is in a cohort they are responsible for.

This creates a gap between moderation responsibilities and notification coverage.


Proposed Solution

Introduce a new audience filter in the Notifications app:

Filter class name

GroupTAinCohortFilter

Audience filter parameter (example)

{
  "cohort_for_group_tas": [<cohort_id>]
}

Expected behavior

  • The filter takes a list of cohort IDs.
  • It returns all Group Community TA user IDs assigned to those cohorts for the given course.
  • These user IDs should be appended to the existing audience for the content_reported notification.

Important Constraint: General Topic

If the reported content is in a General topic (visible to all learners),
Group Community TAs MUST NOT be included.

They should only receive notifications when the reported content belongs to a cohort they are assigned to.


Questions for the Community

  • Does this behavior make sense for most Open edX deployments?
  • Any privacy, operational, or performance concerns?
  • Should this be:
    • a global config toggle, or
    • a course-specific configuration?

Acceptance Criteria (Proposed)

  • A new filter GroupTAinCohortFilter exists.
  • Group Community TAs assigned to a cohort are notified for cohort-specific content_reported events.
  • Group Community TAs are not notified for General topic reports.
  • Documentation is updated.

Internal Reference

Internal edX/2U ticket: ACT-400 — Add Group Community TA to audience for content_reported notification for cohorted courses.

Opening this issue to gather community feedback and find contributors interested in implementing this improvement.

Tagging for visibility

Tagging contributors who may have additional insights on the proposed implementation:

@awais-ansari
@ayub02

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions