Entity Activity Group

Entity Activity Group is an optional submodule in the Entity Activity 2.x beta. It lets people explicitly follow a Group and receive activity when a node is added to that Group. This is the first iteration: please try it and report problems or missing use cases in the Group integration issue.

Requirements

• Drupal core 10.3 or later in the 10.x line, or Drupal 11.
• Entity Activity 2.x and Group 3.3.5 or a later 3.3.x patch release. Group 2.x and 4.x are not supported.
• Group's Group Node (gnode) submodule.

Set up

1. Install the compatible Group and Entity Activity releases. Enable Group, Group Node (gnode), Entity Activity, and Entity Activity Group (entity_activity_group).
2. At /admin/config/content/entity-activity, enable the Group entity type for subscriptions.
3. Place the Subscribe on display component or block on the Group display and grant the subscribe all entities permission to the intended roles. Users must also be able to view a Group to follow it.
4. Create an Entity Activity generator, enable the Group node activity plugin, choose the Group and node types to track, and select immediate or cron-based generation.
5. As an eligible user, choose Follow group. Add a node to that Group and check the follower's activity log. Run cron if the generator is queued.

What following does

Follow group and Unfollow group manage an explicit Entity Activity subscription. They do not join or leave the Group, change Group roles, or grant content access. When a node is added to a Group, including when an existing node is attached, the generator creates activity for followers who can view both the Group and node. The node is the log source; the Group is its subscription target.

Queued generation rechecks the relationship and access before saving. Stored Group logs, unread listings, Views, and mail delivery also recheck relevant access or relationship state. If a follower loses access or the relationship is removed, the corresponding stored Group log is no longer shown to them.

Current limits

• Group members are not subscribed automatically. Each user must follow the Group explicitly, or a site-specific integration must create subscriptions.
• This generator does not notify on ordinary node edits, relationship edits, detachments, deletions, comments, or later publication of a node that was attached while unpublished.
• Views filters inaccessible Group logs after querying, so access changes can leave short or empty paged results. Use an unpaged View when access-aware pagination matters.
• Queued processing is at least once; retrying the same relationship event can produce another log.

For implementation detail, see the submodule README. Please include your Drupal, Group, and Entity Activity versions, reproduction steps, and expected versus actual behavior when reporting feedback in the Group integration issue.