| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) • Sales (sale_management) |
| Lines of code | 130 |
| Technical Name |
se_all_in_one_disable_followers |
| License | OPL-1 |
| Website | https://sprinterp.com |
| Versions | 17.0 18.0 19.0 |
All in One Enterprise Follower Restriction & Notification Framework
Disable and restrict automatically adding partners, vendors, or customers as followers across Sales, Invoices, and Mail Composer actions.
Key Module Highlights
All in One Disable Followers
Configure Global Follower Restriction Settings
Navigate to the Odoo **Settings** menu and select **General Settings** from the left-hand navigation sidebar. Scroll down to discover the newly integrated administrative block titled **"Disable/Restrict to add followers"**. Here, you can granularly toggle individual checkboxes to disable automatic follower triggers by confirming sales, validating invoices/bills, or sending out documents directly via emails.
Key Logic: These flags inject dynamic runtime context parameters such as disable_follower_sale_ctx
and mail_create_nosubscribe=True, overriding the standard _message_auto_subscribe_followers
methods across targeted operations.
Validate Sales Process Without Customer Auto-Subscription
When the "Disable to add followers by Confirm Sale" option is enabled in settings, navigating to any Quotation and clicking the primary "Confirm" button will transition the document into a Sales Order. The system safely bypasses Odoo's default behavior, ensuring that the customer or related partners are not automatically appended to the document's Following registry list in the chatter layer.
Key Logic: Overriding the action_confirm() method injects localized
state conditions into the current environment execution branch, filtering the partner_ids
parameter array safely before committing backend database subscription logs.
Activate Sales Follower Restriction Flag
To activate the restriction mechanism specifically for your sales workflows, ensure you check the box titled "Disable to add followers by Confirm Sale" in the operational configuration panel. Don't forget to click the primary "Save" button at the top-left corner of the dashboard screen to commit these localized pipeline modifications successfully to the company schema database.
Key Logic: Enabling this config parameter updates the active res.company
record data registry line, which is evaluated dynamically at runtime whenever an operational
record confirmation execution stream is triggered.
Enforce Operational Follower Restrictions on Sales Order Confirmation
As validated across active records, triggering the workflow confirmation on a standard quotation successfully maintains a restricted subscriber list. Even upon full order execution, the document's Following registry isolates the chatter layer, keeping third-party entities completely decoupled from internal workflow discussion logs.
Key Logic: The underlying core architecture checks the
disable_follower_sale config boolean at the exact moment of order verification,
overriding native sub-methods to protect structural data privacy without compromising
pipeline transactions.
Activate Financial Invoice & Bill Follower Suppression
To extend your privacy controls to the accounting workflows, navigate back to the operational configuration panel and enable the checkbox titled "Disable to add followers by Validate Invoice/Bill". Once ticked, click the primary "Save" button at the top-left command header to store this validation override configuration safely within your company workspace.
Key Logic: Activating this setting maps directly to the disable_follower_invoice
fields, providing an enterprise-grade runtime interceptor that prevents automatic customer
or vendor subscriptions during ledger post operations.
Validate Invoices and Bills Without Automatic Partner Inclusions
With the invoice tracking override active, creating a customer invoice or vendor bill and executing the primary "Confirm" or "Post" validation will safely decouple the target partner from the document's subscriber grid. The chatter log isolates internal notes smoothly, ensuring third-party accounts are not automatically forced into the document's active Following list.
Key Logic: The custom module hooks directly into the account.move
operational logic via an inherited action_post() method wrapper, securely
passing runtime execution contexts (disable_follower_invoice_ctx=True) to
shield data ledger visibilities.
Extend Follower Suppression to Vendor Bills Purchases
The underlying framework handles all variations of accounting documents symmetrically. Upon validation of a standard Vendor Bill, the system invokes the exact same security layer to ensure that supplier or third-party vendor profiles are completely restricted from auto-populating into the active Following register layout of the document.
Key Logic: Since Odoo maps both invoices and bills onto the same unified account.move
database model structures, the custom inherited actions clean up subscriber logs
comprehensively across all purchase-side compliance flows.
Ensure Consistent Enterprise Data Isolation Across Sales Orders
The system consistently enforces follower restrictions across all sales pipelines. Upon transforming a standard quotation into an active Sales Order, the backend layer isolates the chatter stream flawlessly. Third-party partner profiles are completely skipped, keeping the document's active Following list clean and focused solely on designated internal stakeholders.
Key Logic: The custom model layer intercepts the core validation pipeline, filtering out default subscription arrays at the exact millisecond of state transition, which effectively blocks automated chatter expansion.
Activate Email Composer Follower Restriction Controls
To finalize your communication privacy setup, navigate to the unified block configurations and enable the third checkbox titled "Disable to add followers by Send by Email". Click the primary "Save" button at the top-left command header to store these restrictions. This comprehensively blocks Odoo's native mail routine from forcing email recipients into your document subscription grid.
Key Logic: Enabling this configuration updates the active disable_follower_email
corporate parameter, which is intercepted at runtime by the
mail.compose.message wizard and core message_subscribe methods to
prevent automatic subscriber loops.
Prevent Customer Auto-Subscription When Sending Documents via Email
When executing the "Send by Email" action workflow on any operational quotation, Odoo traditionally forces the message recipient directly into the thread subscription list. With this restriction framework active, the outbox dispatch process completes seamlessly while successfully maintaining an isolated Following registry list, protecting your communication streams from crowded external additions.
Key Logic: The custom module inherits the mail.compose.message wizard
logic and overrides the _action_send_mail() workflow by dynamically wrapping
runtime overrides (disable_follower_email_ctx=True) to cleanly block automated
partner subscription triggers.
Key Features & Capabilities
Empower your communication channels with automated subscription controls and native follower restriction engines in Odoo.
Sales Thread Protection
Intercepts and blocks automatic follower additions during quotation sending and final Sales Order confirmations, keeping sales pipelines focused.
Invoice Chatter Control
Suppresses the default Odoo mechanism that adds customers, partners, or internal teams as followers upon validating customer invoices or vendor bills.
Mail Composer Bypass
Overrides standard mail triggers to send professional outbox dispatches seamlessly without forcing recipients into the document's subscription sub-grid.
Centralized Administration
Adds native configuration toggles directly inside Odooâs General Settings panel, letting administrators easily manage restriction rules with a clean UI.
Multi-Company Isolation
Fully supports complex multi-tenant corporate infrastructures by separating all configuration flags safely within individual res.company parameters.
Safe Context Overrides
Implements advanced runtime context state updates (mail_create_nosubscribe) to securely block subscribers without breaking baseline data logging.
Need Any Help?
Installation, Configuration & Bug Fixing support from our experts.
© 2017 SprintERP Technologies. All Rights Reserved.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) • Sales (sale_management) |
| Lines of code | 130 |
| Technical Name |
se_all_in_one_disable_followers |
| License | OPL-1 |
| Website | https://sprinterp.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module