Unless I am missing something, it seems like a real hazard for the Rich Text Field contents to be openly editable on Entities created by Integrations such as with Discourse or Integromat. At a very minimum it is unclear what the consequences of doing so will be. Obviously without Bi-directional integrations/sync, an edit should not propagate back to the source app. And since there is as yet no answer to my question about What happens when an integration is updated/expanded?, I am unsure if edits will be preserved if/when the Rich Text is updated via the Integration, or what.
This confusion and uncertainty could be avoided by simply making this Rich Text Field uneditable. Which is exactly how all other default Integrations fields are treated AFAIK, and this makes good sense. Given that you can’t sync back any changes, you shouldn’t be able to make changes to this data in Fibery. You can of course create new fields on Integrations Types, which you should be able to edit, or create Links to other Entities, or Relations, all of which should be able to address any need that was possibly met for some by being able to edit this Rich Text content.
I realize that the reason it is this way may be simply due to a limitation in the Rich Text Field “type” itself. In which case I just think that should be remedied.