I think I have read the full documentation and am still confused.
If I use GRIST_SINGLE_ORG=x then personal sites disappear, there are no more teams just one org with everyone in it. So this single org becomes the team and there is no creation of orgs or teams possible, just workspaces.
If I disable that variable, each user has a personal site, and I can create new team sites. But all of a sudden the term org has now disappeared. I see no option to create orgs. Not that I need any, I just want to understand the correlations. This makes it look like orgs are the same as teams?
So far I have figured out that a team is the same as a team site, right?
Yes “team sites” and “orgs” are used interchangeably. We try to standardize on calling them “team sites” but it is like herding cats.
A team could be a casual way to refer to a team site, or to the users with access to that team site.
Grist usually figures out which team site to show based on a slug or subdomain in the URL. “GRIST_SINGLE_ORG” tells it to ignore all that and just always assume a specific slug, and therefore a specific team site. In that case, it doesn’t make sense to show UI for creating team sites, since you’d never be able to view them. Likewise personal sites become unviewable.
Thanks Paul, I think I finally get it. The org=teams part was the confusing issue. I initially had the mental model of: ORG A, ORG B being used like a multi tenant setup and then each ORG would have different teams under that structure like: HR; IT and then each team would have workspaces.