Proposal:

1) Add a new property personalizable in the template definition. We already support similar properties deletable, moveable and writable that are specific to component templates and restrict the actions that editors can take on components. This is an existing pattern.

Example:

templateScript: /my-module/components/textImage.ftl
renderType: freemarker
dialog: my-module:components/textImage
personalizable: false

The new property personalizable should be true by default. This means that component personalization is an opt-out feature: a site admin needs to specifically turn the feature off if they don't want to allow component personalization. It also means that an editor can start experimenting with component personalization immediately without having to ask IT to turn the feature on.

2) To restrict personalization of a component in a particular area, add a new permission personalize in the area definition. This is also an existing pattern. We already support the permissions write, move and delete. As a use case, you may want to allow editors to personalize textImage everywhere except in the footer area.

Example: Restrict personalization of textImage in the footer area to the superuser role

areas:
  footer:
    availableComponents:
      textImage:
        id: mtk:components/textImage
        permissions:
          personalize:
            roles: [superuser]