summaryrefslogtreecommitdiff
path: root/addons/project/security/project_security.xml
AgeCommit message (Collapse)Author
2016-02-18[IMP] hr_timesheet: Timesheet entries are now related to projectsTanguy Charlier
- Hide account_id field and add a required project_id field on timesheet entries - Remove is_timesheet field: as project_id is only required for timesheet entries and not for other analytic lines, it can be used to determine wether a line is a timeheet entry or not. - Remove project_timesheet module as all its functionalities are moved to hr_timesheet - Replace timesheets on contract option on products by timesheets on project - Small fixes and improvements in timesheets and projects views and groups
2015-11-20[IMP] Newly created users get all manager access rightYannick Tivisse
Coming from a bug in web_settings_dashboard. Invited user didn't have any rights when created from the dashboard, which was leading to an error. This bug leaded to a new discussion. Better to have basic employee having user rights for all main applications. For bigger entreprises there is an admin that will carefully remove extra rights, if necessary. The target is small businesses, it makes sense that every way to create a user gives the same result. In conclusion, each new user has a full access to the applications by default How is it implemented ? We added an inactive default user which original access right to the groups 'base.group_user' and 'base.group_partner_manager' in base. Each application will extend the default user's access right by adding the maximal access right for this application. On user creation, we will use by default the 'group_id' field from the default user. We will in the same time remove the ugly 'default_groups_ref' key which was passed sometimes in the context for some fields in some views, and sometimes nothing. So, the user can modify the access rights for the default user, but he should be aware that removing project user access rights for a default user will prevent a *created on the fly in a task* user will not be able to access the task.
2015-10-01[MERGE] forward port of branch saas-6 up to e9f1ee4Christophe Simonis
2015-09-28[FIX] project: multi-company security rules in Tasks AnalysisDenis Ledoux
This change avoid to display the tasks that a user is not permitted to see in the reporting view 'Task analysis' Closes #4399 Courtesy of jkei https://github.com/jkei
2015-08-21[REF] mail: mail_thread: followers updateThibault Delavallée
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.
2015-08-14[IMP] project,project_issue,project_timesheet,project_issue_sheet: project ↵Damien Bouvy
visibility and access rights modifications [REM] portal_project: move ALL the things - move portal access rights from portal_project and website_project_issue to project and project_issue - move portal menuitems back to their respective module - remove public visibility of projects - adapt demo data to have a 'Demo Portal' project - add correct access rights for account.analytic.line for portal users - small view tweak (do not display 'timesheet' tab if one can't see antyhing in it anyway)
2015-07-08[IMP] Project : remove task delegationYannick Tivisse
Conflicts: addons/project/wizard/project_task_delegate.py
2015-07-06[FIX] Menu configuration in root menuYannick Tivisse
2014-11-18[FIX] project: access rights and followersMartin Trigaux
For privacy_visibility 'followers' or 'portal', the user should be follower of the project (not the task). Remove public access to portal task Fixes #2372 If no project on the task (or other rule), an employee (not a portal) can access if is follower of the task. Follower rule is not enough as a user creating a rule will subscribe to the rule but to subscribe to record, the user should have access to it in the first place. To make sure the snake does not bit its tail, fallback to give access on task where the user is reponsible (user_id = user.id). Fixes #139 Adapted the tests to the new behaviour (removed not relevant and added some on creation)
2014-11-06[FIX] project: access task without projectMartin Trigaux
Allow access to task without a project defined if the user is follower. Fixes #3450
2014-04-25[FIX] project: force menu nameChristophe Simonis
bzr revid: chs@openerp.com-20140425170357-iqcqqfe71mm2z0qg
2013-06-05[MERGE]sync with trunksgo@tinyerp.com
bzr revid: sgo@tinyerp.com-20130605071905-o2ldzc6vxqnoe099
2013-04-26[FIX] project, task, issue, portal: fixed access rules for employees/portal ↵Thibault Delavallée
users + added an help on privacy_visibility. bzr revid: tde@openerp.com-20130426130259-35j0v7lg7unxhzzp
2013-04-17[MERGE]sync with trunksgo@tinyerp.com
bzr revid: sgo@tinyerp.com-20130417060441-6vnz2tiym5fawr2n
2013-04-12[FIX] [ADD] project, project_issue, portal_project, portal_project_issue: ↵Thibault Delavallée
improved privacy_visibility selection of project.project; improved access rules; added tests to enforce them. bzr revid: tde@openerp.com-20130412143719-ztjo06r900l024dm
2013-03-12[IMP]improve yml for project and add access rights as neededsgo@tinyerp.com
bzr revid: sgo@tinyerp.com-20130312112700-zamjzcjp5d9nv5n0
2012-12-19[MERGE] Harmonization of noupdate flag on security XML data, courtesy of ↵Olivier Dony
Alexis de Lattre (Akretion) ir.rule records are in noupdate data blocks to let the admin alter them without fear of them being reset at next update. Other records such as groups are in normal mode, so they can be updated whenever necessary bzr revid: odo@openerp.com-20121218232001-t425t4hi7qbmsip2
2012-10-10[IMP] project: made little change in ir ruleAjay Chauhan (OpenERP)
bzr revid: cha@tinyerp.com-20121010083548-lt8oncuanvcfpqk2
2012-10-08[IMP] project: solved the issue of 'Followers Only' visibility for projectAjay Chauhan (OpenERP)
bzr revid: cha@tinyerp.com-20121008131720-v1573v9zitef1whp
2012-09-10[FIX] Project: fixed a security rule based on follower_ids, that is now ↵Thibault Delavallée
message_follower_ids. bzr revid: tde@openerp.com-20120910075850-0b5sg1vljcc8gba9
2012-08-22[REM] project: removed custom 'followers' fields; security rule updated to ↵Thibault Delavallée
use follower_ids. bzr revid: tde@openerp.com-20120822074924-bbb5lc1w48dtebeb
2012-07-13Harmonize the noupdate flag on security XML files :Alexis de Lattre
- ir.rule objects are noupdate="1" - all other objects are noupdate="0" bzr revid: alexis@via.ecp.fr-20120713170838-pjsysliyt6twazrc
2012-06-28[IMP] improvements during code reviewQuentin (OpenERP)
bzr revid: qdp-launchpad@openerp.com-20120628121820-r8bxfzq38fy8pcgt
2012-06-28[IMP]remove tabs and add spaces instead of themSanjay Gohel (Open ERP)
bzr revid: sgo@tinyerp.com-20120628064005-zuerrpazumf5lf1q
2012-06-14[IMP] project: implemented the privacy/visibility record rule in a cleaner ↵Quentin (OpenERP)
way + some cleanup and bug fixing related to contract management bzr revid: qdp-launchpad@openerp.com-20120614100922-5g29ui88nhqojon2
2012-06-13[IMP]:passed base menus ref instead of project.Amit Patel (OpenERP)
bzr revid: apa@tinyerp.com-20120613131507-1yezuu5k7dc1h9s3
2012-06-13[MERGE] merged with main trunkQuentin (OpenERP)
bzr revid: qdp-launchpad@openerp.com-20120613090855-9tpft9kutxzgwyze
2012-06-12[MERGE] trunk-first_10_clicks-psi (add group to enable task delegation)Raphael Collet
bzr revid: rco@openerp.com-20120612095835-iisiv73hqbhe9l9w
2012-06-04[IMP]project: Set record rule for public or followersDBR (OpenERP)
bzr revid: dbr@tinyerp.com-20120604064419-3scxoolmyj8iskw3
2012-05-29[IMP]project : change reference of group group_delegate_taskAjay Chauhan (OpenERP)
bzr revid: cha@tinyerp.com-20120529073311-98bkx7jlisvinrba
2012-05-29[IMP]project : add new group to restrict delegationAjay Chauhan (OpenERP)
bzr revid: cha@tinyerp.com-20120529061415-x8salptgz19hyop2
2012-04-27[IMP] Project: Add new field in configuration wizard, add new group in ↵Jagdish Panchal (Open ERP)
security xml, and apply group in project_view.xml bzr revid: jap@tinyerp.com-20120427071701-obqjn71vu7dykjki
2012-04-04[IMP] groups: remove auto-inclusion of admin in groups, and make the ↵Raphael Collet
inclusion explicit in groups bzr revid: rco@openerp.com-20120404090830-nteimn2kvz8nkk7h
2011-12-12[IMP] base_contact, event, knowledge, product, project, sale_mrp: avoid ↵Raphael Collet
redefinition of sale groups bzr revid: rco@openerp.com-20111212145128-zx64v0uwf8n0lwyu
2011-12-12[IMP] product, project, purchase, purchase_requisition: add group categoriesRaphael Collet
bzr revid: rco@openerp.com-20111212140528-g8oxverkipswionf
2011-08-02add group implicationsRaphael Collet
bzr revid: rco@openerp.com-20110802130811-pkdmw43ufifz0tpj
2011-02-28[REVERT] all: revert incorrect change of default ir.rules for multi-companyOlivier Dony
By default only records belonging to the user's company or descendant companies should be visible. The original patch introduced visibility of records from ancestor companies, which should be suited only for a few cases, such as res.patner. Original revision: 3164.24.175 sbh@tinyerp.com-20101223095216-n6psmzicdcs8is8x lp bug: https://launchpad.net/bugs/720175 fixed bzr revid: odo@openerp.com-20110228135754-6skiy4fb9dg54xb6
2010-12-23[Fix] : correct security rule of company_idSbh (OpenERP)
bzr revid: sbh@tinyerp.com-20101223095216-n6psmzicdcs8is8x
2010-11-14[FIX] correct regression on intalling module without demo dataHarry (OpenERP)
bzr revid: hmo@tinyerp.com-20101114134821-7djwpr6nmmxu584q
2010-11-02[ADD] Task ID-1720: The demo user should be in all '<application's name> ↵uco (OpenERP)
user' groups. bzr revid: uco@tinyerp.com-20101102095327-77v9g35gjosrc5ky
2010-10-18[FIX] project: Project Managers are allowed to see all tasks even if they ↵Olivier Dony
are Project Users too bzr revid: odo@openerp.com-20101018125118-5pbcqqm2amjfvltr
2010-10-18[IMP] ir.rule reviewedFabien Pinckaers
bzr revid: fp@tinyerp.com-20101018092840-7a6wv2vw2s6a1a2s
2010-10-17[IMP] access rights, account tax include no more required, some fixesFabien Pinckaers
bzr revid: fp@tinyerp.com-20101017203119-2p80zc0nz6tjpxr8
2010-09-22[IMP]: Security, added ir.rule for Project Manager GroupRvo (Open ERP)
bzr revid: rvo@tinyerp.co.in-20100922080645-81q0mireru2k6csf
2010-08-10[IMP] crm,hr_*,auction,knowledge,mrp,product,project,sale,survey : access ↵amp (OpenERP)
rights improvements bzr revid: vir@tinyerp.com-20100810134529-wyqlh5d3zabd25gv
2010-07-13[FIX] project: security access rule correctedqdp-launchpad@tinyerp.com
bzr revid: qdp-launchpad@tinyerp.com-20100712224033-615wex94s3nqvycp
2010-07-02[IMP] clean project_* code (DHS)Mustufa Rangwala
bzr revid: mra@mra-laptop-20100702143706-k5zeko7e9n7ikvk1
2010-06-12[IMP] access rights. Remove bad stuff on point of saleFabien Pinckaers
bzr revid: fp@tinyerp.com-20100612162154-f9dgju8wsmn79gq0
2010-04-28[IMP]:changes in ir.rule demo to support the new functionaliy of ir.ruleRvo (Open ERP)
bzr revid: rvo@tinyerp.co.in-20100428125109-wq33afl8104gx6rf
2010-03-16[REVIEW]: review record rules for the sale, purchase, account, stock, and producMantavya Gajjar
bzr revid: mga@mga-20100316143337-ng6bmx315jq3ymu4
generated by cgit v1.2.3 (git 2.25.1) at 2026-10-24 13:59:57 +0000