Entity Activity

Entity Activity provides configurable, per-user activity logs and notifications when supported content entities are created, updated, or deleted. Users subscribe to entities or translations, and site builders control which events generate logs.

2.x beta: testers welcome

The 2.x line is a straightforward continuation of 1.x for Drupal 10.3+ and 11, not a rewrite. Known reported 2.x issues have been addressed in the current beta, but it is still an early beta and needs broader real-site testing before a stable release. Please try the latest 2.x beta and report regressions, setup problems, and missing use cases. The 8.x-1.x release-candidate line remains available for Drupal 9.4 and 10; Drupal 11 sites should use 2.x.

Features

• Subscriptions for supported content entity types and translations.
• Configurable generators for create, update, and delete operations, including referenced entities, tokens, language handling, and immediate or cron-based processing.
• Fieldable log and subscription entities with Views integration, blocks, display components, and theming support.
• Optional Entity Activity Mail for immediate or scheduled email reports.
• Optional Entity Activity Mass Subscribe for subscribing or unsubscribing users by role, user selection, or filtered list.
• Optional Entity Activity Group in 2.x: users explicitly follow a Group and receive activity when nodes are added. It supports Group 3.3.5 and later 3.3.x patch releases with Group Node (gnode); Group 2.x and 4.x are not supported. Following does not change Group membership or access. This first integration attempt welcomes feedback.

Requirements

• Entity Activity 2.x: Drupal core ^10.3 || ^11. The 8.x-1.x line declares ^9.4 || ^10.
• Token
• Drupal core Text, User, and Serialization modules

Quick start

1. Install and enable Entity Activity and its dependencies.
2. At /admin/config/content/entity-activity, enable the entity types on which users may subscribe.
3. Place the Subscribe on display component or subscription block, and grant the required subscription and log permissions.
4. Create a generator, configure the relevant log-generator plugin, operations, bundles, and message tokens, then enable it.
5. Subscribe a user, perform a configured entity operation, and confirm that the activity log appears. Run cron when the generator uses queued processing.

For detailed configuration, display, mail, mass-subscription, Group integration, extension, and troubleshooting guidance, see the Entity Activity documentation guide.

Similar modules

Message and Flag can be combined to build related workflows and support a broader range of use cases. Entity Activity is focused specifically on subscriptions and generated activity logs, which can make this use case quicker to configure.

Support and community

• Report bugs and request features in the Drupal.org issue queue. Search for an existing issue before creating a new one.
• For discussion, join Drupal Slack and visit the #entity_activity channel.

Supporting organizations

Initial development was sponsored by Gallimedia. Ongoing support and development is sponsored by TrueCMS.