Anthony

Thinking about this one more, it should be a backend change not a front end change.

I think we should do this change at the underlying form, and the templates should retain just a simple `{% form|crispy %}`. We can do this with JS if needed,...

At this point, I think that would be my suggestion as well. First, it probably only affects core team and maybe a few other users. But this would also make...

Hrm. This feels like a good place to just use an API interaction, it will be a bit hacky and awkward to create a mixed application logic/JS form like you're...

> Even people with 1 organization need to select the team. Yeah I understand, I also mentioned above that we can automatically skip this form for a number of cases....

> Could you describe the steps/wizard form for each of these cases clearly? I don't think we should have differing forms, fields, or UX for these use cases. We should...

> Do we want a field like this one? That is looking great. We can build on top of this later to communicate these are teams, show org SSO status,...

cc @humitos I don't know if we've fixed this yet or not

This is probably worth a separate issue, but I've noticed these build concurrency notifications on a number of builds too. Shouldn't these notifications clear after the build is successfully started?...

> Yes, I've mentioned this in 1) from my previous comment https://github.com/readthedocs/readthedocs.org/issues/11131#issuecomment-1956118651 That comment implied to me that the messages would only be _deduplicated_ with the fix -- ie: >...