Multi-product B2B SaaS: should "organizations" be separate per product, or shared?
Hi all! We run two B2B products with different main user groups. Customers can adopt each product on its own. Login is unified under a single account.
Current setup
- One account signs in to both products.
- Both products share the same "organization" (company) and memberships (user, organization, role).
- Roles are owner / admin / member.
- Whether a user has signed up for a product is tracked by their acceptance of that product's terms.
Problems we're hitting
- Removing a member in one product also removes them from the other.
- Changing someone's role in one product also changes it in the other.
- There's no clean way to express "leave just this one product."
Options we're considering
1. Separate organizations per product. Each product has its own organizations, members, and roles.
2. Shared organizations, with a "product" column on memberships. Memberships become (user, organization, product, role).
3. Shared organizations and memberships, plus a separate "product access" layer. This is the organization → product access model used by tools like Atlassian or Google Workspace.
Questions
1. If you've built or run a multi-product B2B SaaS, which model did you choose? Looking back, are you happy with it?
2. Which hurt less over time: "start with separate organizations and group them under a company later," or "shared organizations with per-product permissions from day one"?
3. Did you keep one owner per organization, or one owner per product?
4. How did you separate "leave this product" from "delete my account"?
Any advice would be appreciated. Thanks!
Replies
Be the first to reply
Have a question or a thought to share? Add a comment above to start the conversation.