Odoo 19 Discuss: choose a channel, note or customer message
A communication decision table, external-mention warning and verified canned-response path for teams working inside Odoo 19.
Applicability
Odoo 19; app installation, subscription, access rights and mail configuration must match each workflow. Examples are fictional; UI translations may differ.
Research method
Odoo 19 official documentation research only; no new Odoo product test. Source checks apply only to the scopes listed below.
Choose where the decision belongs before typing the message. A discussion about one quotation should remain connected to that record; a team-wide operating question belongs in a suitable Discuss channel. This guide is based on Odoo 19 documentation, not a live notification or access-control test.
Contents
- Choose the communication surface
- Log note does not remove the need to check recipients
- Set channel access deliberately
- Configure and use canned responses
- Diagnose missed notifications and wrong audiences
Choose the communication surface
| Need | Suitable place | Check before posting |
|---|---|---|
| Ask about one opportunity's pricing decision | Its chatter, if available | Record access and note recipients |
| Discuss a team process | Appropriate Discuss channel | Channel membership and privacy |
| Ask a short person-to-person question | Direct message | Whether the final decision must be copied to the record |
| Send a customer an update | Send message on the relevant record | Followers, recipients and attachments |
Chatter exists on records whose models provide it, not every screen or record in Odoo. A chat message containing a record link is not proof that its recipient has access to the linked record. Decide where to record the outcome so a replacement colleague can understand the decision without searching private conversations.
Log note does not remove the need to check recipients
For a fictional quotation discount, an internal note might say “Margin approval needed before revising the offer”. Use Log note, identify the internal colleague and check their entry in the mention selector. An @mention produces a notification according to settings; it is not a universal promise that every mentioned person becomes a permanent follower or can view all records.
There is a significant documented exception to “internal”: Odoo 19 says an outside contact mentioned in an internal note receives its contents and directly attached files by email. Their reply is logged and they become a follower. Do not mention a customer's contact in a margin or staffing note. An internal-mode label does not override that recipient action.
For a customer-facing update, select Send message and inspect the recipients, including followers. Open the expanded composer when the audience or attachments need careful review. The customer text should state the accepted next step, not expose the internal discussion that produced it.
Set channel access deliberately
Create a channel using the plus beside Channels, then inspect its settings and Privacy tab. Authorized Group controls who can join; Auto Subscribe Groups enrolls members of selected groups. These are distinct purposes. Naming a channel “Management only” is not access control.
For a fictional delivery channel, specify its purpose, membership owner and where final task decisions are recorded. Review guests and invitations as part of membership. Copying a discussion into a channel with a broader audience can disclose information even if the original record is restricted.
Configure and use canned responses
The documented Odoo 19 route is Discuss → Configuration → Canned Responses. Create a shortcut and its replacement text. Use a narrow fictional response such as “Please provide the order reference and a short description of the issue”; do not include a real customer's data in a reusable reply.
If Authorized Group is blank, the response is available only to its creator. Add the appropriate group when it is intended for a support team. Even an administrator who can edit another person's response does not automatically have permission to use it without the relevant authorized group.
In a supported conversation or chatter composer, use the plus menu's Insert a Canned Response, or type :: to find a response. Review the inserted text before sending. This is a saved text aid, not a completed action or assurance that facts such as dispatch dates are current.
Diagnose missed notifications and wrong audiences
| Symptom | First check | What to change |
|---|---|---|
| Colleague cannot open the record | Model and record access | Request the appropriate access review; another mention will not grant it |
| Colleague did not notice a mention | Correct selected contact and notification preference | Agree an escalation owner and due activity for critical work |
| Team cannot find a canned response | Creator and Authorized Group | Share with the intended group rather than duplicating the text per user |
| Customer received an internal discussion | Outside mention, followers and message mode | Record what was sent and correct the communication process |
| Sent message edited but customer sees old text | Whether a new message was actually sent | Send an explicit correction if necessary |
Official documentation says editing a sent message does not send an updated message to the recipient. Treat a meaningful correction as a new communication decision; changing stored text cannot recall an already delivered email.
For a first rollout, choose one record type and one team channel. Write a three-line rule: where internal decisions go, who may send externally and where the final result is recorded. Ask APAA to map that rule to a scoped setup if record access and team responsibilities are currently inconsistent.
Sources
- Chatter
Record-specific availability, notes, external mentions, followers and message editing
Source checked
- Canned responses
Configuration path, authorized groups and :: insertion
Source checked
- Use channels for team communication
Privacy, authorized groups, subscriptions and invitations
Source checked