diff options
| author | Antony Lesuisse <al@openerp.com> | 2016-07-05 23:03:32 +0200 |
|---|---|---|
| committer | Antony Lesuisse <al@openerp.com> | 2016-07-06 01:17:43 +0200 |
| commit | ccf606e026a49a77731df20345f109aa0c64ef49 (patch) | |
| tree | d85f5068576a6e9e65782af0d9dfe82dbbe1ed2f /addons/project/security/project_security.xml | |
| parent | 05e0bf3f1b7b96a9f8e4f95e529bfe2cc7b44d17 (diff) | |
[ADD] website_project: Portal access to Projects
Split project to move portal features to a new module named website_project.
Portal users may now access their projects and tasks throught the
website_portal My account page. The Backend portal menuitem is removed.
Simplify the privacy settings of project, to be visible to portal users the
project must be in 'portal' mode.
Original authors: Vipul Bhatt, Florian Wintjens
Diffstat (limited to 'addons/project/security/project_security.xml')
| -rw-r--r-- | addons/project/security/project_security.xml | 48 |
1 files changed, 5 insertions, 43 deletions
diff --git a/addons/project/security/project_security.xml b/addons/project/security/project_security.xml index 56c51d7eea2..7f06484836c 100644 --- a/addons/project/security/project_security.xml +++ b/addons/project/security/project_security.xml @@ -43,10 +43,10 @@ </record> <record model="ir.rule" id="project_public_members_rule"> - <field name="name">Project: employees: portal, employees or followers</field> + <field name="name">Project: employees: following required for follower-only projects</field> <field name="model_id" ref="model_project_project"/> <field name="domain_force">['|', - ('privacy_visibility', 'in', ['portal', 'employees']), + ('privacy_visibility', '!=', 'followers'), ('message_partner_ids', 'in', [user.partner_id.id]) ]</field> <field name="groups" eval="[(4, ref('base.group_user'))]"/> @@ -63,15 +63,13 @@ </record> <record model="ir.rule" id="task_visibility_rule"> - <field name="name">Project/Task: employees: portal or employee or (followers and following)</field> + <field name="name">Project/Task: employees: follow required for follower-only projects</field> <field name="model_id" ref="model_project_task"/> <field name="domain_force">[ '|', - ('project_id.privacy_visibility', 'in', ['portal', 'employees']), + ('project_id.privacy_visibility', '!=', 'followers'), '|', - '&', - ('project_id.privacy_visibility', '=', 'followers'), - ('project_id.message_partner_ids', 'in', [user.partner_id.id]), + ('project_id.message_partner_ids', 'in', [user.partner_id.id]), '|', ('message_partner_ids', 'in', [user.partner_id.id]), # to subscribe check access to the record, follower is not enough at creation @@ -87,42 +85,6 @@ <field name="groups" eval="[(4,ref('project.group_project_manager'))]"/> </record> - <!-- Portal --> - <record model="ir.rule" id="portal_project_rule"> - <field name="name">Project: portal users: portal or following</field> - <field name="model_id" ref="project.model_project_project"/> - <field name="domain_force">[ - '|', - '&', - ('privacy_visibility', '=', 'portal'), - ('message_partner_ids', 'child_of', [user.partner_id.commercial_partner_id.id]), - '&', - ('privacy_visibility', '=', 'followers'), - ('message_partner_ids', 'in', [user.partner_id.id]) - ]</field> - <field name="groups" eval="[(4, ref('base.group_portal'))]"/> - </record> - - <record model="ir.rule" id="portal_task_rule"> - <field name="name">Project/Task: portal users: (portal and colleagues following) or (followers and following)</field> - <field name="model_id" ref="project.model_project_task"/> - <field name="domain_force">[ - '|', - '|', - '&', - ('project_id.privacy_visibility', '=', 'portal'), - ('project_id.message_partner_ids', 'child_of', [user.partner_id.commercial_partner_id.id]), - '&', - ('project_id.privacy_visibility', '=', 'followers'), - ('project_id.message_partner_ids', 'in', [user.partner_id.id]), - '&', - # on employee project can receive messages but not access the object - ('project_id.privacy_visibility', '!=', 'employees'), - ('message_partner_ids', 'in', [user.partner_id.id]) - ]</field> - <field name="groups" eval="[(4, ref('base.group_portal'))]"/> - </record> - <record model="ir.rule" id="report_project_task_user_report_comp_rule"> <field name="name">Task Analysis multi-company</field> <field name="model_id" ref="model_report_project_task_user"/> |