Skip to Content

Rich Chatter

by
Odoo
v 17.0 Third Party 3
Download for v 17.0 Deploy on Odoo.sh
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Lines of code 645
Technical Name rich_chatter
LicenseLGPL-3
Websitehttps://armandi.es
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Lines of code 645
Technical Name rich_chatter
LicenseLGPL-3
Websitehttps://armandi.es

Rich Chatter for Odoo 17

Add visual rich text editing to Odoo Discuss and the standard chatter composer while keeping the native mail.thread workflow for followers, notifications, internal notes, and customer emails.

Features

  • Visual WYSIWYG formatting while typing, without exposing HTML tags to users.
  • Rich formatting for Discuss, chatter messages, and internal notes.
  • Bold, italic, underline, strike, quotes, colors, lists, links, and separators.
  • Discuss-friendly keyboard behavior: Enter sends, Shift+Enter creates a normal editor line break.
  • Sanitized HTML storage for safer rendering.
  • No change to standard follower, notification, or email flows.

Screenshots

Standard Odoo chatter composer before enabling Rich Chatter
Chatter before: standard Odoo internal note composer.
Odoo chatter composer with Rich Chatter formatting toolbar
Chatter after: quick rich text toolbar in the native composer.
Standard Odoo Discuss composer before enabling Rich Chatter
Discuss before: compact plain text composer.
Odoo Discuss composer with Rich Chatter formatting toolbar
Discuss after: visual rich text editor with expanded writing area.

Free Module

This module is free and distributed under the LGPL-3 license.

Compatible with Odoo 17 applications that use Discuss and the standard chatter on mail.thread models.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author, please use the developer contact information. They can usually be found in the description.