Wikipedia:Requests for permissions/Autopatrolled/Administrator instructions

The autopatrolled (formerly autoreviewer) user right is intended to reduce the workload of new page patrollers. Articles that are created by accounts with the autopatrolled flag will be automatically set as patrolled by the MediaWiki software.

This user right does not require consent from the user before granting it to them. The right does not alter the interface for the user nor change they way they can edit, instead being entirely in the interest of the patrollers. If a particular user clearly meets the qualifications for autopatrolled, it is recommended that you grant the right so that we are not unnecessarily clogging the reviewing backlog with pages meeting inclusion criteria.

Prerequisites

In general, autopatrolled is only granted to trusted users who:

1. Regularly create articles
2. Have demonstrated they are familiar with Wikipedia's policies and guidelines, especially those on biographies of living persons, copyrights, verifiability and notability
3. Has created 25 articles, not including redirects or disambiguation pages
4. Have had an account for a reasonable amount of time. Autopatrolled is not normally given to brand-new editors, regardless of the number of articles created

In addition:

1. Autopatrol should not be granted to editors who have had any copyright issues in the last 12 months.
2. A sample of the editor's article creations should be checked and verified to be nearly perfect, including use of correct MOS formatting, categories, defaultsort, etc.

Tools to assist in evaluating a candidate's suitability:

• Σ's pages created tool
• xtools
• BLP edit counter

Responding to requests

Note if a request was recently declined for a given user/permission, a bot will comment with a link to that discussion. You may wish to ping the administrator who declined the previous request asking for their input before responding to the new request.

To grant the permission:

• Grant the user right(s) to the user at Special:UserRights. Indicate the request was approved at WP:PERM (or a specific page therein) in the "Reason", along with any other information you deem appropriate.
• Issue the corresponding notification template to the user for the permissions that were added:

Notification templates

Useful template notifications Template Permission {{subst:Account creator granted}} Account creator {{subst:Autopatrolled granted}} Autopatrolled {{subst:Edit filter helper granted}} Edit filter helper {{subst:Edit filter manager granted}} Edit filter manager {{subst:Event coordinator granted}} Event coordinator {{subst:File mover granted}} File mover {{subst:IP block exemption granted}} IP block exemption {{subst:Mass message sender granted}} Mass message sender {{subst:New Page Reviewer granted}} New page reviewer {{subst:Page mover granted}} Page mover {{subst:Pending changes reviewer granted}} Pending changes reviewer {{subst:Rollback granted 2}} Rollback {{subst:Rollback and reviewer granted}} Rollback and reviewer {{subst:Template editor granted}} Template editor

To respond to the request:

• On the permissions page, mark the request as approved or denied using {{done}} or {{not done}}. Include any relevant rationale for the decision. If you are revoking a permission, use the template {{revoked}} which will archive as done. If the user has withdrawn their request, you can mark it as {{withdrawn}} which will archive as not done. For some permissions, there is a convenient template for canned responses, such as with Confirmed and Rollback.
• 36 hours after the last comment was made (or whatever is specified in the config), a bot will automatically archive the request. You can force the bot to archive as soon as possible with the code {{User:MusikBot/archivenow}}

Helper script: The above process can be expedited using the script User:MusikAnimal/userRightsManager.js. Once installed, click "assign permissions" on any PERM page, enter optional closing remarks in the popup dialog, and the script will grant the right with a permalink to the discussion, and issue the corresponding talk page template.

To override where the bot archives, use {{User:MusikBot/override|d}} for approved, or {{User:MusikBot/override|nd}} for denied. This will override any other {{done}} or {{not done}} templates, and make the bot ignore the user's rights.

To re-open a request, deactivate the resolution template using the code {{tl|template name}}, as with {{done}} or {{not done}}. Strikethroughs like <s>{{done}}</s> or other means to suppress the original resolution template will still be registered as resolved by the bot. Only deactivating or removing the template will work.

Archiving

All requests are archived at Wikipedia:Requests for permissions/Archive as approved or denied. This is done as a historical reference, namely so that admins can review previously declined requests.

N hours after the last comment was made on a request (as specified by the bot's config), the discussion is removed from that page and an entry containing a PermaLink to the discussion is added to the archives, noting the user and the permission. This archiving process is fully automated and should not be attempted manually.

Bot clerking

For convenience, the requests for permissions pages are clerked by MusikBot. See User:MusikBot/PermClerk for more information on the tasks and how to configure them.