Wikipedia:Requests for permissions/New page reviewer/Administrator instructions

New page reviewer is a user group that allows users to patrol pages. NPRs work with the New Pages Feed and the Page Curation tool to process, approve, or tag newly created pages.

Prerequisites

The New page reviewer user right is granted by administrators. Administrators use their own discretionary assessment of an editor's contributions as well as the following general guidelines:

Generally speaking, editors granted new page reviewer should:

1. Have been a registered user for at least 90 days with at least 500 undeleted mainspace edits
2. Have a good knowledge of content policies and guidelines and experience with quality control processes. This is typically demonstrated by prior participation in one or a combination of the following areas:
   • The deletion processes, i.e. AfD, PROD, and CSD
   • Articles for Creation
   • Writing new articles
3. Have a solid track record of interacting with other editors, especially new editors, in a civil and constructive manner
4. Have no behavioral blocks or 3RR violations that were active within the last 6 months
5. Commit to reviewing pages solely on a volunteer basis

These criteria are guidelines; meeting them does not constitute a right to the permission. At their discretion, administrators may grant the permission to editors who do not meet the strict criteria but that they otherwise deem to be competent, or may ask for additional experience. Typically, consistent recent activity is required, to ensure that reviewers are familiar with current policy and guidelines. Activity on other Wikimedia projects is not taken into consideration.

See the October 2016 RfC for more information.

Tools that may assist in evaluating the candidate's suitability:

• xtools
• Non-automated contributions
• BLP contributions
• NPP patroller info - to see patrols prior to when the user group was introduced

Other things to check

In addition to checking if the user meets the prerequisites, when granting new page patroller you are encouraged to check the candidate's...

• User talk page for suitable style of communication.
• User page for inappropriate content.
• Article creations for possible COI.
• Experience with article deletion
• Block log
• Perm log (to see if the permission has ever been revoked or expired)

Also...

• Consider requesting the candidate to state whether or not they have actually read the required tutorial.
• Consider granting the permission for a limited amount of time on a trial basis, or encourage inexperienced editors with good communication skills to sign up for instruction at WP:New pages patrol/School.
• Check for hat collecting behavior, especially at autopatrol and AfC
• Let valid requests sit open for a few days, to give others time to comment

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: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.