For example, say Alice works for Acme, and she signs up for Jira. She is now the admin, so puts the credit card in to upgrade the account, and then invites her colleagues.
Is Acme an "organization" in terms of PropelAuth? Organizations sound looser and more user defined, almost more like a Gmail group of users than a "company".
In your example, some people have implemented it as Acme is the organization, and some people have implemented it as specific teams within Acme are an organization.
I suspect we'll need to add a second tier (e.g. a team or a group) underneath a more rigid definition of a company. Would that have made things more clear?
Also, hey, I'm Adam, a very happy customer of PropelAuth at Kable.io. Andrew is an incredibly responsive founder, who has been a great partner in the launch of our own B2B business. High recommend from me -- PropelAuth rules
We're currently integrating Auth0 for authentication but sticking to our own authorization stuff. Auth0 organizations seem way heavier than what we need, more for like white-labeling an app to a handful of huge enterprise clients, rather than just having lots of small clients with a handful of users each.
We had similar feelings about Auth0's org implementation, it doesn't really match the way most companies think about orgs, especially at an early stage.