For large projects, I often split up parts of work in separate .aep files. I can bring those together by importing, but then a big project is the result, and the original parts do not update when something in the big project is updated.
How grateful would it be when projects could be nested, and remain connected to there originals (e.g., when saving, a dialog comes up asking if the changes should be implemented in the original .aep as well.)
There could also be a read-only status initially (allowing rendering and placing assets in comps), and when breaking that read-only status, the connection will be lost, and the components of the nested .aep will be actually imported.
Food for thought.
AdChoices