redacted redacted redacted
I’m not the expert on all things Application Modeling but I believe the answer is yes, you need to copy the whole module.
In 2024.06 you can add a “Permission” which specifies a role who can see this menu entry. However, the setting is ignored if you don’t specify a menu name. This means that you have to create a new menu entry to be able to show and hide models in a module. This means creating a whole module to achieve the desired functionality with modeling alone.
There may be a more elegent solution based around declaring your models in a module with no menu entry (Leave “Menu” → “Name” blank) but I couldn’t get it to work with modeling alone.
You could use a custom model loader implementation that takes the role into account and returns a different form model for different roles.
The new, experimental dynamic config feature might be a good fit.
redacted redacted redacted
Dynamic config is an API feature (code).