Open OCA-git-bot opened 1 month ago
For v18, I would like to create new security groups, and use these instead of the accounting groups to control access to MIS reports and templates:
For budgets:
On the budgets part: does it make sense to not access MIS budgets, but see the results in a MIS report? I consider OK to have a rw access group, but ro should be the MIS base one.
It is actually possible to view MIS Reports without access to account.move.line
. So, in the same spirit, since budget information can be sensitive data, I'd say it's worth a separate security group. Viewer of MIS Reports will then not be able to view reports involving budget data, but other reports will work.
I think it will be weird to access the report, but not to be able to preview it/export it. Let's block it by access rules (or inheriting the _check_access
method) for not viewing them in the list.
working on mis_builder
Todo
https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-18.0
Modules to migrate
Missing module? Check https://github.com/OCA/maintainer-tools/wiki/%5BFAQ%5D-Missing-modules-in-migration-issue-list