Community mailing list archives
Re: Warehouse access rightsby
Thanks Quentin for your explanation.
However, I disagree your opinion about the simplicity, it should be a default pattern and you can update it later if you want (just like the CRM).
About the second point, I already thought about such solution before, but this costs me a great effort to modify all the default routes made by Odoo, and get the routes very complicated.
Am I right, or I'm missing something?
On 29/04/2015 11:07, Abu Helal wrote: > Hi, > The first point to discuss is why there is no default security pattern > for the warehouse module like the CRM? It's a good question, but the main policy of Odoo is to be simplest as possible so, I think, don't put default security pattern on warehouse is the result of this policy because you can add your own security pattern after the installation. > The second point, how we can think when trying to make a security pattern. > Let's say there is a stock move from source A to destination B, then who > is supposed to have the access rights on this move warehouse A stock > keeper, our B one? Each security pattern is specific of the company behavior. For your example, maybe it's an employee of the warehouse A that make the move or maybe it's an employee of the warehouse B that make the move. So, it depends on the policy of the company, there is no generic patter to that. But, you can also have two moves : one from A to a virtual location (move owned by A) and one from the virtual location to B (move owned by B). With this behavior, you can apply security rules on each move and A don't see the move from virtual location to B and B don't see the move from A to virtual location. To resume, it depends on your implementation of the ERP, it's why Odoo developers didn't put security patterns on warehouses. Regards, -- Quentin THEURET TeMPO Consulting 20, Avenue de la paix 67000 Strasbourg France http://www.tempo-consulting.fr Tel : 33 (0)3 88 56 82 18 Fax : 33 (0)9 70 63 35 46