Having new joiners or externals on the app comes with the risk that they unintentionally or intentionally modify or delete branches.
Is there a way to restrict a user to specific branches or at least prevent him from deleting branches or are there any best practises to prevent that risk?
No, but they mention “Branch permissions: grant different access levels to project collaborators” at the bottom, in the “What’s next?” section on the new version control page: Introducing Bubble’s New Version Control
Still nothing. At the moment, any collaborator can basically screw up your MAIN version and you wouldn’t know; as there is no changelog and no restrictions on editing it.
+1 on this bigtime. I added it to the Bubble Ideaboard here:
Upvote that feature suggestion if you want to see this implemented.
This feature is essential for working with untrusted labor. I’m not even sure of a viable workaround short of exporting the app to a new instance and having untrusted labor work there then trying to port the changes across back into the original app… that breaks all the branching/merging utility though.