...
- AccessRequirement itself can have similar terms. AccessRequirements do not have name. Without the context of which subject it applies too, it is hard for user to identify which AccessRequirement they wants.
- ACT members have to adapt to a new way to use AccessRequirement.
Questions:
- Does it make sense to have AccessRequirement as a stand alone object that can be created without associate with a subject?
- If so, how would user navigate to or search for created an AccessRequirement?