Odoo native does not support defining a Cc field in the Mail Composer by default; instead, it only has a unique Recipients fields, which is confusing for a lot of end users.
This module allows to properly separate To:, Cc:, and Bcc: fields in the Mail Composer.
From Odoo 17.0, this module sends one mail per recipient and keeps same all headers (To, Cc, Bcc) in all emails
Features
- Add Cc and Bcc fields to company form to use them as default in mail composer form.
- Add Bcc field to mail template form. Use Cc and Bcc fields to lookup partners by email then add them to corresponding fields in mail composer form.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Adds separate Cc and Bcc fields to the email composer, email templates, company settings and sent messages, so users can send copies and blind copies without mixing them into the main recipients list.
This module splits the single "Recipients" field of the Odoo email composer into clear To, Cc and Bcc fields, making it obvious who receives a copy and who receives a blind copy.
Where it appears: - In the email composer window, next to the recipients, you now get Cc and Bcc fields (only for comment mode, not for logging notes). - On the company form, you can set default Cc and default Bcc partners that are pre-filled in the composer. - On email templates, a Bcc field is added; placeholders can be used there. - On sent messages and message records, Cc and Bcc partner lists are stored and shown. - The template preview also shows the Bcc value when present.
Business rules and automatic behaviour: - When a template is used, the Cc and Bcc addresses defined in the template are looked up as partners and pre-filled in the composer. - When no template is used, the company's default Cc and Bcc partners are pre-filled. - When sending, each recipient gets an individual email, but all copies keep the same To, Cc and Bcc headers. - Bcc recipients are hidden from the visible headers; an optional marker header can be enabled through a context key or environment variable. - Cc and Bcc partners are added to the notification recipients so they receive the email.
It touches the email composer, email templates, sent emails, messages, companies and the mail server sending logic.
Depends on
Required by other modules
Models and fields (8)
- mail.mail · extends an existing modelemail_bcc (Bcc)
- mail.thread · extends an existing model
- res.company · extends an existing modeldefault_partner_cc_ids (Default Cc), default_partner_bcc_ids (Default Bcc)
- mail.message · extends an existing modelrecipient_cc_ids (Cc (Partners)), recipient_bcc_ids (Bcc (Partners))
- mail.template · extends an existing modelemail_bcc (Bcc)
- ir.mail_server · extends an existing model
- mail.compose.message · extends an existing modelpartner_cc_ids (Cc), partner_bcc_ids (Bcc)
- mail.template.preview · extends an existing modelemail_bcc (Bcc)
Text generated by AI (DeepSeek) from reading the Odoo 18.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: 4 confirmed, 5 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/mail.
terminal Installation and usage
OCA documentation · Odoo 18.0Configuration
Source · Odoo 18.0In company form there are two fields to set default cc and bcc partners.
>
In template form there are two fields to set cc and bcc emails.
>
Usage
Source · Odoo 18.0The partners cc and bcc from company form will be used to fill in mail composer form.
>
When select a template that has cc and/or bcc emails, the emails will be used to lookup partners then found partners will be added to corresponding mail composer's fields.
>
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.