| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Use a sudo on a ir_cron creation instead of giving full access rights
to employee on a technical field
|
|
|
|
Purpose:
Having the res_group defined in base and sales_team auto installed
with mail doens't make sense.
- Move the empty res_config class and the related view from
base_setup to sales_team (base_setup only contains the 'General Settings'
model and views
- Move the 'sale' related content from product to sale module (Access rights,
menuitems,...)
- Set sales_team at autoinstall False. The module is installed when needed by
crm or sale for example
- Set sales_team as a dependency of voip. (Access rights defined for configuration
purpose)
- Set sales_team ad a dependency of subscription (Access rights issue too)
[FIX] account: move some ir.model.access to sale module
[FIX] payment: Move some ir.rule to website_sale
[FIX] stock: move some ir.model.access rule to sale_stock
[FIX] project: Move some ir.model.access rules to crm_project_issue
[FIX] mrp: Move some ir.model.access rules to sale_mrp
[FIX] calendar: move some ir.model.access rules to crm
Rename xmlids accordingly. Example: 'base.group_sale_manager' becomes
sales_team.group_sale_manager.
[ADD] sales_team: See own documents => See only his sales team
Moved the "User: Own Leads Only", "User: All Leads" and "Manager" groups from sale and crm
into sales_team module. Add the record rules so that user can see only his Own Sales Team
if "See Own Leads" is sales right and can see all sales teams if he is having sales rights
of "See All Leads" or manager.
|
|
This branch need more testing instead of doing 10 fixes. A lot of issues are occuring
when installing modules in different orders.
This reverts commit fa6e415cdb23ce9494487ed672792186157b40e0.
|
|
Purpose:
Having the res_group defined in base and sales_team auto installed
with mail doens't make sense.
- Move the empty res_config class and the related view from
base_setup to sales_team (base_setup only contains the 'General Settings'
model and views
- Move the 'sale' related content from product to sale module (Access rights,
menuitems,...)
- Set sales_team at autoinstall False. The module is installed when needed by
crm or sale for example
- Set sales_team as a dependency of voip. (Access rights defined for configuration
purpose)
- Set sales_team ad a dependency of subscription (Access rights issue too)
Rename xmlids accordingly. Example: 'base.group_sale_manager' becomes
sales_team.group_sale_manager.
|
|
Subscription: moved access rights from tools to sales groups. As this was the
last module to use the tools module category, it has been removed. This
category was used like a misc group. However now we try to better classify
modules.
|
|
bzr revid: ssu@tinyerp.com-20120307054759-dsp0r4n1pbf8x4hg
|
|
bzr revid: fp@tinyerp.com-20111212181113-mhnnbps3ip8ls6pp
|
|
access rights
bzr revid: amp@tinyerp.com-20101005133252-hz7jww5xuzjrxal1
|
|
survey,account,email_template,idea,lunch,marketing_campaign,sale,stock_planning : Improvements in access rights
bzr revid: vir@tinyerp.com-20100813060634-laq3wb2d660wcrrp
|
|
bzr revid: amp@tinyerp.com-20100807132304-yzow2wyjo2utdl51
|
|
bzr revid: fp@tinyerp.com-20080903224650-u1oadqv9x75atmyl
|
|
bzr revid: fp@tinyerp.com-20080903180400-df7l6wxg1zpirmmi
|
