Skip to Content
This question has been flagged
chatterrecord_rulesaccess rights
2 Replies
1146 Views
Avatar
Uday Sankar k

I’m facing an issue related to chatter  visibility in Odoo and would like to understand if this is expected behaviour or if I’m missing something.

For a custom model
some users cannot see any chatter messages (tracking / history), and the UI shows:

However:

  • Chatter messages do exist in mail_message

  • Other users (including admin / superuser) can see the full chatter

  • The affected users can still:

    • Open the record

    • Perform actions on the record

    • Post new messages (but cannot see old ones)

There are no messages in this conversation

I already checked Access rights (ir.model.access) – OK
Record rules (ir.rule) – evaluated and tested
No record rules on mail.message
The default company of the affected users is different from the company of the record
Even when the record is accessible and backend checks pass, chatter remains empty

what ELSE is left to check in this case?

Avatar
Discard
Avatar
CandidRoot Solutions
Best Answer

Hey Uday,

I have banged my head against this exact wall before. Since you already confirmed standard ACLs and Record Rules are passing, and the user can actually write to the record, standard logic says they should see the history.

However, because you mentioned "The default company of the affected users is different from the company of the record," I am 99% sure this is the "Multi-Company Message Rule" biting you.

Here is what is likely happening and what you need to check:

1. The mail.message Company Trap We often forget that mail.message is a model itself, and it has a company_id field.

  • The Scenario: When the record was created (or when those old messages were posted), they were likely stamped with Company A.

  • The Problem: Even if your user (from Company B) has a record rule to see the Record itself, there is a global multi-company rule that applies to every model with a company_id field.

  • The Conflict: If the user is logged in and their "Allowed Companies" (top right switch) is set to only Company B, Odoo’s standard multi-company security will strictly hide any mail.message rows belonging to Company A. They see the record shell, but the messages inside are filtered out by SQL.

The Fix/Test: Ask the affected user to tick the box for the Record's company in their top-right company switcher (so they are in "Company B + Company A" mode). I bet the chatter instantly appears.

2. Subtypes and "Internal" Groups If the multi-company check passes, the next "invisible" filter is the Message Subtype.

  • Check the mail.message rows in the database. Do they have a subtype_id?

  • Go to Settings > Technical > Email > Subtypes.

  • Check the subtype for "Discussions" or "Note" related to your custom model.

  • If the "Internal Only" boolean is checked on that subtype, users must be part of the specific Internal/Employee group to see them. If your custom users are "Portal" or "Public" or a custom restricted group, they won't see messages of that subtype.

3. The "Partner" Filter (Rare but possible) Sometimes, messages are created with specific partner_ids (private notifications). If the message was sent "Privately" to a specific list of partners and the current user isn't in that list, they won't see it, even if they have access to the document.

My money is on #1. Since they can post new messages (which likely get stamped with their current company, Company B), they can see their own new messages, but the old history (Company A) remains invisible until they switch their allowed company context.

Let me know if that was it!

If this helped, kindly upvote.
Best Regards,


CandidRoot Solutions Pvt. Ltd.
Mobile: (+91) 8849036209
Whatapp: (+91) 8849036209

Email: info@candidroot.com
Web: https://www.candidroot.com

Avatar
Discard
Avatar
Cybrosys Techno Solutions Pvt.Ltd
Best Answer
Hi,

When users cannot see chatter messages (tracking/history) for a custom Odoo model, even if general access rights and record rules appear correct, the issue often stems from specific configurations. First, ensure the custom model inherits from mail.threadand includes the <chatter/>element in its form view. Crucially, verify that affected users have at least read access to the custom model itself, as chatter visibility is tied to record access. A common cause is messages being posted as "internal notes," which are typically only visible to users in the base.group_usergroup (internal users); if the users in question are portal users or lack this group, they won't see these notes. While record rules are checked, a deeper review is warranted, as a restrictive rule on the custom model can prevent access to the record and, consequently, its chatter. Finally, confirm that the _mail_post_accessattribute on mail.threadis not inadvertently restricting visibility.


Hope it helps.


Avatar
Discard
Related Posts Replies Views Activity
Access Rights Limitations
record_rules Security access rights
Avatar
Avatar
2
Nov 24
3329
Allow user to leave messages in chatter but not alter record
security chatter record_rules
Avatar
0
Feb 24
3358
Acces rights, record rules and notification and messages V14
groups chatter record_rules v14
Avatar
0
Jun 24
1454
Leaves Approval through hierarchical manner
record_rules
Avatar
1
Apr 26
4536
Toggle chatter button on todo tasks - Have it everywhere in odoo? Solved
chatter
Avatar
Avatar
1
Mar 26
1729