We are running into the issue that editors need to have the 'version administrator' role enabled in order for them to post to the default. However, this also makes it possible to edit in the default. https://enterprise.arcgis.com/en/portal/latest/administer/windows/roles.htm#GUID-49AAF916-F477-4D16-9898-E720B5970742
We always make sure to tell to our editors that they have to create a version, make edits and then post, but this is sometimes forgotten by mistake. This creates wrong data in the default version, which is not what we want. There is no time and effort available for one person to check all the editors work and post it, when disabling the version adminstrator role for all of the editors.
So my idea is to create a role that allows users to post to the default db, but disable them from editing on the default version. This will result in an a workflow where editors without version adminstator privileges cannot edit the default version by mistake, but does allow them to post their edits and thus make changes to the default db (with error checking off course). This also removes the need of one person that is responsible for posting (which just isn't workable in our office).