Wikipedia:Requests for permissions/Header

Bot report:

Handled here

 * Account creator : The account creator flag is granted to users who are active in the request an account process. The flag removes the limit on the maximum number of new accounts that can be created in a 24 hour period. It also allows users to make accounts with names similar to other accounts. The account creator flag is only given to users who participate in the ACC process and may be removed without notice should a user's participation in the account creation process cease.
 * Autopatrolled : The autopatrolled flag is granted to users who are active in the creation of new articles. This tool is granted so their creations are auto patrolled in Special:NewPages. Unlike other requests, any user may nominate an editor for Autopatrolled, even without that user's consent. A user who wishes to have this flag generally should have created at least  articles and must be trusted, experienced, and must have demonstrated they are familiar with Wikipedia's policies and guidelines, especially WP:BLP and Notability.
 * AutoWikiBrowser : AutoWikiBrowser is a semi-automated MediaWiki editor for Microsoft Windows, designed to make tedious repetitive tasks quicker and easier. It is essentially a browser that automatically opens up a new page when the last is saved. When set to do so, it suggests some changes (typically formatting) that are generally meant to be incidental to the main change. Please read the rules of use and registration requirements on the main page before requesting permission. This is not a true user right, but access needs to be granted by administrators just like other permissions. If approved, your name will be added to the CheckPage. Users with under  non-automated mainspace edits or  total mainspace edits are rarely approved. You will need to give a reason for wanting AWB access.
 * Confirmed : The confirmed flag may be granted to new users who have not yet hit the threshold for autoconfirmed status. These are users who have not had both 10 edits and 4 days experience. People with this flag can  upload files and edit semi-protected pages before hitting the autoconfirmed flag. Users requesting this flag must indicate clearly why they should be exempted from the customary confirmation period.
 * Event coordinator : The event coordinator user right allows editors to create multiple new accounts, and to temporarily confirm accounts so that they can create new articles.
 * Extended confirmed : The extended confirmed flag is normally automatically added to accounts after 500 edits and 30 days, but may be added to legitimate alternate accounts of users that already have this access. The flag allows users to edit pages under extended confirmed protection.
 * File mover : The file mover user right is intended to allow users experienced in working with files to rename them, subject to policy, with the ease that autoconfirmed users already enjoy when renaming Wikipedia articles.
 * Mass message sender : Mass message sender enables users to send messages to multiple users at once. This flag is given to users who have made requests for delivery in the past, clearly showing an understanding of the guidance for use.
 * New page reviewer : The new page reviewer user right allows users to mark pages as patrolled and use the page curation toolbar. At administrators' discretion, the right may be accorded on a time limited basis or indefinite.
 * Page mover : The page mover user right allows users experienced in working with article names to move them, subject to policy, without leaving behind a redirect. They may also move all subpages when moving the parent page(s). General guidelines include making 3,000 edits and 6 months of editing history. At administrators' discretion, the right may be accorded on a time limited basis or indefinite.
 * Pending changes reviewer : The reviewer flag is granted to users who are experienced enough with Wikipedia editing and its policies for contributing to the process of reviewing articles placed under pending changes.
 * Rollback : Rollback enables users to remove vandalism much more quickly and efficiently than by undoing it. Users who do not demonstrate an understanding of what constitutes capable vandalism fighting, either because they have no or little history of doing so, or show a poor ability to discern between good and bad faith edits will not be granted this right. Also, it is unlikely that editors with under  mainspace edits will have their request granted. For a more detailed explanation of rollback and information about when it is appropriate to use the tool, see Rollback. For information about the technical details of the feature, see here.
 * Template editor : The template editor flag allows users to edit protected templates and Lua modules. General guidelines for granting include making at least 1,000 edits overall (with at least 150 to templates or modules), being a registered user for over a year, and having a record of successfully proposing significant edits to several protected templates. Users should demonstrate proficiency with template syntax and an understanding of the need for caution when editing heavily-used templates.

Handled elsewhere
Several permissions are requested and handled elsewhere:


 * Administrator and bureaucrat access: Requests for administrator or bureaucrat access need to be posted at requests for adminship and requests for bureaucratship, respectively.
 * Bots: Request for bot flags should be made at Bots/Requests for approval.
 * Edit filter: Requests for access to the edit filter manager group and the edit filter helper group should be made at Edit filter noticeboard.
 * Interface administrator: Requests for interface administrator access should be made at Bureaucrats' noticeboard. Only current administrators may become interface administrators.
 * IP-block-exempt: While the IP-block-exempt right can be granted by administrators, this flag is not handled here. Requests for the IP-block exempt right should be submitted via the Unblock Ticket Request System or, if there are significant privacy concerns, email the checkuser team at or contact a CheckUser directly.
 * CheckUser and Oversight: These rights are only granted by the Arbitration Committee, and only after strict scrutiny. More information can be found here.
 * AfC reviewer: This access is granted by administrators at Wikipedia talk:WikiProject Articles for creation/Participants.
 * Redirect autopatrol list: Addition to the list is granted by administrators at Wikipedia talk:New pages patrol/Redirect autopatrol list.
 * Steward permissions can only be granted in yearly elections, and are rarely given.
 * Global permissions such as global renamer, sysop, IP block exempt, rollback, etc should be made at Steward requests/Global permissions.

Removal of permissions
If you wish to have any of your permission flags (except administrator) removed, you should contact an administrator. If you want your administrator flag removed, you should contact a bureaucrat.

This is not the place to request review of another user's rights. If you believe someone's actions merit removal of a permission flag, you should raise your concern at the incidents noticeboard.

The bureaucrat, checkuser, and oversight flags are removed at meta:Steward requests/Permissions. Stewards will typically not carry out such requests unless they are made on behalf of the Arbitration Committee, by a user who is requesting their own access be removed, or in cases of an emergency.

Requestors
To make a request for a permission, click "add request" next to the appropriate header and fill in the reason for wanting permission.

Any editor may comment on requests for permission.

Administrators
Administrators are permitted to grant account creator, autopatrolled, confirmed, event coordinator, file mover, mass message sender, new page reviewer, page mover, pending changes reviewer, rollback and template editor flags to any user who meets the criteria explained above and can be trusted not to abuse the tool(s). Administrators may either grant these permissions permanently or temporarily. For convenience, a bot will automatically comment with relevant data if the user does not meet configurable qualifications. Even if the bot does not comment, administrators should review the user's contributions and logs to ensure the tools will be used appropriately and check for any indication of potential misuse.

Once an administrator has granted a permission or decided to deny a request, they should add done or not done respectively under the request with their comments. If a user already has the requested permission, or is autoconfirmed and requesting confirmed, already done should be used. N hours after the last comment was made (as specified by the config), the request will be archived automatically: approved requests will be placed here; declined requests will go here. See User:MusikBot/PermClerk for more information on archiving functionality.

Other editors
Requests for permissions is primarily intended for editors requesting a permission for their own account. Other editors are welcome to comment if they have specific information that is relevant to that request that a patrolling administrator is unlikely to discover for themselves. Otherwise, since only administrators can effectively respond to these requests, general comments or 'clerking' by other users are rarely helpful. Non-administrators cannot "decline" to grant a request, because they're not in a position to accept it.

A limited exception to this is Requests for permissions/Autopatrolled, where third party nominations are encouraged. Other editors should still avoid offering general remarks on requests and leave the final decision to an administrator.