Bob, thanks for the reply. Honestly, I don't understand how meeting the needs of thousands of small organizations impedes meeting the needs of large organizations, and vice versa. I guess if developing an information system is viewed as a zero-sum game pitting small customers versus large ones, but I don't see it that way, and fortunately most other companies we work with don't either.
I don't really see bulk inviting 100 users as much of a workaround. Beyond the reasons that aewilson lays out, there are technical oddities with the current implementation. There appears to be no validation of e-mail addresses to see whether someone is already associated with our organization in My Esri. I guess getting an invite when you are already at the party is fine for the individual, but those invites tend to be ignored by users, which creates lots of chaff to sift through.
Another issue with invites in general, they don't appear to have an expiration. Although we can assign permissions with an expiration date, the invitation itself doesn't appear to have one, which leads to even more chaff.
What my organization is advocating for is a e-mail based verification and self-enrollment system. Similar to how other systems we engage with work, a user submits a request and provides his/her organizational e-mail address. A verification e-mail is sent to the user. Once the e-mail is verified, the profile is automatically enrolled with training permissions and a set expiration.
The auto enrollment wouldn't be perfect, but it would sure be a lot more enterprise than what exists now.
Also, why did the tokens for classes have to go away? Tokens may not have been perfect, but it seems one imperfect system was replaced by an equally or more imperfect one. Why not support tokens and organizational association?