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 Toolkit
A made-to-order Odoo customization that turns the standard chatter into a configurable panel — fullscreen, docked-bottom, side, or hidden — per user and per model. ECOSIRE scopes, builds, installs, and supports it on your Odoo 17/18/19 database.
$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
Four chatter display modes — fullscreen overlay, docked-bottom drawer, right-side column, and fully hidden with a toggle button
OWL component patch applied via `patch()` over the core `Chatter` and `FormRenderer`, delivered as an assets-bundle extension rather than a fork of core `mail`
Per-user mode preference persisted on `res.users` so each person's choice survives reloads and new sessions
Configurable default mode per model, set during scoping (e.g. hidden on data-entry forms, fullscreen on ticket forms)
Works on any model that already inherits `mail.thread` — no per-model view rewrite required to enable the toggle
Fullscreen mode renders the message/log thread in a viewport overlay for reviewing long email conversations
Bottom-dock drawer reclaims horizontal width on wide accounting and manufacturing forms while keeping the thread one click away
Optional keyboard shortcut bound to the mode toggle, configurable per your team's preference
Group-gated mode switching via `ir.model.access.csv` and record rules where only certain user groups may change layout
Clean dependency footprint — depends only on base `mail` and `web`, so it installs on both Community and Enterprise
Version-matched build for Odoo 17.0, 18.0, or 19.0, tested against the OWL component signatures of your target release
Non-destructive install — activity scheduling, followers, and message logging behavior of the native chatter are untouched
Tested on a staging clone against your real (including studio-inherited) form views before production go-live
`__manifest__.py` pinned to your Odoo series with an explicit version string for clean upgrade tracking
About this Product
On record-heavy forms — sales orders, invoices, manufacturing orders, project tasks — the standard Odoo chatter is pinned to the right and can eat roughly a third of your horizontal space. On wide, field-dense layouts that fixed placement squeezes the inputs your team actually works in, and there is no supported setting to move it, collapse it, or expand it to read a long email thread. Odoo core ships mail.thread and mail.activity.mixin behind a single hardcoded layout; the moment a team asks to dock the chatter at the bottom, pop it fullscreen to review a long conversation, or hide it entirely on a data-entry screen, you have run out of road with native configuration. There is no toggle for it, and each Odoo major version reshuffles the underlying OWL components, so a quick browser CSS hack breaks on the next upgrade.
Why Choose All In One Chatter Toolkit
Four chatter display modes — fullscreen overlay, docked-bottom drawer, right-side column, and fully hidden with a toggle button
OWL component patch applied via `patch()` over the core `Chatter` and `FormRenderer`, delivered as an assets-bundle extension rather than a fork of core `mail`
Per-user mode preference persisted on `res.users` so each person's choice survives reloads and new sessions
Configurable default mode per model, set during scoping (e.g. hidden on data-entry forms, fullscreen on ticket forms)
Works on any model that already inherits `mail.thread` — no per-model view rewrite required to enable the toggle
Fullscreen mode renders the message/log thread in a viewport overlay for reviewing long email conversations
This is where we build the All In One Chatter Toolkit for you. It is a made-to-order module that wraps the existing chatter with a display-mode controller: users switch between fullscreen (an overlay that gives the thread the whole viewport), bottom (a docked drawer beneath the form), side (the familiar right column), and hidden (chatter collapsed to a toggle button so the form reclaims full width). We implement it as an OWL component patch layered over the core Chatter and FormRenderer via the assets bundle and patch() — never a fork of core mail — plus a lightweight res.users preference so each person's chosen mode persists across sessions and reloads. Because the toggle lives in the form's control area, it works on any model that already inherits mail.thread, without per-model view surgery.
During scoping we tailor the behavior to how your teams work: default mode per model (for example, hidden on POS-adjacent entry forms and fullscreen on helpdesk tickets), which user groups may change the mode, whether the preference is global or remembered per model, and any keyboard shortcut you want bound to the toggle. If you run studio-customized or heavily-inherited forms, we test the patch against your actual XML views on a staging copy so the drawer and overlay respect your field layout. Access to who can switch modes is governed the standard Odoo way — ir.model.access.csv plus record rules where a group restriction is needed — and the module is delivered clean for either Community or Enterprise, since it only depends on the base mail and web modules present in both.
Delivery is build-to-order: after a short scoping call we confirm the exact modes, defaults, and target models in writing, then build against your Odoo version. Typical delivery is 2–4 weeks from confirmed scope, depending on how many custom forms need testing and your staging/UAT availability. You receive installable source, install and configuration on your environment, and a support window after go-live. Pricing starts from $249 (indicative, single-company base scope); additional target models, per-group mode permissions, deep testing against studio-customized forms, and multi-company rollout increase the quoted scope.
What you get
- Installable module source code for your Odoo version (17.0, 18.0, or 19.0)
- Installation and configuration on your environment (or a staging clone you nominate)
- Technical documentation — `__manifest__.py` notes, patch points, and configuration keys
- End-user guide plus one live training session for admins and power users
- Post-go-live support window for defect fixes and configuration adjustments
- UAT sign-off on a staging database with a documented rollback plan
- Git repository handover with tagged release for your version
- Configuration record of per-model defaults and group permissions agreed during scoping
Who this is for
Operations teams on dense forms
Teams working manufacturing, inventory, or accounting forms where the fixed right-side chatter crowds the fields they enter data into all day, and who need to reclaim the width without losing access to the message thread.
Support and helpdesk agents
Agents who live inside long email and note threads and want a fullscreen reading mode for conversations, while keeping a compact view for fast triage on other records.
Odoo administrators standardizing UX
Admins who want a supported, upgrade-safe way to set default chatter placement per model and per group, instead of unmanaged CSS hacks that break on the next major version.
Businesses on Community or Enterprise
Organizations on either edition that need the same configurable chatter experience delivered as a clean module depending only on base `mail` and `web`.
Installation overview
Download from ECOSIRE
Buy the license on ecosire.com and download the All In One Chatter Toolkit 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 Toolkit, 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 Toolkit Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Availability | Built to order for your database and version | You build it from scratch in-house | Instant download, generic build | |
| Display modes | Fullscreen, bottom, side, hidden — configurable | Whatever you scope and code yourself | Fixed set, no per-model tailoring | |
| Per-user / per-model config | Preference on `res.users` + per-model defaults | Possible but you design the whole scheme | Often global toggle only | |
| Upgrade safety | Version-matched, OWL-patch tested on staging | Depends on your team's discipline | May lag new Odoo OWL changes | |
| Edition support | Community and Enterprise (base `mail`/`web` only) | Whatever you target | Varies by listing | |
| Access control | Group-gated via ACL + record rules | You implement it | Rarely group-aware | |
| Support & ownership | Support window + git repo handover | Self-supported | Vendor ticket queue, no source ownership | |
| Fit to your forms | Tested against your real (studio) views | Full control, full effort | Generic — may clash with inherited views |
Frequently Asked Questions about All In One Chatter Toolkit
Is this an app I can download and install today?
No. The All In One Chatter Toolkit is build-to-order. We scope your exact modes, defaults, and target models on a short call, then build and test it against your Odoo version. It is a productized service, not an existing marketplace download.
How long does delivery take?
Typical delivery is 2–4 weeks from confirmed scope. The main drivers are how many custom or studio-inherited forms need testing and your availability for staging UAT. We confirm a firm timeline in the fixed quote after scoping.
How does pricing and scoping work?
Pricing starts from $249 as an indicative single-company base scope. After a scoping call we issue a fixed quote. Additional target models, per-group mode permissions, testing against heavily-customized forms, and multi-company rollout increase the quoted scope.
Which Odoo versions and editions do you support?
We build version-matched for Odoo 17.0, 18.0, and 19.0. The module depends only on base `mail` and `web`, so it works on both Community and Enterprise. Each build is tested against the OWL component signatures of your specific release.
What support and updates come after go-live?
Every engagement includes a post-go-live support window for defect fixes and configuration tweaks, plus the git repository so your team owns the source. Because Odoo reshuffles OWL components between major versions, upgrades to a new Odoo series are quoted as a separate rebuild.
Will it break my activities, followers, or email logging?
No. The toolkit is a display-layer patch over the existing chatter. It changes only how the panel is positioned and sized — native activity scheduling, followers, message posting, and email logging behavior are untouched.
Can different teams have different defaults?
Yes. During scoping we can set a default mode per model and restrict who may change it using `ir.model.access.csv` and record rules, so, for example, support sees fullscreen tickets while data-entry forms default to hidden.
Related Modules
Request a quote
All In One Chatter Toolkit
A made-to-order Odoo customization that turns the standard chatter into a configurable panel — fullscreen, docked-bottom, side, or hidden — per user and per model. ECOSIRE scopes, builds, installs, and supports it on your Odoo 17/18/19 database.
- Four chatter display modes — fullscreen overlay, docked-bottom drawer, right-side column, and fully hidden with a toggle button
- OWL component patch applied via `patch()` over the core `Chatter` and `FormRenderer`, delivered as an assets-bundle extension rather than a fork of core `mail`
- Per-user mode preference persisted on `res.users` so each person's choice survives reloads and new sessions
- Configurable default mode per model, set during scoping (e.g. hidden on data-entry forms, fullscreen on ticket forms)