Template:Admin dashboard
Administrative backlog
Reports
- 78.90.62.50 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log) – Tripped disruption-catching filters five times in the last 5 minutes (details). Report false positive. DatBot (talk) 13:23, 29 June 2025 (UTC)
- 83.226.241.135 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log) – Tripped filter 1345 (LTA 1345, details). Report false positive. DatBot (talk) 18:40, 29 June 2025 (UTC)
- Likely a FP. -Ad Orientem (talk) 03:53, 30 June 2025 (UTC)
- 95.98.65.177 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log) – Tripped filter 1345 (LTA 1345, details). Report false positive. DatBot (talk) 20:47, 29 June 2025 (UTC)
- FP. -Ad Orientem (talk) 03:54, 30 June 2025 (UTC)
- 185.30.197.206 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log) – Tripped disruption-catching filters five times in the last 5 minutes (details). Report false positive. DatBot (talk) 20:57, 29 June 2025 (UTC)
- No disruption since most recent warning. Now level II. -Ad Orientem (talk) 03:55, 30 June 2025 (UTC)
- AaravIsAKid (talk · contribs · deleted contribs · nuke contribs · logs · filter log · block user · block log) – Tripped disruption-catching filters five times in the last 5 minutes (details). Report false positive. DatBot (talk) 22:25, 29 June 2025 (UTC)
- Warned user, level II. -Ad Orientem (talk) 03:57, 30 June 2025 (UTC)
- 36.82.246.43 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log) – Tripped filter 1353 twice in the last 5 minutes (LTA 1353, details). Note: This filter has a large number of false positives. Use caution before blocking. Report false positive. DatBot (talk) 00:15, 30 June 2025 (UTC)
- Likely a FP. -Ad Orientem (talk) 04:08, 30 June 2025 (UTC)
- 35.33.251.233 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log) – Tripped filter 1353 twice in the last 5 minutes (LTA 1353, details). Note: This filter has a large number of false positives. Use caution before blocking. Report false positive. DatBot (talk) 01:01, 30 June 2025 (UTC)
- No disruption since being warned. -Ad Orientem (talk) 04:19, 30 June 2025 (UTC)
- 110.39.163.242 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log) – Tripped filter 1319 (LTA 1319, details). Report false positive. DatBot (talk) 04:55, 30 June 2025 (UTC)
- Warned user, level II. -Ad Orientem (talk) 05:01, 30 June 2025 (UTC)
- Ali Raza Journalist (talk · contribs · deleted contribs · nuke contribs · logs · filter log · block user · block log) – Tripped disruption-catching filters five times in the last 5 minutes (details). Report false positive. DatBot (talk) 06:48, 30 June 2025 (UTC)
- 122.150.161.189 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log) – Tripped disruption-catching filters five times in the last 5 minutes (details). Report false positive. DatBot (talk) 07:02, 30 June 2025 (UTC)
User-reported
- RachidRa (talk · contribs · deleted contribs · nuke contribs · logs · filter log · block user · block log) – On Rachid (singer): vandalism after final warning; actions evidently indicate a vandalism-only account. WP:NPOV and also 5 warnings. PerryPerson (talk) 00:29, 30 June 2025 (UTC)
Edits are not vandalism. Please ensure recent edits constitute vandalism before re-reporting. Daniel Quinlan (talk) 01:14, 30 June 2025 (UTC)
- Dragonman275 (talk · contribs · deleted contribs · nuke contribs · logs · filter log · block user · block log) – On :10 News First: User still doing WP:CUTPASTE moves after being warned not to. Happily888 (talk) 03:19, 30 June 2025 (UTC)
This noticeboard is for obvious vandals and spammers only. Consider taking this report to Administrators' noticeboard/Incidents. Ad Orientem (talk) 03:24, 30 June 2025 (UTC)
- Jeevan Sharma -GEO Journalist (talk · contribs · deleted contribs · nuke contribs · logs · filter log · block user · block log) – Block evasion by User:Journalist Jeevan Sharma. Fancy Refrigerator (talk) 07:02, 30 June 2025 (UTC)
- 217.165.236.203 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log) – On Spud (nickname): vandalism after final warning. DoebLoggs (talk) 07:46, 30 June 2025 (UTC)
- 49.196.166.0 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log) – On :10 Drama: Making WP:CUTPASTE moves after being warned not to. Happily888 (talk) 07:50, 30 June 2025 (UTC)
- 217.155.12.135 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log) – On Lilah Parsons: vandalism after final warning. DoebLoggs (talk) 08:13, 30 June 2025 (UTC)
- ÚMNåwDÌÈÙì Help (talk · contribs · deleted · filter log · SUL · Google) • (block · soft · promo · cause · bot · hard · spam · vandal)
Low confidence There is low confidence in this filter test, so please be careful when blocking. -- DQB (owner / report) 12:40, 28 June 2025 (UTC)
This username matched "Attempting to skip filters using multiple similar characters" on the blacklist. -- DQB (owner / report) 12:40, 28 June 2025 (UTC)
Note on file Multiple special characters can be contained in the same phrase, this rule detects when one or more occurs. -- DQB (owner / report) 12:40, 28 June 2025 (UTC)
- Grandprix86 (talk · contribs · deleted · filter log · SUL · Google) • (block · soft · promo · cause · bot · hard · spam · vandal)
- Low confidence There is low confidence in this filter test, so please be careful when blocking. -- DQB (owner / report) 16:10, 28 June 2025 (UTC)
- This username matched "Used x instead of cks attempting to skip filter: prick. Violating string: grandpricks86" on the blacklist. -- DQB (owner / report) 16:10, 28 June 2025 (UTC)
- Low level sexgen trolling. Secretlondon (talk) 18:24, 28 June 2025 (UTC)
- Endracism1234 (talk · contribs · deleted · filter log · SUL · Google) • (block · soft · promo · cause · bot · hard · spam · vandal)
- This username matched "rac(ial)?(ism|ist)" on the blacklist. -- DQB (owner / report) 16:20, 28 June 2025 (UTC)
- Note on file Accusations of racism may constitute a personal attack -- DQB (owner / report) 16:20, 28 June 2025 (UTC)
- I suspect this account only wants to comment on Israel/Palestine at this years Glastonbury. Secretlondon (talk) 18:23, 28 June 2025 (UTC)
- Omghowmanyusernamerestrictions (talk · contribs · deleted · filter log · SUL · Google) • (block · soft · promo · cause · bot · hard · spam · vandal)
- Low confidence There is low confidence in this filter test, so please be careful when blocking. -- DQB (owner / report) 17:40, 28 June 2025 (UTC)
- This username matched "long username without spaces" on the blacklist. -- DQB (owner / report) 17:40, 28 June 2025 (UTC)
- Username might also be disruptive per WP:NOTHERE. Johnny Au (talk/contributions) 00:50, 29 June 2025 (UTC)
- Keks111111111111111111111 (talk · contribs · deleted · filter log · SUL · Google) • (block · soft · promo · cause · bot · hard · spam · vandal)
- Bonervile (talk · contribs · deleted · filter log · SUL · Google) • (block · soft · promo · cause · bot · hard · spam · vandal)
- This username matched "boner" on the blacklist. -- DQB (owner / report) 03:50, 29 June 2025 (UTC)
- CoolEditDude (talk · contribs · deleted · filter log · SUL · Google) • (block · soft · promo · cause · bot · hard · spam · vandal)
- This username matched "Used i instead of l attempting to skip filter: (ltd|pty). Violating string: cooledltdude" on the blacklist. -- DQB (owner / report) 05:10, 29 June 2025 (UTC)
- Note on file Usernames containing this string are often promotional in nature - check if this is the case -- DQB (owner / report) 05:10, 29 June 2025 (UTC)
- False positive. Starfall2015 let's talk profile 07:44, 30 June 2025 (UTC)
- OBA AHMED MOROOF OLAKUNLE OGUNNAIKE OGUNDERU (talk · contribs · deleted · filter log · SUL · Google) • (block · soft · promo · cause · bot · hard · spam · vandal)
- Account used on kiwi browser for testing (main is PerryPerson) (talk · contribs · deleted · filter log · SUL · Google) • (block · soft · promo · cause · bot · hard · spam · vandal)
- Radqueertamari (talk · contribs · deleted · filter log · SUL · Google) • (block · soft · promo · cause · bot · hard · spam · vandal)
- Low confidence There is low confidence in this filter test, so please be careful when blocking. -- DQB (owner / report) 21:00, 29 June 2025 (UTC)
- This username matched "queer" on the blacklist. -- DQB (owner / report) 21:00, 29 June 2025 (UTC)
- Note on file the use of the word "queer" is not necessarily offensive please consider the context -- DQB (owner / report) 21:00, 29 June 2025 (UTC)
- CRUpdateBot (talk · contribs · deleted · filter log · SUL · Google) • (block · soft · promo · cause · bot · hard · spam · vandal)
- Ecommercewebsite15 (talk · contribs · deleted · filter log · SUL · Google) • (block · soft · promo · cause · bot · hard · spam · vandal)
User-reported
- Lin-Manuel McButtbacon (talk · contribs · deleted · filter log · SUL · Google) • (block · soft · promo · cause · bot · hard · spam · vandal) – Violation of the username policy as an offensive username. TheVeganFromNorfolk (talk) 15:53, 29 June 2025 (UTC)
- PEACE CO-29 (talk · contribs · deleted · filter log · SUL · Google) • (block · soft · promo · cause · bot · hard · spam · vandal) – Violation of the username policy as a promotional username. Check User Page Destinyokhiria 💬 21:18, 29 June 2025 (UTC)
- Not a violation of the username policy. Stage names and pen names are permitted except when they imply that the editor is a specific living person they are not. Consider filing a report at the conflict of interest noticeboard. — rsjaffe 🗣️ 21:22, 29 June 2025 (UTC)
- WikiNSE1 (talk · contribs · deleted · filter log · SUL · Google) • (block · soft · promo · cause · bot · hard · spam · vandal) Promotional username, promotional edits to Ashish Chauhan, who is the CEO of NSE. Yuvaank (talk) 21:20, 29 June 2025 (UTC)
 | This page has an administrative backlog that requires the attention of willing administrators. Please replace this notice with {{no admin backlog}} when the backlog is cleared. |
Current requests for increase in protection level
Place requests for protection increases at the BOTTOM of this section. If you cannot find your request, check the archive of requests or, failing that, the page history. Only recently answered requests are still listed here.
Reason: Arbitration enforcement and WP:ARBPIA GiraffeLover19 (talk) 21:33, 29 June 2025 (UTC)
Temporary semi-protection: Persistent addition of unsourced or poorly sourced content – Related to gambling scandal. Sushidude21! (talk) 21:42, 29 June 2025 (UTC)
- Automated comment: One or more pages in this request appear to already be protected. Please confirm.—cyberbot ITalk to my owner:Online 01:52, 30 June 2025 (UTC)
Semi-protection: Persistent disruptive editing – Recent trade. Sushidude21! (talk) 22:52, 29 June 2025 (UTC)
- Automated comment: One or more pages in this request appear to already be protected. Please confirm.—cyberbot ITalk to my owner:Online 00:52, 30 June 2025 (UTC)
Temporary semi-protection: Persistent disruptive editing – Recent trade. Sushidude21! (talk) 22:53, 29 June 2025 (UTC)
- Automated comment: One or more pages in this request appear to already be protected. Please confirm.—cyberbot ITalk to my owner:Online 00:52, 30 June 2025 (UTC)
Reason: IP user resumed edit warring to reinsert incorrect information about the game's art director since lifting of previous protection. Void if removed (talk) 22:58, 29 June 2025 (UTC)
- update: it wasn't really edit warring, so much as it was garden-variety vandalism. permanent semi protection might be a good idea consarn (grave) (obituary) 01:38, 30 June 2025 (UTC)
Semi-protection: Persistent vandalism – Recent addition of unsourced content due to transfer rumours, requesting a week's protection to prevent this. ser! (chat to me - see my edits) 23:36, 29 June 2025 (UTC)
Temporary semi-protection: Persistent vandalism – Presistent BLP violations from IP users. Roast (talk) 23:54, 29 June 2025 (UTC)
Reason: IP vandalism, removal of sourced content, and addition of unsourced information or trivia. CatchMe (talk · contribs) 00:07, 30 June 2025 (UTC)
Indefinite semi-protection: Recently subject to persistent disruptive edits (changes: 1, 2, 3, 4), which included overlinking and eventually caused the article in question to warrant a copy edit template. The user in question and their IPs have been blocked just this week. Mr. Lechkar (talk) 02:15, 30 June 2025 (UTC)
Temporary semi-protection: High level of disruptive editing. Film was released this weekend. Requesting semi-protection for two weeks. MB2437 02:24, 30 June 2025 (UTC)
Reason: Requesting semi-protection, article has been targeted by socks of User:TotalTruthTeller24 for about three weeks now. BOZ (talk) 03:40, 30 June 2025 (UTC)
Indefinite semi-protection: Edit warring with disruptive IP edits which remove/revert recent changes (including a WP:GALLERY violation) in the article along with edit warring on several other Disney Channel international networks articles; range-block the IP user if necessary. Kaptain Yummy (talk) 03:45, 30 June 2025 (UTC)
Temporary semi-protection: Persistent vandalism – persistent WP:CUTPASTE moves. Happily888 (talk) 03:58, 30 June 2025 (UTC)
Temporary semi-protection: Persistent vandalism – persistent WP:CUTPASTE moves. Happily888 (talk) 03:59, 30 June 2025 (UTC)
Temporary semi-protection: Persistent vandalism – persistent WP:CUTPASTE moves. Happily888 (talk) 03:59, 30 June 2025 (UTC)
Temporary semi-protection: Persistent vandalism – persistent WP:CUTPASTE moves. Happily888 (talk) 03:59, 30 June 2025 (UTC)
Temporary semi-protection: Persistent vandalism – persistent WP:CUTPASTE moves. Happily888 (talk) 03:59, 30 June 2025 (UTC)
Temporary semi-protection: Persistent vandalism – persistent WP:CUTPASTE moves. Happily888 (talk) 03:59, 30 June 2025 (UTC)
Temporary semi-protection: Persistent vandalism – persistent WP:CUTPASTE moves. Happily888 (talk) 03:59, 30 June 2025 (UTC)
Temporary semi-protection: Persistent vandalism – persistent WP:CUTPASTE moves. Happily888 (talk) 04:00, 30 June 2025 (UTC)
Semi-protection: Persistent sockpuppetry – MAB. AlphaBetaGamma (Talk/report any mistakes here) 04:00, 30 June 2025 (UTC)
- Automated comment: One or more pages in this request appear to already be protected. Please confirm.—cyberbot ITalk to my owner:Online 04:09, 30 June 2025 (UTC)
Temporary semi-protection: Persistent vandalism – Many of the Zee Entertainment pages already protected for same reason. IPs continue to add logos that are NOT on the website and despite this thread which shows it doesn't meet the style guide. Numerous warnings and yet it is a daily revert at this point. CNMall41 (talk) 04:55, 30 June 2025 (UTC)
Temporary semi-protection: Persistent vandalism – Many of the Zee Entertainment pages already protected for same reason. IPs continue to add logos that are NOT on the website and despite this thread which shows it doesn't meet the style guide. Numerous warnings and yet it is a daily revert at this point. CNMall41 (talk) 04:56, 30 June 2025 (UTC)
Temporary semi-protection: Persistent vandalism – Many of the Zee Entertainment pages already protected for same reason. IPs continue to add logos that are NOT on the website and despite this thread which shows it doesn't meet the style guide. Numerous warnings and yet it is a daily revert at this point. CNMall41 (talk) 04:56, 30 June 2025 (UTC)
Reason: Repeated vandalism, probably because of the the fact that iOS 26 was recently announced. Recommending semi-protection or pending changes protection at the least. Justjourney (talk | contribs) 05:07, 30 June 2025 (UTC)
Temporary semi-protection: Persistent vandalism – Ip editors kept on adding unsourced content. Cassiopeia talk 05:24, 30 June 2025 (UTC)
Temporary pending changes: Persistent edit-warring from IPs. GalStar (talk) (contribs) 07:11, 30 June 2025 (UTC)
- Automated comment: A request for protection/unprotection for one or more pages in this request was recently made, and was denied at some point within the last 8 days.—cyberbot ITalk to my owner:Online 07:12, 30 June 2025 (UTC)
Current requests for reduction in protection level
Before posting, first discuss with the protecting admin on their talk page. Post below only if you receive no reply.
- To find out the username of the admin who protected the page, click on "history" at the top of the page, then click on "View logs for this page," which is under the title of the page. The protecting admin is the username in blue before the words "protected", "changed protection level" or "pending changes". If there are a number of entries on the log page, you might find it easier to select "Protection log" or "Pending changes log" from the dropdown menu in the blue box.
- Requests to downgrade full protection to template protection on templates and modules can be directed straight here; you do not need to ask the protecting admin first.
- Requests for removing create protection on redlinked articles are generally assisted by having a draft version of the intended article prepared beforehand.
- If you want to make spelling corrections or add uncontroversial information to a protected page, please add {{Edit fully-protected}} to the article's talk page, along with an explanation of what you want to add to the page. If the talk page is protected, please use the section below.
Check the archives if you cannot find your request. Only recently answered requests are still listed here.
Reason: This page has been protected for over four years, and no disruption has occurred since 2018. Test to see if protection is still necessary. 2600:1700:C910:2960:A0A6:E1B2:A891:8B7C (talk) 19:28, 28 June 2025 (UTC)
- Pinging @Wugapodes: Daniel Case (talk) 20:51, 29 June 2025 (UTC)
Reason: This page has been protected for over four years, and no disruption has occurred since 2009. Test to see if protection is still necessary. 2600:1700:C910:2960:A0A6:E1B2:A891:8B7C (talk) 19:29, 28 June 2025 (UTC)
- Pinging @Wugapodes Daniel Case (talk) 20:52, 29 June 2025 (UTC)
Reason: This page has been protected for over four years, and no disruption has occurred since 2009. Test to see if protection is still necessary. 2600:1700:C910:2960:A0A6:E1B2:A891:8B7C (talk) 19:29, 28 June 2025 (UTC)
- Pinging @Wugapodes Daniel Case (talk) 02:02, 30 June 2025 (UTC)
Reason: Make way to accept Draft:Gillie da Kid at AfC. The title was salted by Maxim 18 years ago; they do not appear to be active. JSFarman (talk) 20:07, 29 June 2025 (UTC)
- Let's wait till the title is accepted. Daniel Case (talk) 02:19, 30 June 2025 (UTC)
- @Daniel Case: I reviewed the article at AfC and discovered the title was salted when I attempted to accept it. Can you unsalt it so it can be accepted? (Is "unsalt" a thing?) Thank you! JSFarman (talk) 03:33, 30 June 2025 (UTC)
Current requests for edits to a protected page
Please request an edit directly on the protected page's talk page before posting here
Ideally, requests should be made on the article talk page rather than here.
- Unless the talk page itself is protected, you may instead add the appropriate template among
{{Edit protected}},{{Edit template-protected}},{{Edit extended-protected}}, or{{Edit semi-protected}}to the article's talk page if you would like to make a change rather than requesting it here. Doing so will automatically place the page in the appropriate category for the request to be reviewed. - Where requests are made due to the editor having a conflict of interest (COI; see Wikipedia:Suggestions for COI compliance), the
{{Edit COI}}template should be used. - Requests to move move-protected pages should be made at Wikipedia:Requested moves, not here.
- If the discussion page and the article are both protected preventing you from making an edit request, this page is the right place to make that request. Please see the top of this page for instructions on how to post requests.
- This page is not for continuing or starting discussions regarding content should both an article and its discussion page be protected. Please make a request only if you have a specific edit you wish to make.
The Israeli casaulties have changed over the night with new Iranian strikes. I want to change the Current Casaulties from 24 Killed to 53, i have the sources needed. And to change the 2,345 injured to 2,585 injured for which i also have sources. Pkk123477 (talk) 18:53, 19 June 2025 (UTC)
On hold: Hello, Pkk123477. Your edit request has been restored here as we need further input on this, as initially requested by Behappyyar. Would you be willing to post the sources that you have so that they can be reviewed and used to update the article? --Super Goku V (talk) 21:09, 22 June 2025 (UTC)
Please correct the Iranian civilian casualties in paragraph three. It was recently changed without reason from 200 to 600. The sources currently listed actually say 200 but this is out off date. HRANA's latest figure is actually over 400. The source is presently used in the infobox for their own estimate of 1,054 total deaths. The Iranian government hasn't released updated figures so that should be removed until they have an estimate. I suggest adding the sentence:
"According to the anti-government Human Rights Activists in Iran News Agency, over 1,000 Iranians were killed including at least 400 civilians."
102.17.119.14 (talk) 03:11, 28 June 2025 (UTC)
Handled requests
A historical archive of previous protection requests can be found at Wikipedia:Requests for page protection/Archive.
| 1 protected edit request | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
| Updated as needed. Last updated: 16:31, 29 June 2025 (UTC) |
| 12 template-protected edit requests | ||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Updated as needed. Last updated: 03:34, 30 June 2025 (UTC) |
WP:PERM
| Requests for autopatrolled |
|---|
Autopatrolled
I've been here for almost two decades, with 30k+ edits and a fair number of articles created in the mean time. I believe I am well-qualified for autopatrolled perms. _dk (talk) 23:50, 16 June 2025 (UTC)
Hi. Based upon my learning and experience over the years of editing on Wikipedia (almost a decade now), I have created very selected pages which I find qualifying Wikipedia policies. If I find them trending in news but un-complying with the policies, I usually leave a redirect, or occasionally start with the draft. I believe not a single page that I created and/or majorly contributed has been deleted, and many respected editors and admins whom I had interacted with have always been helpful and supportive, believing in my good faith. Plus I only rewrite those articles in bad state which I find relevant, and not every other random article. However, due to recent attacks by sock puppetry over my edits, I want to be an autopatrolled user, so that I can easily continue volunteering independently here, and participate in the ongoing Destubathon as well. I promise I will not misuse this position. Thank you! M. Billoo 13:24, 19 June 2025 (UTC)
Requested this permission ~2 months ago, denied because I was mostly creating auto-notable stubs. I think I have expanded the types of articles I create, including well-sourced local pages or biographical entries where I take time to source subjects that do not inherently meet a generic notability criteria. (I still do create auto-notable pages sometimes, but those no longer make up the majority of pages I create.) As a new page reviewer, I got good experience with the notability guidelines reviewing articles during the backlog drive WP:MAY25, and also participating in AfD. Thought about requesting again as I have run into a few of my own pages while reviewing pages that are in topics I contribute to/am interested in. Yoblyblob (Talk) :) 02:15, 28 June 2025 (UTC)
|
| Requests for AutoWikiBrowser access |
|---|
AutoWikiBrowser
Hello, I would like to use the editor mainly to have access to backreferences for editing using regular expressions. My actual use case would be to make a 300-line table sortable by last name. Work with data would also be useful. I also would like to be able to speed up formatting more generally, e.g. italics, quote marks, etc. Selbsportrait (talk) 22:27, 23 June 2025 (UTC)
I'm back again! I previously requested this to help with WP:POSTMOVE for links to Guna language (then withdrew that request), but since then I've realised there are a few areas I could use this tool in, not least for updating non-linked uses of "Kuna" and "Cuna" for Guna language and Guna people (of which there seem to be quite a lot). I might also use it for linking/redlinking new articles (for instance, some of the drafts I'm currently working on), and also to help out with updating some of the 90,000+ articles transcluding (the now-deprecated) Template:EngvarB to other English-variety templates. Obviously there might also be some typo correction etc. as required. Pineapple Storage (talk) 17:03, 24 June 2025 (UTC)
Hello again. I'd like AWB rights to fix typos in Category:All Wikipedia articles needing copy edit, especially the really common MOS:CURLY violations. I got denied last time for not having made enough edits but I now have made over 600 mainspace edits so I think this should be fine :) --cheesewhisk3rs (pester) 22:59, 28 June 2025 (UTC) --cheesewhisk3rs (pester) 22:59, 28 June 2025 (UTC)
|
| There are no outstanding requests for the confirmed flag. |
|---|
Confirmed |
| Requests for extended confirmation |
|---|
Extended confirmed
Reason for requesting extended confirmed rights My EC/XC status was suspended with extended conformed restriction due to a mistake in Special:Diff/1296492089. The status was removed by Star Mississippi, who said that I was welcome to reapply, after explaining myself, especially contradicting that I had won my status through gaming. After checking my editorial history, there was general agreement in the discussion that that was not the case. The discussion is located in: Jensenjan and WP:XC WP:GAMING I am now more careful with unintentionally wading into sensitive subjects and I continue to edit less controversial entries.I respectfully ask to have my EC/XC status reinstalled. Jensenjan (talk) 11:07, 26 June 2025 (UTC)
|
| Requests for new page reviewer |
|---|
New page reviewer
Hi, I'm requesting rights be extended after a one month trial. I would like to request permanent NPR rights if possible, as I have greatly enjoyed contributing in this capacity and I am eager to help reduce the backlog. Thanks! Halley luv Filipino ❤ (Talk) 00:23, 23 June 2025 (UTC)
I'm a patroller on the Hebrew Wikipedia with extensive experience in content review and Wikipedia policies. I am also familiar with English Wikipedia's guidelines and have been actively participating here, including contributing to article creation and quality control processes. I would like to contribute to New Page Patrol, mainly on topics related to Israel, Judaism, and Hungary, and I would be happy to expand my knowledge and activity into additional areas. Eliezer1987 (talk) 16:58, 23 June 2025 (UTC)
NPR temporary permissions set to expire within a week. Requesting extension or permanent permissions. I have not been as active in the NPR space as I'd like to be, being very busy with the AfC Backlog Drive. Regardless, thank you for your time! MWFwiki (talk) 21:23, 23 June 2025 (UTC)
Hi there, my rights expire on the 30th and I would like to request an extension. I did ask a few weeks ago since I know of the perennial backlog here, but got rejected on the basis it was too early. I'm reapplying now since it's a little under a week until that happens. Aydoh8[what have I done now?] 23:34, 23 June 2025 (UTC)
I was granted reviewer rights for two times, both were temporary. I'm here requesting the right again to review the articles and make the burden less for others too. I was not active like before due to some personal issues, but I'm going to be active now. Please consider extending my rights. Thankyou Taabii (talk) 17:23, 25 June 2025 (UTC)
Hello there, this is my third time requesting new page reviewer permissions, as the previous two requests were granted on a one-month trial basis and the current trial will end on the 30th of June. I have learnt a lot about the policies for notability and inclusion and will be able to reduce the size of the unreviewed pages backlog significantly. JustARandomEditor123 (talk) 06:07, 27 June 2025 (UTC)
I am currently an AFC reviewer and am familiar with the deletion processes. I would like to help clear the backlog. I believe I meet the criteria for this right. I am requesting a trial. Thanks Cactus🌵 spiky ouch 01:04, 29 June 2025 (UTC)
Hello, my rights expired and I completely forgot to reapply till now. I would like to request an extension, as I think I didn't do enough patrolling to warrant a permanent grant (thanks AfC backlog drive). Thank you. mwwv converse∫edits 01:10, 30 June 2025 (UTC)
I have had two 1 month trials before which just expired so I am here to ask to continue, or for indefinite, which ever is more appropriate. Moritoriko (talk) 06:18, 30 June 2025 (UTC)
My current NPR rights are due to expire on 1 July 2025. While I may not be reviewing in large volumes, I focus on thorough, policy-aligned reviews that aim to improve or appropriately tag each page. I’d like to keep my NPR rights for continued constructive contributions. Thank You. Ambrosiawater (talk) 07:55, 30 June 2025 (UTC) |
| Requests for page mover |
|---|
Page mover
I am requesting page mover right mainly because it would help me draftify articles (see my draftify log). And secondarily because it would allow me to perform uncontroversial moves in mainspace without leaving being redirects. I have not participated in RMs but I have made moves that show that I understand the guidelines, namely:
And more recently
I was recommended to return after over a dozen requests at RMTR, and after Gaza war mvoes, I think I've well surpassed that threshold. I'm otherwise keen to continue closing RMs in the backblog, and it'd make it more convenient to implement WP:POSTMOVE after closing such discussions rather than later. Thanks for your re-consideration. CNC (talk) 21:03, 27 June 2025 (UTC) CNC (talk) 21:03, 27 June 2025 (UTC)
|
| Requests for pending changes reviewer |
|---|
Pending changes reviewer
This is my third application. I believe that I have enough experience and that with the help of Twinkle, I could throw a "ROLLBACK" command and thwart the vandals. Thank you, Starfall2015 chat | about me 06:14, 14 June 2025 (UTC)
Hello, While patrolling the recent changes, I often run into pending changes. I think I am a good candidate for this permission because I already revert vandalism prolifically. I have read WP:RPC and whenever I revert something that's not blatant vandalism/a BLP violation, I always include an adequate edit summary, so I would also be able to tell which pending changes are low-quality good-faith edits and let them through (with amendments after, possibly). I also never engage in edit wars or abuse my rollback function. Spotemgottem (talk) 08:27, 29 June 2025 (UTC) |
| Requests for rollback |
|---|
Rollback
I am respectfully requesting rollback rights as I am committed to upholding the quality and reliability of Wikipedia by actively monitoring recent changes and promptly reverting vandalism and unconstructive edits. Having familiarized myself with Wikipedia's policies and guidelines, I believe that the rollback tool will allow me to more efficiently contribute to the maintenance of article integrity and the overall improvement of the encyclopedia. Vineyard93 (talk) 01:04, 23 June 2025 (UTC)
Hello. I saw that rollbackers need 200+ edits and noticed that I've cleared that mark so here is my request: I have been actively reverting vandalism via WP:RW and filters. I apply an adequate edit summary and warn for every single rollback I make using RedWarn. I understand clearly that rollback is for cases of clear-cut vandalism and other edits where the reason for the revert is obvious (such as uncited defamatory statements on a living person). Whenever I encounter a good-faith yet low-quality edit, I either leave it be or undo it with a suitable custom edit summary (and a talkpage message explaining why the edit was reverted). Having this user right would allow me to try out Huggle which I believe would be more efficient than RedWarn's RC patrol or refreshing the browser. Thank you. Spotemgottem (talk) 00:15, 26 June 2025 (UTC)
Hi, I've had several months of experience patrolling recent changes and clearing vandalism. In addition, I often revert sockpuppet edits. I therefore humbly request for the rollback right so that reverting obvious vandalism and sockpuppet/LTA edits (such as by using mass rollback) would be easier. I've read through WP:Rollback thoroughly as well. I understand that for the usual rollback, I need to try to use it with caution as it performs reverts in just one click/tap. Thank you. ~SG5536B 01:56, 27 June 2025 (UTC)
I’m a very active recent changes patroller, very comfortable identifying vandalism and using WP:TW to revert, warn, and report vandals. I’m careful to avoid using immediate revert unless the edit is obviously vandalism. Rollback would allow me to more efficiently fight very active vandals before an administrator is able to block them. I would still use WP:TW in most cases, for routine recent changes patrol. ZachH007 22:47, 28 June 2025 (UTC)
I’ve been using Twinkle to revert vandalism from recent changes and warn users for a while now. I’ve been doing this for about two years, with some breaks because of school and life, but I’ve stayed consistent overall. I know what counts as vandalism and what doesn’t, and I always try to assume good faith. I’d really appreciate rollback to help make reverting quicker and save time. I can be trusted with the tool and use it properly. Thank you, ItsCheck (talk) 01:05, 29 June 2025 (UTC)
|
Usage
{{Admin dashboard/header}}
{{Admin dashboard/ab}}
{{#ifeq:{{Yesno|{{{showaiv|7 days}}}}}|yes|{{#ifexpr:{{#time:U|-{{{showaiv|7 days}}}}}-{{#time:U|{{REVISIONTIMESTAMP:WP:Administrator intervention against vandalism}}}} <= 0|{{Admin dashboard/aiv}}}}}}
{{Admin dashboard/csd}}
{{Admin dashboard/uaarfpp}}
{{Admin dashboard/rfarfp
| 1 = {{{style|}}}{{#if:{{{showperm|}}}|
{{!}} showperm {{=}} {{{showperm}}} }}{{#if:{{{showrfab|}}}|
{{!}} showrfab {{=}} {{{showrfab}}} }}{{#if:{{{showacc|}}}|
{{!}} showacc {{=}} {{{showacc}}}} }}{{#if:{{{showaptl|}}}|
{{!}} showaptl {{=}} {{{showaptl}}} }}{{#if:{{{showawb|}}}|
{{!}} showacc {{=}} {{{showawb}}}} }}{{#if:{{{showconf|}}}|
{{!}} showconf {{=}} {{{showconf}}} }}{{#if:{{{showfmvr|}}}|
{{!}} showext {{=}} {{{showext}}} }}{{#if:{{{showacc|}}}|
{{!}} showacc {{=}} {{{showevco}}}} }}{{#if:{{{showext|}}}|
{{!}} showfmvr {{=}} {{{showfmvr}}} }}{{#if:{{{showmms|}}}|
{{!}} showmms {{=}} {{{showmms}}} }}{{#if:{{{showrevr|}}}|
{{!}} shownpr {{=}} {{{shownpr}}} }}{{#if:{{{shownpr|}}}|
{{!}} showpmvr {{=}} {{{showpmvr}}} }}{{#if:{{{showpmvr|}}}|
{{!}} showrevr {{=}} {{{showrevr}}} }}{{#if:{{{showrlbk|}}}|
{{!}} showrlbk {{=}} {{{showrlbk}}} }}{{#if:{{{showte|}}}|
{{!}} showte {{=}} {{{showte}}} }}
}}
{{Admin dashboard/footer|newadmin={{{newadmin|no}}}}}<!--
You can re-arrange the order or pick and choose by transcluding elements separately -->
Note that directly transcluding the template or using all the subtemplates above can cause the page to exceed the post-expand include size.
Parameters
TemplateData for Admin dashboard
Administrators Dashboard
| Parameter | Description | Type | Status | |
|---|---|---|---|---|
| style | 1 | Backwards compatibility. Not entirely show of purpose at this time.
| String | optional |
| New administrator | newadmin | Allows you to toggle the 'New administrators' navbox on/off. Set to 'yes' to transclude.
| String | optional |
| Show AIV | showaiv | Allows you to toggle the WP:AIV section on/off. Set to 'no' to prevent transclusion.
| String | optional |
| Show PERM | showperm | Allows control over the entire WP:PERM section in one parameter. Setting this parameter to a valid time offset will only show sections that have had an edit in the specified amount of time.
| String | optional |
| Show RfA/RfB | showrfab | Allows hiding the requests for RfA/RfB section of WP:PERM. Setting this parameter to a valid time offset will only show this section if it has had an edit in the specified amount of time.
| String | optional |
| Show account creator | showacc | Allows hiding the requests for account creator section of WP:PERM. Setting this parameter to a valid time offset will only show this section if it has had an edit in the specified amount of time.
| String | optional |
| Show autopatrolled | showaptl | Allows hiding the requests for autopatrolled section of WP:PERM. Setting this parameter to a valid time offset will only show this section if it has had an edit in the specified amount of time.
| String | optional |
| Show confirmed | showconf | Allows hiding the requests for confirmed section of WP:PERM. Setting this parameter to a valid time offset will only show this section if it has had an edit in the specified amount of time.
| String | optional |
| Show extended confirmed | showext | Allows hiding the requests for extended confirmed section of WP:PERM. Setting this parameter to a valid time offset will only show this section if it has had an edit in the specified amount of time.
| String | optional |
| Show file mover | showfmvr | Allows hiding the requests for file mover section of WP:PERM. Setting this parameter to a valid time offset will only show this section if it has had an edit in the specified amount of time.
| String | optional |
| Show new page reviewer | shownpr | Allows hiding the requests for new page reviewer section of WP:PERM. Setting this parameter to a valid time offset will only show this section if it has had an edit in the specified amount of time.
| String | optional |
| Show page mover | showpmvr | Allows hiding the requests for page mover section of WP:PERM. Setting this parameter to a valid time offset will only show this section if it has had an edit in the specified amount of time.
| String | optional |
| Show reviewer | showrevr | Allows hiding the requests for reviewer section of WP:PERM. Setting this parameter to a valid time offset will only show this section if it has had an edit in the specified amount of time.
| String | optional |
| Show rollback | showrlbk | Allows hiding the requests for rollback section of WP:PERM. Setting this parameter to a valid time offset will only show this section if it has had an edit in the specified amount of time.
| String | optional |
| Show template editor | showte | Allows hiding the requests for template editor section of WP:PERM. Setting this parameter to a valid time offset will only show this section if it has had an edit in the specified amount of time.
| String | optional |