Skip to main content

Do not send notifications to users autosubcribed through user_id field

Project description

Beta License: AGPL-3 OCA/social Translate me on Weblate Try me on Runboat

This module allows to select users and/or groups whose members do not have to be sent notifications through the chatter. The models in which these rules have to be applied can also be selected.

Table of contents

Configuration

To configure this module you need to:

  • Go to Settings > Technical > Auto Subscribe Mute

  • Create a new instance or edit an exiting one. The following fields are available:

    • Name. The name of the rule.

    • Model. Model in which the rule is applied. Only models with a user_id field can be selected.

    • Users. List of users which the rule will be applied to. The users in this field will be autosubscribed to the document when they are set in the user_id field but only with the “Muted” subtype, which notifies nothing. Note that this rule will not be applied when the user in the list set itself in the user_id field, as the subscription in this case depends on the creation of the document, not the autosubscription.

    • Groups. List of groups which the rule will be applied to. The users that belong to the groups in this field will be autosubscribed to the document when they are set in the user_id field but only with the “Muted” subtype, which notifies nothing. Note that this rule will not be applied when a user in any of the groups in the list set itself in the user_id field, as the subscription in this case depends on the creation of the document, not the autosubscription.

    • Notes. Text field.

Usage

In case a user that has been automatically applied the “Mute” message subtype in a subscription through one of the rules provided in this module needs to be sent notifications in a specific document, just edit the subscription and select the subtypes for which the user has to be sent notifications.

Known issues / Roadmap

  • If a and “Auto Subscribe Mute” rule is modified, created or deleted, changes will not affect existing documents, so their users subtypes will keep the current configuration.

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

  • Sygel

Contributors

Maintainers

This module is maintained by the OCA.

Odoo Community Association

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

This module is part of the OCA/social project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

File details

Details for the file odoo_addon_mute_notification_user_autosubscribe-17.0.1.0.0.2-py3-none-any.whl.

File metadata

File hashes

Hashes for odoo_addon_mute_notification_user_autosubscribe-17.0.1.0.0.2-py3-none-any.whl
Algorithm Hash digest
SHA256 a8a6d031d20ec6ab9f8b4c68ff21d0359fe77e863b8fa24ee6fb6567f5eced53
MD5 863b225a257f48e12621fd33f773e6f0
BLAKE2b-256 e3e4376001470290e2abee4c28c2fb75691f31518173f1848aef1ae58c7b6a99

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page