Template talk:Admin dashboard

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

This administrative dashboard was designed to assist admins[1] in focusing their efforts whilst wielding their mop and bucket. It can be displayed in your userspace by typing {{admin dashboard}} to transclude it. You could also change the order or eliminate sections by transcluding the subpages separately. New features can be requested below or simply edited in yourself. An alternate version of this template can be found at {{dashboard}}.


  • When there are any attack pages or users looking for help, or when the candidates for speedy deletion category exceed 50 (i.e. backlogged), those rows will turn red
  • When there are empty or user requested candidates for speedy deletion, those rows turn green (because you can usually "GO" ahead and delete them ;>)
  • When transcluded, the page will automatically have SoxBot create your adminstats pages if it has not already been created
  • It transcludes Cyde's articles that have been proposed for deletion for at least five days, but keep in mind they might not be eligible for deletion *just yet*
  • The purge button will ensure you get the most up-to-date information (add this link to your quick links toolbar for great justice)
  • When there are current outstanding requests for rollback or account creator, a new section will appear in the table of contents called "WP:RFPERM (rollback)" or "WP:RFPERM (account creator)".[2]
  • Non-admin users are free to utilize the dashboard, and may use the parameter admin=no to suppress the adminstats portion[3] as the bot will not calculate admin stats for non-admins


  1. ^ Who's using it? (linking it?) (talking about it?!)
  2. ^ Feature suggested by Keeper76
  3. ^ Inspired by the first non-admin user, Relyimah


I just added the following to my monobook.js so I'd have quick access to my local copy of the dash. Should be easily modifiable if you want to jump right to the template instead.

--SarekOfVulcan (talk) 16:44, 9 July 2008 (UTC)

  • Cool! On the subject of admin monobook enhancements, i've got User:Xenocidic/twinklewarn.js (blocking level of warning selected by default) (now handled by defaultWarningGroup : 8, in Twinkle config), and also the below script will move the toolbox and search menus above interaction and navigation.

xeno (talk) 16:54, 9 July 2008 (UTC)

  • Its a minor nuisance that prods appear an hour or two before the five days is up (numerous: e.g. My Zmanim expires at 15:59 today).
  • High percentages of prods and speedys seem to relate to sport and modern music. I enjoy these in real life but for some reason find them uninteresting issues on-wiki. It would grand if there was some simple way of categorising them so that I could focus on those I feel motivated to engage with (pop-ups are sometimes v. slow in this neck of the woods). Ben MacDui 13:28, 30 August 2008 (UTC)
    This might be a suggestion you could raise to User:Cyde, who runs the bot which makes the proddable page list. –xeno (talk) 03:03, 16 April 2009 (UTC)
  • Could we put some common links right at the top, like WP:ANI?--SarekOfVulcan (talk) 21:18, 23 February 2009 (UTC)
    • There are links to the noticeboards in the footer, you could move this up if you desired. but feel free to tweak the header and if i don't like it i can make it into an option with a paramater... –xeno (talk) 21:20, 23 February 2009


March 2009[edit]

  • Pages listed in Category:Administrative_backlog should be prominently announced at the top of the page to try to bring down the backlogs sooner. -- (talk) 08:03, 19 March 2009 (UTC)
    Not sure if it's possible to transclude a category... –xeno (talk) 03:03, 16 April 2009 (UTC)
    Yes check.svg Done using <categorytree>. Feel free to put it on a separate subpage.— Train2104 (talk • contribs • count) 00:59, 29 September 2010 (UTC)
  • The AIV section doesn't list the actual reports, it just lists the symbols key; the AIV reports should be added. -- (talk) 08:10, 19 March 2009 (UTC)
    This is fixed, someone had removed the closing noinclude tag - thank you. –xeno (talk) 12:47, 19 March 2009 (UTC)
    Slap a semi on this thing so crazy IPs don't screw it up! -- (talk) 16:53, 19 March 2009 (UTC)
    That was actually the main WP:AIV page and it's only semi'd when it gets vandalized. Thanks for catching it though. I'll look into the other suggestions when I get a moment. –xeno (talk) 16:55, 19 March 2009 (UTC)
  • The link for admin stats in the RFA section is red; should be removed or the template created. -- (talk) 08:10, 19 March 2009 (UTC)
    The link turns blue when transcluded onto an admin's user page when their stats page exists. –xeno (talk) 12:48, 19 March 2009 (UTC)
  • Add 3RR noticeboard. -- (talk) 08:10, 19 March 2009 (UTC)
    WP:AN/3 gets awful big, but if there are admins who are interested in having it included I could make it an optional parameter. –xeno (talk) 03:03, 16 April 2009 (UTC)

Possible addition[edit]

{{In the news/Next update/Time}}, perhaps? And the DYK timer as well? SpencerT♦Nominate! 00:16, 9 April 2009 (UTC)

Feel free to tuck these in somewhere... –xeno (talk) 02:32, 16 April 2009 (UTC)

Reviewer RFPerm[edit]

Added in the Review request for permissions since it seems we are getting a fair amount of these requests. Diff here - feel free to undo if this causes issues.  7  08:55, 16 June 2010 (UTC)

Looks great. Thanks, –xenotalk 23:01, 16 June 2010 (UTC)

Great page[edit]

I happen to think this a great resource and I find it very useful. I've actually been adding on to it, in a dashboard of my own which basically includes everything, every piece of information, pages to watch, things to read, processes to follow, every area an admin may want to work in. It may seem pretty lengthy, I tried to cram in as much as I could ;), but it's basically just a collection of transcluded pages so the editable page itself is pretty small. It's at User:OlEnglish/Dashboard if anyone wants to use it or copy it. -- œ 04:37, 28 November 2010 (UTC)

Suggestion re PROD list[edit]

I don't think it makes sense to list the prods whose expiration will come up sometime during the day, when it would be trivial to list those PRODs eligible for deletion.

I posted a request to Cyde on 12 December, with no response. (I saw somewhere that Cyde may have left the project.)

Does anyone disagree that it would be better to list articles eligible for deletion rather than those who eligibility is upcoming? If so, does anyone have thoughts on how to make it happen?--SPhilbrickT 14:02, 1 January 2011 (UTC)

I agree, but I am afraid I have no idea how this could be done. Ben MacDui 09:31, 2 January 2011 (UTC)
But in all these cases their eligibility is only hours away. It's trivial NOT to consider them already expired--their 7 days is up. It's unlikely anyone would de-prod them on the last day. Besides, if it's an obvious delete, admins can use their discretion when deciding if and when to delete. -- œ 16:03, 3 January 2011 (UTC)
That is not what WP:PROD says - can you say where the existence of such discretion is indicated? Ben MacDui 08:45, 4 January 2011 (UTC)
This issue arose because HJ Mitchell pointed out to me here that I was closing too soon, so at least some don't accept that closing early is fine. Nor do I, my early closures occurred because I assumed the list only included eligible ones. I've stopped closing PRODs. While I realize it is not hard to check each and every one, it would be better to fix the problem. Jarry1250 thinks it should be easy. I'd do it myself, but I have no experience with bots, and this doesn't sound like the right place to experiment.
I think we need two things:
  1. Consensus that the change is desired
  2. A volunteer who knows how to change the code.--SPhilbrickT 13:40, 4 January 2011 (UTC)
Out of curiosity, could someone point me at the relevant code? I'm almost certainly the wrong person to change it, but I'm curious, and who knows.... maybe it really is entirely trivial. --je deckertalk to me 17:50, 27 February 2011 (UTC)
Actually the distinction isn't trivial. With BLP prods some focus on those in their last day. Note that the BLP prod template sorts them by time left. It would be a simple exercise to have a Category:Articles proposed for deletion (time expired), then a separate bot (not trivial but not hard) task to listify that every few hours. Rich Farmbrough, 17:19, 24 February 2011 (UTC).
Fair point. I can imagine that members of the Article Rescue Squadron might want to see the prods that are due to expire. However, I think it should be easy to use the existing code, generate a list called "Articles proposed for deletion (about to expire)", and post that list at ARC or other useful places. Then increment the parameter by one day, and create the list "Articles proposed for deletion (expired)" for use on the admin template. It is misleading to include a list of prods about to expire on the admin to do list.--SPhilbrickT 17:51, 24 February 2011 (UTC)
Turns out there already is such a category. Category:Expired proposed deletions. Problem is it was empty until I null-edited the last days worth of prods. So it all gets a little crazy - to null edit them one needs to read them, which means the date is already in our grasp. So keeping a local list of timestamps seems sensible, then checking they are still prodded. More work than just listifying a cat. Rich Farmbrough, 19:50, 25 February 2011 (UTC).
I'd support this, particularly if I can get at a list of "soon-to-expire" items too, even if it's a separate list, I don't care where. In addition to occasional "article saves" I do sometimes peek "ahead" of the expiration dates and double-check for BLPPRODs that folks have added RS to without pulling the tag, no doubt the closing admin will eventually do that anyway, but it seems to appeal to my need for tidiness.
One note: trying to make sense of which are and aren't expired in the current list is complicated by the fact that the 7-vs-10 day difference between PRODs and BLPPRODs leaves expired and unexpired items fairly intermingled. Sorting the list based on expiration time, and/or separating PRODs and BLPPRODs into two tables, and/or harmonizing the 7 and 10 day wait times for the two tags, would make things easier too. --je deckertalk to me 17:48, 27 February 2011 (UTC)
  • Actually, using prodsum, its a helpful distinction. The ones that are on the top after >7 days are BLP prods, and since I try to look at every one of them, I can wait till then if I don't have time to look further. Additionally, I am among those who check at the end--I try to go between 12 and 36 hours ahead of the actual deletion, in order to double-check only those that have not been removed by others, since I'm prepared to work on the more difficult problems. DGG ( talk ) 01:45, 28 February 2011 (UTC)


It might be a good idea to semiprotect these pages given the number of transclusions. [1] Reaper Eternal (talk) 18:15, 9 February 2011 (UTC)

Addition proposal[edit]

Can we add

| [[:Category:Requested edits#Pages in category|Requested Edits]] || {{PAGESINCAT:Requested edits}}

to the {{Admin dashboard/header}} so that coi requested edits are listed? I could be bold, but I'd like to get some views from other editors first. I'm requesting the same thing at {{dashboard}} Ryan Vesey Review me! 18:06, 21 June 2012 (UTC)

COI proposal[edit]

Would anyone object if I set the COI backlog to 95 (currently 99), indicating when it should turn red? I'd like to get it down to 50 or so, but if I do that immediately, it may stay red for some time. I've run into admins who don't even know the concept exists, despite being on the dashboard, and my hope is that the red banner will prompt some action. My plan would be to gradually lower the threshold slowly until it gets to 50.--S Philbrick(Talk) 21:31, 21 July 2014 (UTC)

Not hearing any objection, I set it at 120. Want it lower, but wanted to start with an achievable goal.--S Philbrick(Talk) 14:17, 1 September 2014 (UTC)