Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
erp5 erp5
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Labels
    • Labels
  • Merge requests 137
    • Merge requests 137
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • erp5erp5
  • Merge requests
  • !393

Merged
Created Sep 15, 2017 by Jérome Perrin@jeromeOwner

dms: do not grant permissions based on Owner role

  • Overview 6
  • Commits 1
  • Changes 13

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:

Screenshot_2017-09-15_at_16.12.53

to:

Screenshot_2017-09-15_at_17.34.34

The full updated document_publication_workflow specification would be:

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.

Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: feat/remove_owner_role_permissions_on_document_workflow
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7