Wikipedia:Requests for permissions/Account creator/Administrator instructions

The accountcreator user group allows a user to bypass MediaWiki account creation throttles, as bots and administrators can, to create accounts for other users without restriction. Without receiving accountcreator access, a user may only create 6 accounts per day from the same IP, and are subject to anti-spoofing and blacklist checks against chosen usernames.

It is granted to users who are active in the account request process (ACC). Procedures for granting and revoking the right differ for each scenario.

For a guide on how to assign user rights in general, see Wikipedia:Administrators' guide/Granting and revoking user rights.

Prerequisites

Account creation team

If the user is requesting the right for the request an account process:

1. Carry out general checks such as the user's contributions, talk page, block log and so on. Ensure that they can be trusted - users with the account creator right are able to ignore spoofing checks, throttle limits and most importantly the username and title blacklist.
2. Confirm that the editor is active in the request an account process (which will also confirm that they are identified), by selecting their username from the list at accounts.wmflabs.org
3. Check the account creation log to see how they would use the extra abilities. Please make sure the accounts created by the user adhere to the username policy.
4. Check with one of the Account Creation Tool admins, listed here, either by emailing one of them directly or by emailing the tool admins at enwiki-acc-adminsgooglegroups.com. This is very important because the ACC tool admins will be aware of the user's involvement in the process. This includes things which, if you don't have an ACC interface tool account, you don't have access to view.

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.