Comment by sokoloff

I suspect nearly “any” solution is good enough to get started and learn what users use and like.

In my guessed-at ideal world, assuming the permissions setting isn’t complex, I’d like the ability for a user to define multiple teams and manage them with an easy method. Maybe that’s an API; maybe it’s a periodic ingest of a csv file. If you must have “admins” and “users” (rather than mostly users who can share teams they create), that will be an ok way to start, but I would bias towards “there are a tiny number of true admins but almost everyone is a user and users can share teams with other users”.

We’re very comfortable with storing config data like this in git and it would be great for tech teams to adjust team ownership by commit/pushing csv files, but that might not fit your actual user base (or the purchase-decision-making subset ;) )