When requiring 'explicit consent' for T&C during enrollment flows, the petitioner is required to agree to these T&C.

This is fine when the petitioner is also the enrolee (as in self-registration), but sort of senseless when using the invitation flow. In that case, the petitioner is already a part of the CO and we would like the enrolee to agree to the T&C before becoming an active member of the CO.

PetitionController apparently enforces T&C approval during 'petitionAttributes' and 'view' actions. A more logical place would be 'approve' IMHO, but there is likely a very good reason to attach it to 'petitionAttributes' at the beginning of enrollment. I assume one of the reasons is that 'approve' is not necessarily executed, but at 'petitionAttributes' that could be checked.