Ability to "Lock" projects from being edited when assigning multiple communities to the same project

What is the challenge or problem or you are trying to solve?

Ability to “lock” the project so that I can seamlessly add multiple communities to the same project without the worry of them editing. If I want to add projects to communities from the corporate office, it will be most efficient as an Enterprise user to not have to 'duplicate' and re-name for all of my communities. But instead, once it's locked from editing, I can assign as many of my communities on it at one time.

What is the impact?

Describe your idea