External CMS management through the API is an increasingly common scenario for me, because I'm seeing more customers want Notion / Airtable / Sanity as the source of truth.
This raises a problem, since the Webflow API fully allows any HTML storage, including tables and scripts, while the Designer CMS interface automatically sanitizes that content without warning.
Ideally there would be a way through the API to "lock" a rich text field so that it's protected and simply can't be edited in Webflow in the CMS, OCE, pop-up CMS, etc.
Locking level
I'm uncertain yet if that "lock" mechanic makes more sense at the field level, or at the item level or at the collection level. My intuition says the collection level or item level are more relevant.
Appgen
This might even relate to e.g. appgen. If I created an app that can save user submissions to the CMS, and I had a custom HTML editor, I'd need to be able to prevent users from opening the CMS and accidentally nukitizing that data.
Discussions
Steve Rouse
