Mute Notification User Autosubscribe
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.
auto_awesome What this module does
AI-generated from the code · Odoo 19.0Lets administrators define, per model, which users or groups should not receive chatter notifications when they are automatically subscribed through the user_id field. Muted users are subscribed with a special 'Mute' subtype instead of the normal notification subtypes.
This module adds a new configuration screen called 'User Autosubscribe Mute', found under the Technical menu of the Discuss/Mail app and restricted to system administrators. On this screen you create rules that link a model (only models that actually have a user_id field pointing to users are selectable) with a list of users and/or groups.
When Odoo automatically subscribes a user to a record because that record's user_id was set, the module checks whether the user is covered by a rule for that model. If so, the user is still subscribed but with a special 'Mute' message subtype, so no normal chatter notification is sent to them.
- Rules are unique per model: you cannot create two rules for the same model.
- Rules can be archived instead of deleted.
- A free-text notes field is available for internal comments.
- Regular users can read the rules; only system administrators can create, edit or delete them.
The module touches the mail.thread behaviour used by all chatter-enabled models and extends res.users with the mute check. It also creates a new 'Mute' mail message subtype.
Depends on
Menus it adds
Models and fields (1)
- user.autosubscribe.mute · new modelname, notes, active, model_id, user_ids (Users), group_ids (Groups)
Text generated by AI (DeepSeek) from reading the Odoo 19.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 2 confirmed, 7 with no information of 9 versions.
Sources · Odoo 19.0
Confirmed on 2026-11-03 in branch 19.0 of OCA/social.
terminal Installation and usage
OCA documentation · Odoo 19.0Configuration
Source · Odoo 19.0To 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
Source · Odoo 19.0In 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.
No verified information in OCA: Installation.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.