PAH PAH user can add a remote that will populate the PAH repo `validated` that points to the CRC repo `validated` Syncing with validated remote appends but does not delete the content in the PAH repo `validated` that was populated by the installer (note CRC Prod currently has a repo `validated`, but it is not populated with any CollectionVersions) PAH user can clearly differentiate between certified and non-certified content. Note the PAH repo `rh-certified` points to CRC repo `published` which will be labeled differently in the UI as a badge on the collection list page If the PAH admin + CRC orgadmin wanted to only have PAH sync 20 of 50 collections, they would have untoggled 30 collections in CRC and the PAH would need to use the synclist url - that feature is now deprecated and will be removed in a future release. Now PAH should use the published url, an add 20 collections to the requirements.yml file of the remote. CRC (Note: there are open CRC issues that are not part of the AAP 2.4 release, CRC Stage has some updates CRC Prod will not get any repo management updates until 13Jun) Partner Engineer can approve a CollectionVersion into either `published` or `validated` Info in the "Connect to Hub" page about how to sync content down, how that content is specified, and which url to use (which was synclist url now published url) should be clear to the user.