User generated theme upload, defining permissionsUser generated theme upload, defining permissionshttps://liferay.dev/en/c/message_boards/find_thread?p_l_id=119785333&threadId=742218182024-03-29T13:54:26Z2024-03-29T13:54:26ZUser generated theme upload, defining permissionsIƱaki Bergarahttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=742218172016-05-15T05:06:47Z2016-05-15T05:06:47ZHi,<br /><br />We've got a multi instance setup going on with Liferay 6.2, and trying to use theme customizing as a selling point. As such, each instance would be owned by a different client, and each client would be able to customize their instance to their liking. Specially important would be the theme, which all of its styling and templates. Up until now I was in charge of theme modification, and other than the theme settings and variables I've prepared for users to set, I would be the only one with access to the actual theme code to modify and upload it. However, we are reaching a point where users would like to update their own theme by themeselves, without having to go through me.<br /><br />So the question is, how to allow instance owners to update their own themes while not giving them too many rights or allowing them to mess with other plugins. Ideally, I would like for me to set up a theme for them on their instance only and then allow them to update that and only that. I realize that may not be possible in the default liferay version, the app manager isn't even available on the instance control panel after all. So I'll have to compromise on creating a special role for uploaders on the main instance for now. There is a single user right now and he's relatively trustworthy, so I can count on him not messing with other stablished themes, but I shudder at him having the access to just shut down a portlet.<br /><br />I'm currently playing with the role permissions to achieve the closest result I can. I started with zero permissions and try to add only what is absolutely necessary for them. However, for some reason even after giving them everything from "general permissions" and the "app" section of the control panel, a user with that role can only see plugins configuration. I would think I only had to deal with the "app manager" section of the permissions, I don't know what the problem is there. Do I need some other permission to see the rest? And is there some way to restrict which plugins the role has a