Feature Request Lock and expose fields or components

Working in teams with prefabs variants and nested prefabs can sometimes lead to accidentally applying changes to the base prefab with unknown consequences.

To fix that, we could be inspired by Figma components. Once a prefab is created their fields and components can be locked and the user could manually expose which ones can be overriden.

Do you think this is a good idea? Can you think of counter points or additions for this method?

 

From the FAQ from like 2018:

Can we get the ability to treat Prefabs as “black boxes” or "encapsulated" where by default properties can't be edited (overridden) on instances of the Prefab?
There's a simple version of this where no properties can be overridden on instances (except root Transform and a few other basic ones), and a more complex version of this, where it would be possible to expose specific properties in a Prefab Asset so they can be overridden on instances too. Both are things we have been looking into, and would like to do for future releases.

Welp, I guess we just got to wait...

 

Another 5 years