...
- An ACT member navigates to a subject A (entity or team) that they want to apply new AccessRequirement to.
- S/he creates an AccessRequirement B for the subject, setting up the terms, and specifying all requirements.
- Later new data C is added to Synapse.
- An ACT member determines that the new data should have the same AccessRequirement with A. S/he navigates to A and list A's AccessRequirement to find the one they are looking for.
- S/he changes the existing AccessRequirement, extends it to also apply to C.
For team, currently, we haven't exposed the ability to create an AccessRequirement at the team's place. User still navigate to an entity's AccessRequirement to find the "Create new AccessRequirement" button. Ultimately, since it doesn't make sense to have AccessRequirement that applies to both Teams and Entities, we should separating the paths of creating AccessRequirement for Teams and Entitiesan ACT member can navigate to a Team page and create an AccessRequirement for that team.
Problems
Currently, each AccessRequirement can be applied to multiple subjects. Every time a subject is added or removed from the AccessRequirement, the AccessRequirement is updated. Since applying an AccessRequirement to a subject is a relationship between AccessRequirement and subject, adding or removing subjects from AccessRequirement should only change the relationship between the subjects and the AccessRequirement, and do not update the AccessRequirement.
...