Closed
Description
We should have a label or class that prevents (some) modifications, deletions of objects. It should also not be used during creates. This is so that we can mark types as protected to prevent accidental damage.
A consideration is with dynamic schema, we need uses to be able to edit must/may, but not the schema elements themself, so this could be achieved with a system protected access profile, then use that access profile over the schema types.
Perhaps an approach is a self-referring access control that prevents this kind of change?