Quick facts
- Price
- $249.00 USD
- Odoo versions
- 17, 18, 19
- Setup time
- 30 min
- License
- One-time perpetual
- Languages
- 11 languages
One-time Purchase
All in One Chatter Mode
A made-to-order Odoo module that lets users toggle the chatter's visibility, position, and layout on any form so wide screens stay usable and dense records stay focused. ECOSIRE scopes, builds, installs, and supports it for your exact form models and role structure.
$249.00USD
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Key Features
Per-user chatter preference persisted to a stored `models.Model` record keyed to `res.users`, surviving logout and browser change
Optional per-model overrides keyed to `ir.model` so layout choice on `stock.picking` never leaks to `crm.lead` or `sale.order`
OWL component that patches the form renderer's chatter container without forking the core form view
Configurable mode set: bottom-docked, right-side-docked, collapsed-to-tab, and fully hidden — chosen per deployment
Toggle control injected into the control panel or chatter header via a QWeb view extension, no per-view XML surgery required
Administrator-set organization default mode plus an allow-list of which models expose the toggle, exposed in Settings
Layout-only behavior — `mail.message`, `mail.followers`, activities, and tracked-field history are never touched
`ir.model.access.csv` plus a record rule restricting each user to reading and writing only their own preference row
Responsive breakpoint handling so the chosen mode adapts sensibly between wide desktop and narrow laptop widths
Version-correct build against Odoo 17.0, 18.0, or 19.0 chatter DOM and OWL hooks, handling Community vs Enterprise differences
Optional automated action to seed a default mode per role or team when a new user is created
Preferences readable and writable over XML-RPC/JSON-RPC for scripted provisioning across multiple databases
Graceful fallback to the native chatter layout on any model where the toggle is not enabled
Clean uninstall path that removes the preference model and restores stock chatter behavior with no orphaned data
About this Product
On wide monitors the chatter panel on every Odoo form eats a third of the horizontal space that power users would rather give to columns, notebook pages, and one2many lines — while on dense operational records (manufacturing orders, sales orders, project tasks) the same chatter is exactly where people log the audit trail. Odoo ships the chatter in a single fixed layout that the user cannot move or hide, and the position differs between Community and Enterprise builds. The result is a daily friction: data-entry teams want it gone, account managers want it front and center, and there is no per-user, per-model way to have both. This is where the native experience runs out of road — you can patch one view with an XML override, but that decision is global and permanent for every user who opens that model.
Why Choose All in One Chatter Mode
Per-user chatter preference persisted to a stored `models.Model` record keyed to `res.users`, surviving logout and browser change
Optional per-model overrides keyed to `ir.model` so layout choice on `stock.picking` never leaks to `crm.lead` or `sale.order`
OWL component that patches the form renderer's chatter container without forking the core form view
Configurable mode set: bottom-docked, right-side-docked, collapsed-to-tab, and fully hidden — chosen per deployment
Toggle control injected into the control panel or chatter header via a QWeb view extension, no per-view XML surgery required
Administrator-set organization default mode plus an allow-list of which models expose the toggle, exposed in Settings
We build a made-to-order module that adds a user-controllable chatter mode to Odoo form views. A lightweight OWL component injects a toggle into the form's control panel (or the chatter header) that switches the panel between states you define — for example bottom-docked, right-side-docked, collapsed-to-a-tab, or fully hidden — and remembers the choice. Preferences are stored per user and optionally per model via a small models.Model record keyed to res.users and ir.model, so a warehouse operator's collapsed layout on stock.picking never overrides a CRM lead's expanded layout for the sales team. Because the behavior is layout-only, no chatter data, mail.message, or mail.followers semantics change — messages, activities, log notes, and tracked-field history all continue to work exactly as before.
Technically the module is a clean addon with its own __manifest__.py depending on mail and web, an OWL/QWeb view extension that patches the form renderer's chatter container, and a stored-preference model guarded by ir.model.access.csv plus a record rule so each user can only read and write their own settings. Defaults are configurable through Settings so an administrator can set the organization-wide starting mode and choose which models expose the toggle, and the same defaults can be pushed via an automated action or read over the XML-RPC/JSON-RPC API for scripted provisioning. We handle the Community-vs-Enterprise layout differences for you and target whichever of Odoo 17.0, 18.0, or 19.0 you run — the chatter DOM and OWL hooks differ across those versions, so we build and test against your exact release rather than shipping one brittle template.
Delivery is build-to-order: after a short scoping call we confirm which models get the toggle, the exact modes you want, the default per role, and your Odoo version and edition, then produce a fixed quote. Typical delivery is 2 to 4 weeks from confirmed scope, and you receive the installable source, install and configuration on your staging environment, UAT sign-off, and a post-go-live support window. Pricing starts from $249 (indicative, single-company base scope); wider rollouts — many additional form models, per-team default profiles, multi-company deployments, or deeper Enterprise layout work — increase the quoted scope, and we give you a firm fixed price before any build begins.
What you get
- Installable module source code for your Odoo version (17.0, 18.0, or 19.0) and edition
- Installation and configuration on your staging environment, including Settings defaults and per-model enablement
- Technical documentation covering the manifest, preference model, access rules, and OWL view extension
- End-user guide plus a live training session for administrators and key users
- UAT on staging with a documented rollback plan before any production change
- Post-go-live support window for defect fixes and configuration adjustments
- Git repository handover with tagged release and commit history
- Compatibility notes for future minor upgrades within your Odoo major version
Who this is for
Odoo Administrator
Owns the production database and wants a supported, uninstallable module that respects access rules and record rules rather than a hand-hacked view override that breaks on the next upgrade.
Operations / Data-Entry Team Lead
Runs high-volume form work on records like pickings, manufacturing orders, and invoices, and needs the chatter collapsed or hidden to reclaim horizontal space and speed up keying.
Sales or Account Manager
Lives in the chatter for follow-ups, logged calls, and activity scheduling, and wants it docked and expanded by default on CRM and sales forms without forcing that choice on other teams.
Odoo Implementation Partner / IT Manager
Rolls out consistent UX defaults across multiple companies or databases and needs per-role defaults, XML-RPC provisioning, and a clean git handover for their own maintenance.
Installation overview
Download from ECOSIRE
Buy the license on ecosire.com and download the All in One Chatter Mode module ZIP from your account dashboard.
Upload to Odoo
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Install the module
Activate Developer Mode, open Apps, click Update Apps List, search for All in One Chatter Mode, and press Install.
Configure settings
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Verify & go live
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
How All in One Chatter Mode Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Chatter position/visibility control | Per-user, per-model toggle across defined modes | Whatever you build; scope depends on your team | Fixed set of modes, global assumptions | |
| Per-user persistence | Stored preference keyed to `res.users`, survives sessions | Only if you design and store it yourself | Often global or cookie-based, not per-model | |
| Version & edition fit | Built and tested for your 17/18/19 + Community/Enterprise | Depends on your in-house Odoo depth | One template, may break across versions | |
| Security model | `ir.model.access.csv` + record rule, own-rows only | Must be designed and reviewed by you | Varies; access rules not always scoped | |
| Data safety | Layout-only; never touches `mail.message`/followers | Risk depends on implementation care | Usually layout-only but unverified for your data | |
| Support & maintenance | Post-go-live window + git handover + upgrade notes | Your team owns all maintenance | Vendor forum/tickets, generic to all buyers | |
| Provisioning at scale | XML-RPC/JSON-RPC + automated-action role defaults | Build it if you need it | Rarely scriptable per role | |
| Total cost path | Fixed quote from $249 indicative after scoping | Unbounded dev + QA time | Low list price, no fit guarantee |
Frequently Asked Questions about All in One Chatter Mode
Is this an existing app I can download and install right now?
No. This is a build-to-order module. ECOSIRE scopes it to your exact form models, modes, role defaults, and Odoo version, then builds, tests, and installs it for you. You receive the full source code and git repository at handover.
How long does delivery take?
Typical delivery is 2 to 4 weeks from confirmed scope. After a short scoping call we agree the models, modes, and defaults, then give you a fixed quote and timeline. Wider rollouts with many models or multi-company setups can extend that window, which we state before you commit.
How does pricing and scoping work?
Pricing starts from $249 as an indicative single-company base scope. The final number is a fixed quote produced after the scoping call, based on how many form models get the toggle, how many modes you want, per-role defaults, your edition, and any multi-company or provisioning requirements. You approve the fixed price before any build begins.
What support and updates do I get?
Every build includes a post-go-live support window for defect fixes and configuration tweaks, plus compatibility notes for minor upgrades within your Odoo major version. Because you own the source and git repo, your own team or ours can maintain it. Moving to a new major version (for example 18.0 to 19.0) is a separate scoped engagement since the chatter DOM changes between versions.
Does it change or risk my chatter messages, activities, or followers?
No. The module only controls layout — visibility, position, and width of the chatter panel. It never modifies `mail.message`, `mail.followers`, activities, or tracked-field history, so your audit trail and notifications are untouched. It also uninstalls cleanly, restoring the native layout.
Will it work on both Odoo Community and Enterprise?
Yes. The native chatter layout differs between Community and Enterprise, and across 17.0, 18.0, and 19.0. We build and test against your specific edition and version so the toggle behaves correctly rather than shipping one brittle template that assumes a single layout.
Can preferences be applied per user and per team automatically?
Yes. Preferences are stored per user and optionally per model. We can add an automated action to seed a default mode per role or team when users are created, and the preference records are readable and writable over the XML-RPC/JSON-RPC API for scripted provisioning across databases.
Related Modules
Request a quote
All in One Chatter Mode
A made-to-order Odoo module that lets users toggle the chatter's visibility, position, and layout on any form so wide screens stay usable and dense records stay focused. ECOSIRE scopes, builds, installs, and supports it for your exact form models and role structure.
- Per-user chatter preference persisted to a stored `models.Model` record keyed to `res.users`, surviving logout and browser change
- Optional per-model overrides keyed to `ir.model` so layout choice on `stock.picking` never leaks to `crm.lead` or `sale.order`
- OWL component that patches the form renderer's chatter container without forking the core form view
- Configurable mode set: bottom-docked, right-side-docked, collapsed-to-tab, and fully hidden — chosen per deployment