Add the ability add multiple organizations | Voters

Add the ability add multiple organizations

planned

Lior Aharoni

Would be great if:

Each organization would have it's own subscription
It would be possible to transfer ownership of an organization

4 days ago

Support

marked this post as

planned

Support

Thank you Lior! Certain SaaS like Fresha don't have multi-organizations. In-fact most SaaS don't provide multi-organizations, but almost all popular ones do!
There is another ticket where Clerk support is requested. One advantage of Clerk is multi-organizations and Achromatic should definitely provide something in that regard. Furthermore as you mentioned there is some billing concern here. It's not only subscriptions, but also usage-based billing and potentially reporting. This week there are some Google Meet calls to see what models make sense to integrate in the boilerplate.
Additionally this would change how to access the organizationId. Right now we can do a simple session.user.organizationId which we cannot do once there are multiple organizations and memberships.
The implementation is planned for Q4 since there are some other things that take prio.

Lior Aharoni

Support Happy to help! Personally, I don't think the starter should include Clerk or any other paid authentication system by default. Solutions like Clerk and organization-based features can add costs, and if the aim is to support new startups, it's better not to depend on third-party authentication providers. It would be more beneficial to offer these as optional plugins, giving users a choice of multiple solutions, which makes more sense. The organization feature itself is fairly straightforward, so I don't see a strong reason for excluding it from the base starter and rely on 3rd party solution.

Support

Lior Aharoni: Thank you so much for your feedback! We don't plan to include Clerk. It's like you said a third-party dependency which isn't really needed. The multiple organizations feature is fairly easy, but affects the whole application. Before the change, we need to make sure that this is really requested (many B2B apps simply don't need it), that's why it's in Q4.