Wikipedia:Requests for permissions/Administrator instructions/General

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

To override where the bot archives, use  for approved, or   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, as with done or not done. Strikethroughs like  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 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. See User:MusikBot/PermClerk for more information on the tasks and how to configure them.