Merge !393 dms: do not grant permissions based on Owner role
My use case is that we have an ERP5 configuration where a PDF document is "implictly" created when user validate an invoice. Later this PDF becomes "secret" and we want to remove permissions on the PDF to all except a small group of users. Please also read commit message for more uses cases. My idea is to change globally document publication workflow to remove permissions for Owner, because usually in workflow we don't have security for Owner, except in draft states. For cases where the user who created the document must have certain permissions for the whole lifetime of the document, we can create a security rule where this user would be Associate. Also, for the case of documents, maybe we would want to use *Contributors* fields instead of Owner, as it gives more flexibility. In what I am suggesting, the permissions by state would change from:  to:  The full updated `document_publication_workflow` specification would be: [P-ERP5.Workflow.Security.After.Removing.Owner.pdf](/uploads/02eac46ec436385d0d0577695803b3b5/P-ERP5.Workflow.Security.After.Removing.Owner.pdf) But this is an incompatible change, because some users will loose access to some documents they use to have access. /reviewed-on nexedi/erp5!393
Showing
Please register or sign in to comment