[REF] mail: mail_thread: followers update

Followers can now be partners or channels. Partners following a document
will receive needaction, as previously. However people can follow documents
through channels. Members of a channel are able to listen to a stream
of messages using the channel. Those messages do not create needaction
messages. It is therefore possible to follow documents without receiving
too much notifications. For interesting documents subscribing with its
partner will create notification.

message_follower_ids fields is udpated. It is now a many2many to
mail.followers, not to res.partner anymore. A subscription can be either
a partner (partner_id) or a channel (channel_id).

Some access rules have been updated accordingly.

2 files changed, 5 insertions, 4 deletions

diff --git a/addons/mail/security/ir.model.access.csv b/addons/mail/security/ir.model.access.csv
index 701bbffbeca..7193db4a9a2 100644
--- a/addons/mail/security/ir.model.access.csv
+++ b/addons/mail/security/ir.model.access.csv
@@ -7,8 +7,8 @@ access_mail_mail_portal,mail.mail.portal,model_mail_mail,base.group_portal,1,1,1
 access_mail_mail_user,mail.mail.user,model_mail_mail,base.group_user,1,1,1,0

 access_mail_mail_system,mail.mail.system,model_mail_mail,base.group_system,1,1,1,1

 access_mail_followers_all,mail.followers.all,model_mail_followers,,1,0,0,0

-access_mail_followers_portal,mail.followers.portal,model_mail_followers,base.group_portal,1,1,0,0

-access_mail_followers_user,mail.followers.user,model_mail_followers,base.group_user,1,1,0,0

+access_mail_followers_portal,mail.followers.portal,model_mail_followers,base.group_portal,1,1,1,0

+access_mail_followers_user,mail.followers.user,model_mail_followers,base.group_user,1,1,1,0

 access_mail_followers_system,mail.followers.system,model_mail_followers,base.group_system,1,1,1,1

 access_mail_notification_all,mail.notification.all,model_mail_notification,,1,0,0,0

 access_mail_notification_portal,mail.notification.portal,model_mail_notification,base.group_portal,1,1,1,0

diff --git a/addons/mail/security/mail_security.xml b/addons/mail/security/mail_security.xml
index c05d434c789..642975ea7a5 100644
--- a/addons/mail/security/mail_security.xml
+++ b/addons/mail/security/mail_security.xml
@@ -7,17 +7,18 @@
             <field name="name">Mail.channel: access only public and joined groups</field>
             <field name="model_id" ref="model_mail_channel"/>
             <!-- This rule has to be improved for employee only groups -->
-            <field name="domain_force">['|', '|', ('public', '=', 'public'), ('message_follower_ids', 'in', [user.partner_id.id]), '&amp;', ('public','=','groups'), ('group_public_id','in', [g.id for g in user.groups_id])]</field>
+            <field name="domain_force">['|', '|', ('public', '=', 'public'), ('message_partner_ids', 'in', [user.partner_id.id]), '&amp;', ('public','=','groups'), ('group_public_id','in', [g.id for g in user.groups_id])]</field>
             <field name="perm_create" eval="False"/>
         </record>
 
         <record id="mail_followers_read_write_own" model="ir.rule">
-            <field name="name">mail.followers: read and write its own entries</field>
+            <field name="name">mail.followers: write its own entries</field>
             <field name="model_id" ref="model_mail_followers"/>
             <field name="groups" eval="[(4, ref('base.group_user'))]"/>
             <field name="domain_force">[('partner_id', '=', user.partner_id.id)]</field>
             <field name="perm_create" eval="False"/>
             <field name="perm_unlink" eval="False"/>
+            <field name="perm_read" eval="False"/>
         </record>
 
         <!-- If technical rights then read and write others subscriptions -->