Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

Can edit option from content approval be removed or disabled ?

Written By

Kanchan Bisht

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • The workflow has been enabled for web content. For that, one site role has been created that can approve or reject it. But while approver assigns it to themself, they will get edit option also and from the permission perspective only view permission has been assigned for the approverimage_2021_03_30T08_49_15_280Z.png

Environment

  • Liferay 7.2

Resolution

  • It is not currently possible to disable it using out-of-the-box methods.

Additional Information

  • Scenario: When a workflow is enabled for an asset type, and an asset is submitted for publication, anyone with a reviewer role immediately has full permissions over that asset.
  • A feature request for an out-of-the-box method to disable the permissions grant on the assets list has been created, and its progress can be followed at LPS-91795. Voting for this feature request will increase its visibility.
  • While that feature request is being considered, the customer could do customization as a workaround that disables WorkflowPermissionImpl.hasImplicitPermission() eg. for this method to always return false, leaving the other permission checkers to determine if the user has access. In DefaultModelPermissionChecker there is a chain of permission checkers. If one of them returns false, it goes to the next one, and so on. As soon as one returns true, the chain is cut and it considers the user to have the permissions. If you take WorkflowPermissionImpl.hasImplicitPermission() out of this chain (or make it return false), the reviewer user will not get all those permissions that constitute the issue for your use case.
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?