Separating experiment tracking by team while keeping shared model visibility?

Several teams need independent experiment spaces and retention policies, while reviewers want one place to discover approved models and understand lineage. How would you structure experiments, registered models, permissions, and naming so teams can move independently without creating a fragmented model catalog?