I see someone has asked one of my classics for low code (how to test it thoroughly) - I'll ask the other: how is change control managed? Can another person review a change, be it in behaviour or visual, in a diff, as well as running automated tests, before a change goes live?
Good question, these are definitely on our radar and very possible with how it's currently setup.
For us, we're trying to strike the balance of nocode and lowcode so a lot of the advanced features of version control and approval flows are not a priority for a lot of our users. I imagine this will change as we grow though
