Element-state based user rights

As a solution developer

I want to be able to set up user rights which are dependent on object/element states. 

So That MooD can be set up to recognise different user right through the life cycle of elements. The story behind this is that there are instances where a users group can make certain edits to a set of elements, so long as they are in the "proposed" state. However, when they enter the "in effect" state, these users should not be able to make changes to those elements - they would either have to go into a new state ("considered for change") or be handled by a super user.

This could potentially be tied into a baselining/versioning story.

Benefits: Ability to deliver solutions with higher precision user rights.

Acceptance Criteria

1. Ability define states for elements (through dedicated mechanisms or from selecting for instance a pick list to represent a state)
2. Ability for MooD to recognise element state and assigning user rights on a individual user or group level in a state-dependent manner.

Customer / Originator LFV

Priority Low