...
- If group attributes change, see if it affects group attributes
- See which memberships change, if these are related to subject attributes, then update the attribute tables
- If attributes change, see which policies those refer to, and incrementally adjust the membership of those groups
- Policy changes should change the population
Loading groups that are used
We could have another table which links up expressions (policies) with the groups used in those policies. Loader jobs which only load groups which are used (if a fraction of course groups are used) could key off that table to know that a group is used in a policy and needs to be populated.