Add ability for organziations to manage/approve contributors(employees)

We have already had one incident where an organization asserts that a user utilized the organizations name without approval. The user was reportedly still undergoing on-boarding and had not passed through the control gate to be considered approved to post on D.O. using the companies name.

If I’m reading that correctly, the person was saying they are working on behalf of the organization truthfully. That sounds like a feature.

The proposed resolution is over-complicated. There is a common-enough use case that would be good to support - when someone leaves an organization, they don’t always update their profile. It would be good for organization owners to have a way to remove people without needing a support request.

https://drupal.slack.com/archives/C0451JV7HRD/p1700231774258499 is the relevant Slack thread for this.

The short version is that the user was hired and started posting on issues against the current D.O. using the companies name with an account they had created at a previous employer.

If I’m reading that correctly, the person was saying they are working on behalf of the organization truthfully. That sounds like a feature.

As far as the new organization was concerned it is my understanding the user wasn't authorized to post yet and was not suppose to be making contributions on D.O at all. In other words they were essentialy not yet working on behalf of the organization even though they claimed they were.

Reportedly this is an edge case that user reportedly already had an account from a previous organization (it looks like it might be an org we have had issues with on D.O. in the past that would benefit from remedial training) and just jumped in with less than ideal behavior without hitting the employers checkpoint of 'you have now been trained to post on D.O. you may not begin"

The original request involves allowing organizations the ability to catch employees that may be acting outside of the training guidelines before they create a situation that requires the D.O. Moderators, Contrb Project Maintainers, or the DA have to expend time and effort on disciplinary matters, which was part of the goal of the credit farming punishments targeting the organization not the individual user.

The original request would make D.O. more like GitHub, where you have to be approved into an organization rather than self attesting.

There is certainly room to question if the Organization could have done something different to ensure the employee didn't try and jump straight into creating issues on D.O. just as there is room to question why we don't provide the tools to know when a new user joins an organization.

What @drumm said... there's already a much more common user case for an organisation having more control over who is listed as being associated with them. At my previous place, about half the people listed no longer work there. Org owners should have the ability to remove people from their organisation at the very least.