I’m non-technical and spent most of my COVID time building a project-management application designed for use by companies with 5-50 employees. Currently, I’m using the PERSONAL subscription and found that I can only invite individual users to test on a single instance. I need to have 8-10 separate instances running in order to get the feedback I need.
$25 per month was a great price point to learn and explore, however, at $115 per month for the PROFESSIONAL version, I need to start being more deliberate about how I do things.
Has anyone made this kind of transition before and be willing to share their experience with me?
I’d greatly appreciate any and all feedback on this question.
I’ve definitely done this before lol. I was quite inexperienced with database handling just about 1 year ago and it caused a catastrophic issue… my site completely crashed because of the massive amount of traffic I was getting. So, I upgraded to professional and boosted capacity to try to keep the site as alive as possible while my colleague and I worked to fix it. The Bubble bill for that month was quite high, but got everything under control and learned an endless amount of lessons from that.
The only problem, currently, seems to be that I can’t create a separate instance for each user of our app on the PERSONAL plan? I believe we need to migrate over to the PROFESSIONAL plan in order to do that?
Establish a user role field via option sets (regular, admin as an example) and setup an organization field of type organization (first create a data type called organization). Both for the user data type.
Upon signup establish an organization and a role to each user.
This is one basic way of establishing a database structure to enable you to navigate and/or show content per user role and org.
You can now set conditions in various ways across your app to:
only allow an admin page loading to admin users
only show organization exclusive content if a current user’s organization is this page’s organization
Etc etc etc
The above is one of many way to go about establishing a structure to allow you to manage user’s access and visibility permissions. Bubble allows for a very sophisticated way of doing this including restricting what information is sent from the server to the browser to what user via privacy rules.
Thanks for getting back to me @cmarchan… Ok, that makes a lot of sense in terms of internal application organization. Yet, and I apologize for not being ‘technical’ in my analogy: It feels like I’m building a barracks that houses all my users together and not an apartment building that gives each one their own space.
