The confirmed user right provides a user early access to editing privileges that all users receive with autoconfirmed, which is automatically granted when an account has at least 10 edits and is at least 4 days old.^[1]

Autoconfirmed or confirmed users can create articles, move pages, edit semi-protected pages, and upload files or upload a new version of an existing file. Autoconfirmed users are no longer required to enter a CAPTCHA for most events and they may save books to the Books namespace. In addition, the Edit filter has a number of warning settings that only affect editors who are not autoconfirmed.

The vast majority of requests for confirmed are declined. First consider:

1. If they just want to upload an image, they can make a request at Files for upload for non-free images or use the same username and password to upload free images at Wikimedia Commons
2. If they just want to change the name of an article, they can file a requested move

That being said, acceptable means for granting confirmed early may include:

1. The account is a legitimate alternative account of a user who is already autoconfirmed
   • Check the original account's account creation log to verify the accounts have the same owner
   • You could also request that the user make an edit under original account confirming the alternate account belongs to them
   • If the original account does not have an established record in the project, the need for a confirmed alternate account may be questionable
2. The user has been shown especially prolific editing patterns, to the extent that the CAPTCHA's they run into are inhibiting their productivity
   • The user might have edited under as an IP prior to having the account. For privacy reasons you should not request they verify this
   • There should be no evidence of unconstructive editing. You may wish to check the user's filter log

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:

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.