User:Valereee/Individual admin actions
This is a compilation of the administrative actions an individual administrator is authorized to take when dealing with editor behavior or issues at pages.
Standard admin actions
[edit]Administrators have the authority to do the following as an individual admin action when appropriate:
- block user accounts, IP addresses, and IP ranges from editing for a period of a few hours up to indefinitely,[a]
- partially block accounts, IP addresses, and IP ranges from individual pages or from namespaces,
- propose/accept unblock conditions for a user account that wasn't blocked as an AE, community, OS or CU action,
- unblock a user account that wasn't blocked as an AE, community, OS or CU action,
- unblock IP addresses and IP ranges,
- remove user talk page access,
- apply, modify, and remove page protection,
- delete pages; there is a technical limit for pages with over 5,000 revisions,[b]
- grant user permissions requested by user accounts[c] and revoke such permissions,
- restore deleted pages, and
- restrict and restore public visibility of information in individual logs and page revisions.
Any administrator may reverse such an admin action as an individual admin action, although consultation with the imposing admin, or at AN if the imposing admin is unavailable, is encouraged, and reversing a reversal is wheel-warring.
Contentious topics admin actions
[edit]At all CTOPs
[edit]Individual administrators are authorized to perform as contentious topic restrictions the following standard set of actions at all CTOPs:
Editors
[edit]- sitewide and partial blocks,
- topic bans and page bans (from the entire contentious topic, a subtopic, or specified pages within the topic),
- interaction bans,
- revert restrictions,
- issue logged CTOPs warnings, including to editors who had not previously been made aware,
Pages
[edit]- page protection,
- revert restrictions,
- the "consensus required" restriction,[d] and
- the "enforced BRD" restriction.[e]
In addition, admins may revert violations of 1RR, BRD, and consensus required at CTOPs as an admin action without becoming WP:INVOLVED. Admins working at AE may grant additional words to participants there.
Note: there are special conditions for an individual administrator to change a contentious topic restriction set by another individual administrator as a CTOPs action.
At designated CTOPs
[edit]Individual administrators are authorized to perform the following actions at designated CTOPs, all of which must be logged:
- set a CTOPs restriction as only appealable to ARCA,
- impose a balanced editing restriction,
- Impose talk page word limits
- extended-confirmed protect articles by default, and
- impose infobox probation.
Note: There are special conditions for an individual administrator to change a contentious topic restriction set by another individual administrator as CTOPs action.
Bespoke actions
[edit]Individual administrators are advised to use rough consensus of admins at AE to create bespoke versions of CTOP sanctions that otherwise would be authorized for individual admin use.
At non-CTOPs arbitration enforcement
[edit]Individual admins can enforce violations of non-CTOP arbcom remedies, but cannot as individual admins modify those sanctions without the explicit prior affirmative consent of the enforcing admin.
Individual administrators are authorized to impose for up to one year the following actions:
Individual restrictions
[edit][edit source | copy]
- sitewide and partial blocks,
- topic bans and page bans (from the entire contentious topic, a subtopic, or specified pages within the topic),
- interaction bans,
- revert restrictions,
- word limits per discussion,
- the "balanced editing" restriction
Page restrictions
[edit][edit source | copy]
- page protection,
- revert restrictions,
- the "consensus required" restriction,
- the "enforced BRD" restriction,
- word limits for all participants in a specific discussion
Individual admins can also require a sanction they've imposed under ARBPIA5 to be appealed only to ARCA.
Policy that could be confusing
[edit]- Information at Wikipedia:Arbitration_Committee/Procedures#Standard_provision:_enforcement_of_restrictions does not apply to individual admins (orto the AE noticeboard) but rather to ARCA.
- While blocks and page protection are part of the standard admin toolset, these restrictions are also included in the list of CTOPs restrictions because imposing them as a CTOPs action places them under the CTOPs appeals/reversal procedures.
- ARBPIA5, a non-CTOP ArbCom case, has different provisions, remedies, appeals process, and logging requirements than Arab-Israeli conflict, which is a designated CTOP.
- Arbitration Enforcement Noticeboard (commonly called AE) handles both CTOPs and non-CTOPs arbitration enforcement, but there are differences between an AE action (arbitration enforcement action) and a CTOPs action, either of which can be performed by an individual admin.
See also
[edit]Notes
[edit]- ^ These blocks can disallow editing of certain pages or namespaces, or be applied sitewide.
- ^ Pages with more than 5000 revisions can only be deleted by a steward.
- ^ Administrators are able to grant and revoke the account creator, autopatrolled, confirmed, edit filter helper, edit filter manager, event coordinator, extended confirmed, file mover, IP block exempt, mass message sender, new page reviewer, page mover, pending changes reviewer, rollback, template editor, and AutoWikiBrowser access user rights.
- ^ On pages where "consensus required" is in effect, an edit that is challenged by reversion may not be reinstated without affirmative consensus on the talk page.
- ^ On pages where "enforced BRD" is in effect, an edit that is challenged by reversion may not be reinstated by the editor who originally made it until the editor (a) posts a talk page message discussing the edit and (b) waits 24 hours from the time of the talk page message.