Legacy Knowledge Base
Published Jun. 30, 2025

Custom panel app and portlet is not shown for non omniadmin users

Written By

Jorge García Jiménez

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

  • We have a custom module that puts a module in the product menu.
  • We have a site role, S1, with permissions assigned to the module:
    • Access in Site and Asset Library Administration,
    • View.
  • If we log in with:
    • an admin user, we can see the category and the module.
    • a regular user with a regular role with enough permissions, we can see the category and the module.
    • a regular user with site role S1, we cannot see the category nor the module under the product menu.

Environment

  • Liferay DXP 7.4

Resolution

  • This custom module has a PanelApp class. This PanelApp points to a PanelCategory via the OSGi component property "panel.category.key".
  • The value of thsi property has to begin with the prefix "site_administration".
  • In this example of the Liferay codebase, the value of "panel.category.key" is the constantPanelCategoryKeys.SITE_ADMINISTRATION_CONTENT, which is resolved to "site_administration.MyCustomPortlet", fulfilling the prefix requirement.
Did this article resolve your issue ?

Legacy Knowledge Base