Wikipedia:Request an account/Guide

From Wikipedia, the free encyclopedia
Jump to: navigation, search

The Account Creation Interface is an application software that is used to facilitate account creation requests on the English Wikipedia. It is hosted on Wikimedia Labs. This guide describes accepted practices in handling requests that are submitted to the tool. Users who wish to participate in this process must apply for access pursuant to the required qualifications that are listed in this guide. New interface users should read this page thoroughly and experienced users should periodically check for updates.

Registering for use[edit]

To use the interface to handle requests, you must register here and complete your registration by leaving a signed edit with a link to your identification diff from the Identification noticeboard on your Wikipedia user talk page confirming that you wish to sign up. Your account must be approved by a tool administrator and if approved, you will receive a notice usually on your talk page. If you are declined, you will receive an email explaining why.

Notes, terminology, and requirements[edit]

  • Interface administrators (herein referred to as tool administrators or administrators) are not the same as Wikipedia administrators (herein referred to as sysops). Most Wikipedia sysops are not tool administrators.
  • Tool accounts unused for 45 days will likely be suspended. Contact a tool admin to regain access.
  • Despite the similar names, you do not need the "account creator" right to use the account creation interface. This is an entirely separate permission from being granted access to the interface itself. Your rights as a regular Wikipedia editor are sufficient to create accounts in normal situations. After gaining experience using the account creation interface, you may wish to apply for the "account creator" right which lets you handle more complex cases and override certain limits.

Qualifications for using the interface[edit]

To qualify as an ACC user, you must meet the following minimum requirements:

  • You MUST be identified to the Wikimedia Foundation before access to the interface is granted
  • You have a clean block log or if you have had a block it must not be recently placed (preferably not within 6+ months, depending on length of block)[note 1]
  • You need a valid email address that you actively watch. (Signup: here) Tool policy change notices are sent out this way, and you are responsible for keeping up with them. [note 2]
  • You have no history of abuse. Users with a history of account-related abuse — such as sockpuppetry — will be denied access to the tool
  • You have no active or recent editing restrictions or had disciplinary action enacted upon yourself, such as Arbitration Committee sanctions and editing restrictions
  • You MUST have read, understood and agreed with the ACC guidelines
  • Your account on Wikipedia must be at least 6 months old and have at least 1500 edits.[note 3]
  • You have a solid grasp of Wikipedia's policies and guidelines and show yourself to be a knowledgeable user
  • You have a clear understanding of and agree to abide by the Wikimedia Foundation's privacy policy
  • You need to be able to accept/acknowledge constructive criticism
  • You must only use one account and not apply for a new one.
  • You need to wait a reasonable amount of time before appealing an account decline or suspension decision. Also excessive appeal requests without taking enough time to properly consider and address the original deny reason will not be considered.
  • You must connect your account to your Wikipedia account during signup.[note 4]

This list is not exhaustive, but are the primary reasons tool admins consider when looking at a request for an account.

Finally, the acceptance of requests are subject to the opinions of tool administrators based on the demonstrated trustworthiness, competence of the candidate, and the apparent need for more users.

Interface documentation[edit]

After logging in, you will see the main interface — see screenshot below — which displays a list of open requests, requests needing account creator attention, a list of requests needing CheckUser attention, and a list of the last five closed requests. After you mark a request as being handled, each open request or request needing account creator attention or CheckUser attention will have a string of links, like this:

Zoom (CMT) [ (2) | (100) ] WikipediaAccount | Ban: IP — E-Mail — Name

Please remember that account creating is not a race! The requests that end up in the ACC interface are accounts which couldn't have been created under normal circumstances. Please keep this in mind and react thoughtfully. It happens sometimes that one is in the middle of a situation and one doesn't know what action to take. Just ask in the ACC IRC Channel for help in situations such as these: #wikipedia-en-accounts connect. There are always other interface users online who are willing to assist you. In case you do not get a satisfactory response, and do not know which course to undertake, it is better to defer the request to other users rather than to undertake a wrong course of action. If you ask for help, you will need to provide (to non-admin users) the link shown on the 'zoom' page to the other user to allow them to see the private data.

Please note: If you seem to 'rush' through a request (for example, by not performing all the checks listed below), you may lose access to the tool. It is essential that all the checks are performed to ensure that accounts are correctly created or declined.

Using the tool[edit]

Personally identifying information[edit]

  • The ACC tool contains personally identifying information and is subject to the privacy policy. It can not be shared outside of the interface. Users who do violate this rule, risk indefinite suspension, and possibility of their identified status being revoked. Please see this email for more details.
  • Users may not post personally identifying information in the comments of a request; that would not be following the Data retention policy. For example but not limited to: IP addresses, email addresses, real names, and excessive information about a block that could allow the IP to be found in the block log. Any violations of this rule will result in suspensions. See this email for more information.


  • If you reserve a request and then need to go offline without completing the request, please break the reservation beforehand, so that another user can complete the request, unless you have good reason to require the request to be handled by yourself, in which case you must leave a comment. If you do not do this, the request will remain reserved and cannot be created by other users; a tool admin may forcefully break the reservation if you have left no indication as to why you need to keep the request reserved.

Script usage[edit]

  • Using a script or other program to automatically handle requests in any way (includes reserving) is not taken lightly and will probably result in account suspension. Using an automated refresher, however, is generally OK, as long as the refresh time is considerate to the instance's resources (at most once a minute). Remember there is a live feed of requests on IRC, this may be a better place to watch than the interface.

IP blocks and IP rangeblocks[edit]

Please see this email sent to the mailing list which details what to do with requests affected by active blocks.

Please keep these points in mind when dealing with ALL requests made from ANY kind blocked IP address or rangeblock:

  • If there are checkuser-related reasons for the block, you must defer the request to CheckUsers.
  • If you are uncomfortable or uncertain with any request, the safest choice is to defer the request to CheckUsers.
  • Even after noticing that a request is from a blocked IP address or rangeblock, you should run the other checks. If there are other reasons that would warrant a request from a block IP request, such as a username policy violation, or similar username, then you should decline the request for that reason.

When deferring a request to CheckUsers, please include a brief statement on the reason for deferral. This is especially true if you are ignoring part of the guide (such as deferring an older schoolblock). In this case, you must tell the CheckUsers why you are deferring the request. Examples of deferral reasons include:

  • "single IP anonblock"
  • "rangeblock for long term abuse"
  • "similar account blocked for sockpuppetry"
  • "see IP's talk page"
  • "A number of previous blocks for sockpuppetry".

Do not leave a comment that could allow someone to determine the IP (range) from the Wikipedia block log. This includes blocking administrator usernames, exact dates, or usernames as part of block reason. This is be considered to be releasing personally identifying information and be dealt with accordingly.

Open or anonymizing proxies, web hosts and Tor exit nodes, that is blocks with {{blockedproxy}}, {{webhostblock}}, {{Colocationwebhost}} or {{zombie proxy}} as the reason should be deferred to the proxy check queue unless you are capable of confirming that the block reason is still valid yourself. If the request's IP is confirmed to be an open proxy, the request should be closed as "Open Proxy". If there is strong reason to believe that the IP is no longer an open proxy or web host a request should be made at WP:OP for the IP to be checked. Before making a request at WP:OP you should seek advice from an experienced ACC team member. Be extremely careful not to link the request at WP:OP to the ACC request as this would breach our privacy requirements and may get you suspended.

IP range blocks[edit]

These are blocks that affect a range of IP addresses, rather than just one. This is typically done to partially or completely block networks that can operate using than one Public IP address. If there is ANY rangeblock on the requesting IP (or any indication of sockpuppetry), defer the request to CheckUsers. Users creating accounts in such cases without consulting a CheckUser will be suspended.

Exceptions to this policy:

  • You placed the block yourself, and you are sure the requester is not the block target.
  • The rangeblocks is placed on an Opera Mini IP range, and solely because of the fact that it is an Opera Mini IP range.
  • Blocks that expressly ask ACC users to ignore the block.
  • Rangeblocks affecting schools (see blocks affecting schools below).
  • Blocks that do not have the "account creation disabled" parameter set.

Single IP blocks[edit]

These are blocks that are made to a single IP address, and is commonly done to block single users (such as a residence or network with one public IP address).

  • If the blocked IP is a {{schoolblock}}, refer to blocks affecting schools below.
  • If you believe that the IP address is static, then you should defer the request to CheckUsers (if the block is older than 1 week).
  • If you have a request that you are going to decline or drop due to a single IP block, you need:
    • To be 100% sure that you are correct that this is the only person on the IP (using tools such as to find out if the IP is static or not is not sufficient on its own to determine this).
    • Approval from a CheckUser or tool admin (except where there is sockpuppetry involved) which is documented on the tool, before you carry out any action.
    • If you do not have either of these, then defer it to CU, even if it's already been there.

If you attempt to verify attributes of an IP address such as if it is shared, an open proxy, etc. on your own, you take full responsibility for your actions. If you make incorrect decisions without contacting a CheckUser first, you may be warned or suspended by a tool admin.

Blocks affecting schools[edit]

Single IP blocks or rangeblocks affecting schools can be ignored only if both are found to be true:

  • The block is an {{anonblock}}, a {{schoolblock}}, or due to vandalism, and
  • the block was applied to the IP longer than one week ago.

If both of the above requirements are true, then the request is likely due to a block that was not caused by the requester, and in this case, WP:AGF would apply. Otherwise, refer the case to CheckUsers.

Real names relating to famous, popular, etc. persons[edit]

  • Where the requested username is a real name relating to famous, popular, etc. person the requester's identity needs to verified through the OTRS system. The standard in the username policy is that the name or nickname has to relate to a "specific, identifiable" person. In terms of a test for ACC they should be notable enough to have a Wikipedia article; however, having an article doesn't necessarily mean that they are specific and identifiable and that there is a likelihood that someone is trying to impersonate them. If you believe that they are specific and identifiable and that them having the name may cause confusion, you will need to close the request as "Notable Person". If you aren't sure whether the above test is met, consult with a tool admin or experienced user, it is better to create the account in good faith (remembering that they can be blocked) then to send it to OTRS to deal with.

Promotional usernames[edit]

  • Requested usernames should only be declined as a username policy violation where it is clear that they are - remember to assume good faith. If you are in doubt, create the account and watch it, if it is engaging in promotional editing report to WP:UAA (as you would with any other promotional username and editing).

Checking for multiple requests[edit]

  • You should check for multiple requests from an IP address or an E-Mail address. To do so, click the Zoom button next to an open request or click the requested username in the list of last 5 closed requests, or go to the logs—see below and click a request number. At the end of the request line—like you see normally for all open requests, you will see the UTC date and time the request was submitted. Farther down the page you would also see a list of other requests—if any, from that IP address or E-Mail address. If there are multiple requests that are clearly from the same user, please ban the offender from sending requests to the tool. Please keep in mind that shared IP addresses are common. If you have multiple requests from the same IP address and the IP is static, defer to checkusers, if it's dynamic, assume good faith and create.


  • There is a bug which happens while creating an account: The SUL account is created, although it is not listed at the SUL util nor at Hersfold's Fake SUL tool. Please use Special:CentralAuth to check if the SUL account was created, but no local account. In this case leave a comment on the request explaining the situation and defer the request to on hold. The SUL account will delete itself after 24-48 hours and the account may be created.

Messages outside of the interface[edit]

  • If you need to make any form of a comment or question to the requester, either use the "Custom Close" button if you are immediately closing and need to explain something or email the user directly if you want the user to be able to respond to clarify something before you decide on how to close the request.
  • Make sure you carbon copy (CC) the mailing list on all emails related to ACC. If you believe the email should not be sent to the ACC mailing list, or if it relates to the actions of tool users, you should carbon copy it to the tool administrators' mailing list,
  • The mailing lists and IRC channel are relatively secure so personally identifying information may be discussed there. However, exercise good practice, if you don't need to share it don't - linking to a request is a good way to avoid discussing IP addresses and emails without naming them.
  • Releasing any kind of private information supplied from the ACC tool, the ACC or admins' mailing list, or the ACC or admins' IRC channel outside of those places is an extremely serious violation and will result in an indefinite suspension. Also, the Foundation takes the tool as serious as they do with the checkuser tool, as our interface contains similar data available to tool users. Breaching this rule may result in the loss of identified status at meta and the inability to identify in the future. See this email for more information.

General notes[edit]

  • If the exact wording of the documentation prevents you from creating an account that you feel should be created, ignore it and leave a comment explaining why.
  • If your check of the "Creation log" shows that the user created the account themselves, just drop the request, as they don't need to be confused with any of our other messages. Please leave a comment saying they created the account themselves, so that other users know why you dropped the request.
  • The requesting user can not see any comments left in the request itself, all comments there will only be viewable by other tool users (or only administrators if you choose to mark the comment as "Admin Only"). Also see "personally identifying information" at the top of this section.
  • Please note on creates where there are no issues with the request such as vandalism, similar names, etc. there is no need to leave a comment like "Everything looks good with this request.".
  • If there is a comment on the request asking for, or suggesting, an action and you wish to do something different you must justify this in another comment. If the comment is from a tool admin or CheckUser acting in that position there must be another comment from a tool admin or CheckUser respectively authorizing you to ignore it. Discussion on IRC is not an excuse, it must be documented on the tool.

Creating accounts[edit]

  • Once you have reserved a request as above, and decided that the account should be created, click the Create! link next to the desired username. This will bring you to the MediaWiki account creation form. The name and email will be filled in automatically. Do not type in a password manually—simply click the By Email button and a randomly-generated one will be emailed to the user. If the By Email button isn't visible next to the Create Account button, you may need to login. If a message appears - stating the username is forbidden (example here), defer the request to an account creator who can override the MediaWiki:Titleblacklist. If you do accidentally type in a password and click Create Account, go to Special:Userlogin, type in the username and click Email new password. This will reveal your IP to the requester, so try to avoid doing this. Once the account has been created, click Created! next to the request on the ACC tool.

Custom closes[edit]

  • All custom closes should end with an Email signature. It is recommended that you add this to your preferences so it is automatically appended to any request closures you perform. If you do not, then you must add your signature at the end of your message every time you custom close a request.

Similar account names ("Flagged user needed")[edit]

Similar account flowchart

Sometimes, Wikipedia will not allow you to create an account if the requested user name is (a) a perfect match of an existing global account or (b) too similar to an existing local account.

Perfect match[edit]

  • A perfect match is when the user name (including casing) is identical. If the requested account has a different casing (Apple versus APPLE), then defer to Too similar below.
  • As all user accounts are (becoming) globally unique, if the name exists on another wiki or in SUL already, don't create the account and close the request as "Taken". (SUL taken and Similar may have to be reworded to reflect this change)

Too similar[edit]

In case of accounts that are 'too similar' to existing accounts, only ACC tool users with the account creator flag are able to create the account - only if the account the request is too similar to is inactive. ACC tool users without the account creator flag, though not allowed to create the too similar account requests, are allowed to decline requests (Similar, Taken, UPolicy...).

Inactive accounts are determined by the following qualities:

  • If the similar account has any edits on the English Wikipedia, then for it to be considered inactive, it must:
  • Have been created over one year ago. (accounts created before 2006 have no date in Wikipedias database and thus the SUL util doesn't state anything in that row and in Hersfold's Fake SUL it is marked as ERR , @ ::)
  • The username has fewer than the sum of about fifteen global edits, none of which were within the last year.
  • Last edit was made over one year ago.
  • Last entry in logs occurred over one year ago.
  • If the similar account has zero edits on the English Wikipedia:
  • The username must have fewer than the sum of about fifteen edits globally, none of which were within the last 6 months.
  • Be older than 6 months.

Based on the above rules, if the account the request is too similar to is active, then click Similar to close the request as too similar to an active account.

If the account request is too similar to is inactive, you can go ahead and create the account, provided you are a flagged user, if not, you must break your reservation to allow a flagged user to create the account. Creating such an account should only be done after you have conducted all relevant checks required for any new account request. In order to create the account, you must check the "Ignore spoofing checks" box on the account creation page. This tells the MediaWiki software to ignore any similarity(ies) between the requested account and existing similar account(s), and thus allow the requested account to be created.

Connection to your Wikipedia account[edit]

A relatively new feature of the tool is the ability to connect your tool account to your Wikipedia account. This is done using the OAuth protocol, which gives the tool rights to perform certain actions on Wikipedia on your behalf.

Currently, the connection is only used to gain a cryptographically signed identity ticket from Wikipedia verifying that you have control of an account on Wikipedia. You can see the information in the identity ticket from your tool preferences.

All new users are required to connect their tool account to Wikipedia, and existing users are strongly encouraged to do so. Future updates to the tool may use more features of OAuth, at which point further permissions may be requested. You can manage the permissions available to the tool at Special:OAuthManageMyGrants.

Tool administrators[edit]

Tool administrators (tool admins) are trusted users who can, among other things, edit interface messages—they can use the Edit! buttons in Message management and Template management, and have access to a fifth option invisible to other users, User management, which allows them to approve, promote, demote, and suspend users. However, abuse of these tools is not tolerated, and the interface is not a toy. Abuse will result in immediate loss of access and tools!

Interface developers[edit]

The interface developers are the team who have commit access to the tool, and as such can modify the latest development version of the tool in the code repository. If you want something to be changed or added, or find a bug, you can contact one of them, but it's probably better to file a bug in the bug-tracker on GitHub. You can see the current development team on this page: tools:~acc/team.php.

The tool roots are stwalkerster and FastLizard4. They have access to the server that runs the tool, and are the only people who can modify the configuration of the tool, and update the tool to a new version. The tool roots also act as the liaison between the Labs administrators, and the rest of the tool users. The tool developers and roots reserve the rights to modify the tool as necessary, and to remove access to the tool for any reason as they see fit.


CheckUsers on Wikipedia should have a flag set on their tool account that allows them to have access to CheckUser-only information from the tool. If you are a CheckUser and do not have the flag set on your tool account or are unsure if the flag is already set, please contact one of the tool roots (Stwalkerster or FastLizard4) and they will set the flag for you.


  1. ^ Anything longer than a couple of weeks probably merits a longer gap — longer blocks generally indicate more serious abuse.
  2. ^ The mailing list is where users requesting accounts from ACC often send emails when they need help, and it is also one of the primary discussion mediums for ACC (the other being the #wikipedia-en-accounts IRC channel).
  3. ^ Cases of new accounts being created due to lost passwords etc will be considered on a case-by-case basis — be sure to let us know, probably by email to the mailing list
  4. ^ Failure to complete this step will result in your account being declined, as we cannot prove the connection between your registration, and your Wikipedia account. If you accidentally cancel the OAuth authorisation process, you can restart the linking by logging in to the interface using the password you specified during signup and continue the authorisation process. Existing users (currently) have the option of not linking their account as they have proved the connection using another method.

See also[edit]