As an Architect/developer of MooD solutions
I want to be able to restrict user interactions with Model Masters (e.g. "can use", "is not allowed to navigate to") over the web. More often than not, accessing the elements themselves is not the issue, but since there are several Model Master with different content and functionallity, the ability to use a certain Model Master is a more potent (easier to use) way to restrict user access to content. I am aware that the depth of this model of user rights would allow "a hacker" to potentially get access to underlying fields with enough knowledge of MooD and its structure and this is something to be aware of. In the end, though, being able to say "this user group cannot access this model master" gives a much improved granularity in terms of what to show and not show user than restricting fields and elements.
So That I can better tailor the user experience for the end user. It would be much better restrict access to a model master built for editing than allow the navigation to that model master and getting lots of red text when you start trying to interact with it.
Benefits Improved ability to tailor user experience over the web.
Acceptance Criteria Ability to restrict access for user and user groups to Model Masters.
Customer / Originator LFV
Please sign in to leave a comment.