Legacy Knowledge Base
Published Jun. 30, 2025

Unable to control visibility for Account Roles

Written By

Marcos da Silva Xavier

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

  • Users from an Organization without View permission to see other Organization information are able to do so even after setting everything up properly.
  • The steps for this issue should look like this:
      1. Create Organizations called Org1 and Org2

      2. Create Accounts  called Account1 and Account2 and associate them to Org1 and Org2 respectively.  

      3. Create users called AccountMgr1 and AccountMgr2 and assign them the Account Manager role on Org1 and Org2 respectively.  

      4. Create new Regular role called AccountRole1 Role Manager and assign AccountMgr1 to the role.  

      5. Create a new Account Role called AccountRole1.  Update the permissions on that role so the AccountRole1 Role Manager role can View and Assign Members. 

Environment

  • DXP 7.4 U55+

Resolution

  • If after following the steps, you are able to reproduce the behavior and would like to have a fix, please request a hotfix from Liferay Support with LPS-173628 added to it.
  • Upgrading to the latest version of 7.4 should address this as well.

 

 

Did this article resolve your issue ?

Legacy Knowledge Base