Has anyone written something great about how to model your Rails-based SaaS app with Users, Teams, Organizations, and Subscriptions so that you don't regret it later?
-
-
One promising-looking approach:https://www.firehydrant.io/blog/how-firehydrant-creates-data-in-rails/ …
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
I’m not sure I understand the need for the “team” concept for tuple, unless it’s about enabling segregation of users within an org? Do you want users in different teams not to be able to see each other?
-
The team is a collection of users who can see each other online and do calls. It also owns the subscription, so it pays for all the team members.
- Još 5 drugih odgovora
Novi razgovor -
-
-
I have feelings about this but I’m not sure I can fit them all into Twitter. Maybe we should Tuple.

-
Blog post! :)
- Još 8 drugih odgovora
Novi razgovor -
-
-
Let people have multiple email addresses. You’ll want it eventually
-
Really? How come?
- Još 2 druga odgovora
Novi razgovor -
-
-
In the http://JumpstartRails.com template, Account/Org is the main model, every user has a personal Account private to them, then can create other Accounts to share with their team. Invitation for the email invite, then creates an AccountUser when they accept.
-
Every resource gets attached to an account, you can transfer the resource between accounts, and account can easily work for multitenancy by domain, subdomain, script path (like basecamp does).
- Još 2 druga odgovora
Novi razgovor -
-
-
You may want to draw some ancient wisdom from the Party Data Model.
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.