meaning BWT owners will need to individually set the team's admin(s) on our web site, and any other project's Web site.
Correct, as I said, it's a kluge. I think this comes down to the fact that admins (like members below) have to exist at any given project and BTWs themselves can't ensure that the way they're implemented.
Request foundership - There is no check for BWT, and there probably should be. Likewise, the set foundership function has no check.
I think this is most glaring omission as the owner/founder is definitely set upstream and shouldn't be modified locally.
Remove Member - There is no check for BWT, owner/admin could remove a team member. Presumably this will be updated upon next team import, and the team member will be 'undeleted'.
Hm, I don't think BWTs have any members upstream. I mean they can't since they require local users. So this should be fine.
Delete team - There is no check for BWT , owner may delete the team. Presumably this will be updated upon next team import and the team will be re-imported.
That's correct I think. OTOH, this is an easy way to remove all admins and members from a team. So we should probably keep it that way.
Bottom line: BWTs are about the teams themselves, i.e. the "container" not the "content".