Background

We have introduced functionality to surface connected temporary accounts on Special:Contributions in order to help patrollers identify clusters of accounts operated by the same individual.

Now that patrollers can see related temporary accounts, the next logical step is to explore whether and how blocking workflows can support action on those connected accounts. Currently, patrollers must navigate to each account individually to apply blocks, which can be time-consuming and repetitive when multiple connected accounts require the same blocking action.

This epic explores the possibility of enabling patrollers to select connected temporary accounts and apply the same block parameters to them as part of a single workflow.

User story

As a patroller with TA IP access I I want to be able to select one or more connected temporary accounts when blocking a target account so that I can efficiently apply consistent blocking actions to accounts that are part of the same abusive cluster.

Acceptance criteria

• All tasks under this epic are completed