My customer's customers

[cookegrahamg]

hi everyone. Am brand new to bubble but scratching my head on this one. I could be over-thinking it but I think it is a db design conundrum or it could be that I’m a bit ‘old school’ and just need to get my head round different ways of doing things.

I am not asking this question completely cold - I think it is is a similar problem to this one and this one. But i’m still not 100% clear.

In brief - i am struggling to visualise how my app will work for my customer’s customers. My idea is effectively a membership management app for clubs.
So the owners of clubs A, B & C will all subscribe to my SaaS product and they will be club owner user types. As they are club owners they will get an “admin login” to their instance of my SaaS and my expectation is that they will each want slightly different things for their users experience. When an owner logs into admin they will have the functionality to tailor the SaaS product to their club needs according to their subscription level.

My customer’s customers will just have club member user types and their logins will be linked to a specific club and club owner. When club members log in, they will only see the info related to their membership of their club and any other functionality the club owner designates. They won’t see info from every club that is subscribed to the SaaS product.

Is this functionality effectively native to SaaS and all encompassed in one DB instance? Is the db design challenge here to ensure that everything hangs off a unique ID for each club, and that is what ensure members of Club A will only see content set up by Owner of Club A for them?

In my head I was thinking this will only work with separate DB instances, but in the linked threads there was discussion about multi-tenanted SaaS apps being exactly what bubble is designed for. My assumption is therefore that what I want is all available ‘out of the box’ on bubble.

I was researching my idea and stumbled across Zeroqode and their templates and they have one built out for gyms which looks pretty close to what I was thinking. But it threw me as it seems to be built as a template for one gym, rather than as a template for a SaaS which could be rolled out to multiple gyms.

I hope this makes sense? Can someone just clarify my thinking that what I am trying to build is a good fit for bubble and achievable on the platform. If so is the template I found a good option to get me off to a flying start instead of build completely from scratch?

Any hints on whether I would likely need to consider a plan above starter would be super helpful.

Thanks in advance

[J805]

Hey @cookegrahamg

Welcome to the Bubble Community!

This is what Bubble does well. You can use one database, just make sure to set up privacy rules correctly.

I normally recommend building it out yourself, if you have the time and desire to learn. You will understand it much better that way and will gain a valuable skill at the same time.

I don’t have any template recommendations but you can at least download some free ones so you can get an idea about multi-tenant apps and how different developers go about building them.

Hope that helps a bit.

[zachary.bracken]

Hey @cookegrahamg

@J805 is right bubble is great for this kind of application. I have developed this kind of application for my current position. In our situation we actually go one layer deeper. We have a Distributor, Reseller and then the end customers. They all see something different.

My suggestion is build a little bit and play around with the DB. Then once you got the hang of that, really focus on how you want to manage your privacy rules as they are extremely important for an app like this.

There is also another solution if everyone of your customers (gym owners) needs a separate DB and that is to use the sub application feature. I forget what tier of bubble subscription you need to get this but check on that too.

This allows you to build an app like Zeroqode but then every time you sell it you create a sub app which is a copy of your main app but with it’s own DB. When you make changes to the main app you can push them to your sub-apps (customers).

Hope this helps! There is a lot of awesome things about bubble and it really is just learning how to apply traditional way of coding into this very flexible and fast way of developing.

[cookegrahamg]

much appreciated @J805 !

[cookegrahamg]

Thanks for taking the time to reply @zachary.bracken