In order to disable specific fields from appearing in Liferay, the specific component from gogo shell must be disabled. For example, to hide the "Identification" tab in the user administration UI, on each startup, we can set scr:disable com.liferay.users.admin.web.servlet.taglib.ui.UserIdentificationFormNavigatorCategory. However, every time that the server restarts, this disabled component resets and is reinitialized, meaning that the disabling of this component must be set again. As this is the case, this specific strategy is a non-permanent workaround that does not reliably address a long-term strategy.
Permit disabling of certain fields from the user account administration through the UI or via properties.
The implementation of this functionality would allow administrators to effectively control what a user can/cannot set out of the box. For example, if we consider the use case of an organization that only wants users to set their email address and full name, it would be beneficial to remove fields such as Job Title, social network accounts, and so on. Permitting Liferay admins to make this change from the UI or through properties allows a level of control that would permit Liferay to suit their specific organizational requirements.