Background

We have introduced functionality to surface connected temporary accounts to help patrollers detect abusive clusters more efficiently.

However, when patrollers decide that a cluster of related TAs should be blocked, they currently must apply blocks one account at a time through Special:Block. This requires repeatedly opening the block interface, selecting the same options, and submitting the block for each account individually. When clusters contain many related TAs, this process becomes slow and repetitive.

The goal of this task is to reduce that friction by allowing administrators to apply the same block to all related Temporary Accounts in a single action.

User story

As an patroller investigating abuse from a Temporary Account, I want to be able to apply the same block to all related TAs in one action, so that I can efficiently handle clusters of abusive accounts without repeating the same block process many times.

Design needs

• Design of the checkbox
• How does it look like for failed scenarios

Potential Solution

• On Special:Block, when an admin opens Special:Block for a Temporary Account, the page checks whether that TA has related temporary accounts
  • if yes, it shows a simple checkbox such as: [ ] Block all related temporary accounts
  • If selected, the same block parameters entered for the main target are applied to:
    • the target TA
    • all related TAs returned by the system
  • Patrollers configures the block only once: duration, reason, autoblock etc.

Things to consider

• How do we ensure patrollers investigate the accounts before the block is applied? Some ideas:
  • Add a warning/confirmation message: "You are about to apply the same block to x number of related accounts. Please confirm you have reviewed the accounts"
  • Add a link to Special:Contributions list of related accounts
• What happens if a TA in the list is already blocked?