@fionas76543059,
For static template projects, we typically try to set up the content authors off to a great future by pre-configuring allowed components to each template. Once when the /etc/designs are configured and released, we will change the filter in our code from mode replace to merge (existing content are not modified, i.e. only new content is added and none is deleted or modified). This ensures that we will not overwrite the content author's settings.
When there's a need for developers tamper with the /etc/designs configuration, request a scheduled content freeze amend, and re-deploy.
REPLY: They complain that sometimes they have to redo parts of the "allowed components", as the configuration disappears, possibly when the components change, like getting a new Component Group. Has anyone ever heard of this problem before.? This situation looks like an issue with releasing content and forgetting to manage the filter.xml.
I hope this helps,
Brian.