Automate user blocking/deactivation on GitLab.com

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Problem statement

In #7829 (closed), we explored solutions on automatically managing seat usage on self-managed instances. We should explore solutions for groups on GitLab.com, as the solution for self-managed will likely involve an administrator. Since the user attributes and process for managing/removing a user will be different, thus we should explore a separate solution.

Proposal

Consider how we might help GitLab.com group owners automatically manage the membership of their groups. Automated removal of idle members from a group is worth exploring. Other questions for exploration from @timnoah:

• What type of user is interested in managing GitLab.com group users in this way?
• What their current process looks like?
• How often are they performing these kinds of actions?

cc @esybrant