Collaboration limitations - more options?

Need help
1

I have been struggling with the lack of certain Bubble Collaboration limitations. It has been holding us back on working with Agencies and is now holding us back on using AI features.

Is there anyway to manage one of the following things in collaboration mode other than the limited settings available:

Deployment rights (generic): defining which users are allowed to deploy an app
Branch merge rights (generic): defining which users are allowed ti merge branches
Branch edit rights (limitation to edit a specific branch only): defining which branches can be seen/edited by users
App ownership transfer restrictions: defining who can transfer an app ownership.

I think there are a lot more. All would greatly improve app security/best practices and contribute to ringfencing the potential adverse impact of erroneous work by agents in the future.

There may be several more, but i would think implementing this would be very easy.
If there are clear workaround to manage this, sharing those would be highly appreciated!

Thanks

2

I believe if you aren’t marked as an Admin as a collaborator, then you can’t transfer the app. That whole screen part doesn’t show up. Branches aren’t restricted except not having access to the live branch if you restrict that. Besides what’s available there on that page, I don’t think there are any other secret options. Maybe suggest those ideas on the idea board for Bubble to look into implementing. :blush:

3

thanks, yes let me do that.

4

Found this one on the idea board, since it already had 3 votes it may go up a bit quicker :slight_smile:

2 Likes