Commons:Administrators

Shortcuts: COM:A • COM:ADMIN • COM:SYSOP

This page explains the role of administrators (sometimes called admins or sysops) on Wikimedia Commons. Note that details of the role, and the way in which administrators are appointed, may differ from other sites.

If you want to request administrator help, please post at Administrators' noticeboard.

There are currently 180 administrators on Commons.

What is an administrator?

Administrators as of November 2024
Listing by: LanguageDateActivity [+/−]

Number of Admins: 180

  1. 1234qwer1234qwer4, ru, de-4, en-3
  2. 1Veertje, nl, en-4, de-1, fr-1
  3. 32X, de, en-2, hsb-1, ru-1
  4. 99of9, en (bureaucrat)
  5. A.Savin, ru, de-4, en-2
  6. Aafi, ks, ur-5, en-3, hi-2, ar-1
  7. Abzeronow, en, fr-1
  8. Achim55, de, en-3, nds-3, la-2
  9. AFBorchert, de, en-3
  10. Ahonc, uk, ru-4, en-2, de-1
  11. Aka, de, en-3
  12. Alno, fr, en-3, es-2, pt-1
  13. Андрей Романенко, ru, en-3, uk-3, be-2, fr-2, lv-2
  14. Ankry, pl, en-2, ru-1
  15. AnRo0002, de, en-2, fr-2, es-1
  16. Anthere, fr, en-3
  17. AntiCompositeNumber, en, fr-2 (steward)
  18. Aude, en, ar-2, de-2, es-3
  19. Bastique, en, fr-3, es-2, la-2, fi-1, pl-1
  20. Bedivere, es, en-4, pt-1
  21. Billinghurst, en
  22. Blackcat, it, en-3, fr
  23. BrightRaven, fr, en-3, nl-2, es-2, zh-1
  24. Butko, ru, uk-2, en-1
  25. Captain-tucker, en
  26. Christian Ferrer, fr, en-2, es-2
  27. Ciell, nl, en-2, de-1
  28. Common Good, en
  29. CptViraj, gu, hi-4, en-3 (bureaucrat)
  30. Cromium, en, de-1, fr-1
  31. Cybularny, pl, en-2, es-1, de-1
  32. Czar, en
  33. DaB., de, en-1
  34. DarwIn, pt, en-3, es-2, fr-2, gl-2, ca-1, it-1, oc-1
  35. Davepape, en
  36. DerHexer, de, en-3, grc-3, la-3, es-1 (steward)
  37. Dharmadhyaksha, mr, en-3, hi-3
  38. DMacks, en
  39. Didym, de, en-2, fr-2
  40. Dyolf77, ar, fr-5, en-2, it-1, es-1
  41. D-Kuru, de, en-2, it-1
  42. Ebrahim, en-3
  43. Elcobbola en, de (checkuser)
  44. Ellin Beltz, en (bureaucrat)
  45. Ellywa, nl, en-2, de-1, fr-1
  46. Emha, de, bar, en-3, fr-1
  47. Érico, pt, en-2, es-1
  48. EugeneZelenko, ru, be, en-2, bg-1, pl-1 (bureaucrat)
  49. Explicit, en, es, ko-2
  50. Ezarate, es-3, en-1
  51. Fitindia, en-3, hi-2, mr-2
  52. FunkMonk, da, en-4, no-3, fo-2, sv-2, de-1, es-1
  53. Gbawden, en-3, af-1
  54. Geagea, he, ka-3, en-3, ru-1
  55. Geni, en
  56. George Chernilevsky, ru, uk-3, de-2, en-2, bg-1, la-1, be-1, fr-1
  57. Gestumblindi, als, de, en-3
  58. Gnangarra, en, nys-1
  59. GPSLeo, de, en-2
  60. GreenMeansGo, en
  61. Grin, hu, en-3, de-1
  62. Hekerui, de, en-4
  63. Herbythyme, en, fr-2, es-1, it-1
  64. Hesperian, en
  65. Holly Cheng, en, ja-2
  66. Huntster, en
  67. Indeedous, de, en-3, fr-2
  68. Infrogmation, en, es-1
  69. IronGargoyle, en, de-1
  70. Jameslwoodward, en, fr-1 (bureaucrat, checkuser)
  71. Jaqen, it, en-2
  72. Jarekt, pl, en
  73. JarrahTree, en, id-1
  74. Jcornelius, de, lt-2, la-2, en-2, pt-2, fr-1
  75. Jdforrester, en
  76. Jean-Frédéric, fr, en-4, es-1
  77. Jianhui67, en, zh-4, ja-2, ms-2
  78. Jmabel, en, es-3, ro-2, de-1, ca-1, it-1, pt-1, fr-1
  79. Joergens.mi, de, en-3
  80. JoKalliauer, de, en-3
  81. Jon Kolbert, en, fr-4, de-2 (steward)
  82. Josve05a, sv, en-3
  83. Jusjih, zh, en-3, fr-2, ko-1
  84. Kadı, tr, en-5, fr-2, az-2
  85. Kallerna, fi, en-3, sv-2, de-1
  86. King of Hearts, en, zh-3, es-2, ja-1
  87. Klemen Kocjancic, sl, en-3, de-2, hr-1, bs-1
  88. Krd, de, en-3 (bureaucrat, checkuser)
  89. Krinkle, nl, en-3, de-2
  90. Kritzolina, de, en-3, fr-2, it-1
  91. Léna, fr, en-3, es-1
  92. Leyo, gsw, de, en-3, fr-3, es-1, la-1
  93. Lofty abyss, en, mt, it-2
  94. Lymantria, nl, en-3, de-2, fy-2, fr-1, zea-1
  95. Magog the Ogre, en, es-2
  96. Mahagaja, en, de-4, fr-2, ga-2, la-2, cy-1
  97. Maire, pl, en-4, es-2, fr-2, de-2, ru-1
  98. Marcus Cyron, de, en-2
  99. Masur, pl, en-3, de-1
  100. Materialscientist, en-4, ru-4, nl-3, fr-1, es-1
  101. Matrix, en, ta-2
  102. MB-one, de, en-3, fr-1, pt-1
  103. MBisanz, en
  104. Mdaniels5757, en, es-1
  105. MGA73, da, en-3, de-2, no-1, sv-1
  106. Mhhossein, fa, en-3, ar-1
  107. Micheletb, fr, en-3, it-1, es-1
  108. Mike Peel, en, pt-2, fr-1
  109. Minorax, en, zh (oversighter)
  110. Missvain, en
  111. Mitchazenia, en, es-2
  112. Miya, ja, en-2
  113. Moheen, bn, as-1, bpy-1, en-3, hi-1, hif-1
  114. Morgankevinj, en
  115. MPF, en, da-2, de-1, fr-1
  116. Multichill, nl, en-3, de-1, fr-1
  117. Mys 721tx, zh, en-3
  118. Nagy, de, en-3, fr-2, es-1, sv-1
  119. NahidSultan, bn, en-3, bpy-1
  120. Natuur12, nl, en-3, de-1
  121. notafish, fr, en-4, de-3, es-2, it-2
  122. odder, pl, en-4, de-2 (bureaucrat, oversighter)
  123. P199, en, nl, fr-2, tl-2, de-1
  124. Pi.1415926535, en, es-2
  125. Platonides, es, en-2, fr-1
  126. Poco a poco, es, de-4, en-3, fr-2, it-2, pl-2, pt-1
  127. Podzemnik, cs, en-2
  128. Polarlys, de, en-2, fr-1, no-1
  129. Pyb, fr, en-2
  130. Pymouss, fr, en-3, de-2, it-2, he-1
  131. Racconish, fr, en-4
  132. Ragesoss, en, de-1, fr-1
  133. Ra'ike, de, en-2
  134. Rastrojo, es, en-3, fr-2, eo-1
  135. Raymond, de, en-3, nl-1 (oversighter)
  136. Red-tailed hawk, en, es-4, pt-2, ug-1
  137. Regasterios, hu, en-1
  138. Rehman, en, si-1
  139. Reinhard Kraasch, de, en-3
  140. Revi C., ko, en-3
  141. Rimshot, de, en-4, fr-2, it-1
  142. Romaine, nl, en-3, de-2, af-1, fr-1
  143. Rosenzweig, de, en-3, fr-1, la-1
  144. Royalbroil, en, es-1
  145. RP88, en, de-1
  146. Rudolphous, nl, en-3, de-2
  147. Ruthven, it, fr, en-4, es-4, nap-4, ca-2, de-1
  148. Sadads, en, es-3
  149. Sanandros, als, de, en-3, fr-1
  150. Satdeep Gill, pa, en-5, hi-5, es-3, fr-2, fa-1
  151. Shizhao, zh, en-1, ru-1
  152. Spiritia, bg, en-3, ru-2, mk-2, de-1
  153. Sreejithk2000, ml, en-3, hi-3, ta-1, kn-1
  154. Steinsplitter, bar, de-4, it-3, en-1
  155. Stifle, en, ga, fr-2, de-1
  156. Storkk, en, fr-3, de-2, eo-2
  157. Strakhov, es, en-2
  158. TadejM, sl, en-3, de-2, fr-2
  159. Taivo, et, en-3, ru-3, de-1
  160. Teles, pt, en-3, es-2
  161. Themightyquill, en, fr-2, de-1, hu-1
  162. The Squirrel Conspiracy, en
  163. Thibaut120094, fr, en-2, ja-1
  164. Thuresson, sv, en-3, no-2
  165. Tulsi, ne, mai, en-3, hi-2, hif-2, bh-1
  166. Túrelio, de, en-3, es-1
  167. VIGNERON, fr, de-2, en-2, zh-1
  168. Wdwd, de, en-2
  169. Well-Informed Optimist, ru, uk-4, en-3
  170. Wikitanvir, bn, en-3, de-2, as-2, bpy-1
  171. Wutsje, fy, nl, en-3, de-2, fr-1
  172. Yann, fr, en-4, hi-2, gu-1
  173. Yasu, ja, en-2, de-1
  174. Ymblanter, ru, en-3, de-2, fr-2, nl-2, it-1, es-1
  175. Yuval CT, he, en-3
  176. Zzyzx11, en, es-1, fr-1
  177. علاء, ar, en-4, he-1, es-1 (steward)
  178. Abuse filter, (automated account)
  179. CommonsDelinker, (bot) see request
  180. KrinkleBot, (bot) see request

If 180 is not the last number on this list, there may be an error or there are some users assigned temporarily.

Technical

Administrators are users with the technical ability on Wikimedia Commons to:

  • delete and undelete images and other uploaded files, and to view and restore deleted versions
  • delete and undelete pages, and to view and restore deleted revisions
  • protect and unprotect pages, and to edit admin-protected pages
  • block and unblock users, individual IP addresses and IP address ranges
  • edit less-restricted interface messages (see also Commons:Interface administrators)
  • rename files
  • add and remove user groups
  • configure Upload Wizard campaigns
  • delete and undelete specific log entries and revisions of pages
  • import pages from other wikis
  • merge the history of pages
  • modify abuse filters
  • not create redirects from source pages when moving pages
  • override the spoofing checks and title or username blacklist
  • send a message to multiple users at once (massmessage)
  • use higher limits in API queries

These are collectively known as the admin tools.

Community role

Administrators are experienced and trusted members of the Commons community who have taken on additional maintenance work and have been entrusted with the admin tools by public consensus/vote. Different admins have different areas of interest and expertise, but typical admin tasks include determining and closing deletion requests, deleting copyright violations, undeleting files where necessary, protecting Commons against vandalism, and working on templates and other protected pages. Of course, some of these tasks can be done by non-admins as well.

Administrators are expected to understand the goals of this project, and be prepared to work constructively with others towards those ends. Administrators should also understand and follow Commons' policies, and where appropriate, respect community consensus.

Apart from roles which require use of the admin tools, administrators have no special editorial authority by virtue of their position, and in discussions and public votes their contributions are treated in the same way as any ordinary editor. Some admins may become more influential, not due to their position as such, but from the personal trust they may have gained from the community.

Suggestions for administrators

Please read Commons:Guide to adminship.

Removal of administrator rights

Under the de-admin policy, administrator rights may be revoked due to inactivity or misuse of sysop tools. In a de-admin request, normal standards for determining consensus in an RfA do not apply. Instead, "majority consensus" should be used, whereby any consensus to demote of higher than 50% is sufficient to remove the admin.

Apply to become an administrator

All intending administrators must go through this process and submit themselves to RFA, including all ex-administrators who are seeking to return to their previous role.

First, go to Commons:Administrators/Howto and read the information there. Then come back here and make your request in the section below.

  • If someone else nominated you, please accept the nomination by stating "I accept" or something similar, and signing below the nomination itself. The subpage will still need to be transcluded by you or your nominator.


Use the box below, replacing Username with your username:

Voting

Any registered user may vote here although those who have few or no previous edits may not be fully counted. It is preferable you give reasons for both Support and Oppose votes as this will help the closing bureaucrat in their decision. Greater weight is given to an argument, with supporting evidence if needed, than to a simple vote.

Promotion normally requires at least 75% in favour, with a minimum of 8 support votes. Votes from unregistered users are not counted. However, the closing bureaucrat has discretion in judging community consensus, and the decision will not necessarily be based on the raw numbers. Bureaucrats may, at their discretion, extend the period of an RfA if they feel that it will be helpful in better determining community consensus.

  Neutral comments are not counted in the vote totals for the purposes of calculating pass/fail percentages. However, such comments are part of the discussion, may persuade others, and contribute to the closing bureaucrat's understanding of community consensus.

Purge the cache Use the edit link below to edit the transcluded page.

Requests for adminship

When complete, pages listed here should be archived to Commons:Administrators/Archive.

  • Please read Commons:Administrators before voting here. Any logged in user may vote although those who have few or no previous edits may not be fully counted.

No current requests.

Requests for bureaucratship

When complete, pages listed here should be archived to Commons:Bureaucrats/Archive.

  • Please read Commons:Bureaucrats before posting or voting here. Any logged in user may vote although those who have few or no previous edits may not be fully counted.

No current requests.

Requests for CheckUser rights

When complete, pages listed here should be archived to Commons:Checkusers/Archive.

  • Please read Commons:Checkusers before posting or voting here. Any logged in user may vote although those who have few or no previous edits may not be fully counted.

No current requests.

Requests for Oversight rights

When complete, pages listed here should be archived to Commons:Oversighters/Archive.

  • Please read Commons:Oversighters before voting here. Any logged in user may vote, although those who have few or no previous edits may not be fully counted.

Vote

Kadı (talk · contributions · deleted user contributions · recent activity · logs · block log · global contribs · CentralAuth)

Scheduled to end: 00:00, 11 November 2024 (UTC)

Hello I am Kadı. I am an administrator in Commons. Also, I serve as a VRT personnel and global renamer. Sometimes users request oversight actions from me. 3 days ago, I changed visibility of edits on a file because of the uploader's request and I forwarded it to the oversighters but there is no action. I request to be an oversighter, to handle this requests and suppress the edits. Kind regards, --Kadı Message 18:52, 27 October 2024 (UTC)[reply]

Votes

Comments

  • There definitely is a need for another oversighter. I'm not sure if unwanted location data (which is still present in the metadata, file should be overwritten with changed EXIF to purge the unwanted data) merits oversighting rather than hiding it from non-sysops but maybe others can convince me that it's appropriate. Abzeronow (talk) 19:18, 27 October 2024 (UTC)[reply]
  • Like in your last request, I think the community would like to hear how many requests for OS you made in the last 12 months, and how many of them lead to actual oversight. Feel free to add how long it took to have the OS requests processed. (The last 2 or 3 requests I made were processed within few hours, so I don't actually see any problem.) --Krd 07:46, 28 October 2024 (UTC)[reply]
    @Krd, hello. Thanks for your question. Oversight actions are very important which includes users' privacy, and personal datas. I do not remember the number of my requests but 4 days ago I evaluated a request then forwarded to OS mails. 4 days passed, no answer. The request is so basic, it may take approximately 5 minutes. In addition, I do not indicate directly here the requested files for protecting the user's privacy.
    All of us are volunteers here, I do not blame anyone. Commons is a very large project, for example in trwiki we have 4 oversighters, Commons is a very enormous project than trwiki definitely, but in Commons we have only 3. This is definitely not adequate for Commons. I am volunteering here to handle oversight requests faster. In my previous request, you can see this link A steward self assigned OS access to themself in order to handle and emergency action. Kind regards, Kadı Message 09:16, 28 October 2024 (UTC)[reply]
    An emergency is no relevant example. Also, two Commons OS have edited today. Can we rule out that there is just some communication problem? Krd 13:43, 28 October 2024 (UTC)[reply]
    @Krd, I disagree with you. It is a relevant example. Large wikis should use local OS' We are not a small wiki. Kadı Message 15:52, 28 October 2024 (UTC)[reply]
    Even with more local OS, let it be 10, you will have situations where no one is present for an emergency situation. Volunteers are generally not required to meet emergency situation standard, so and emergency example IMHO is moot. Krd 17:42, 28 October 2024 (UTC)[reply]
    @Minorax, Odder, and Raymond: Can you comment if you received the request, and if there is any relevant backlog? --Krd 13:58, 28 October 2024 (UTC)[reply]
    @Krd: I can confirm we did receive the request. There is no backlog, but we place lower priority on requests where content has already been revision deleted by an administrator as opposed to content that's visible on the wiki. I had limited access to e-mail throughout last week but I will action the request shortly. I do have to say that this whole discussion is striking me as quite strange where a user is requesting advanced permissions because one (one!) request they filed hasn't been answered to their satisfaction. As demonstrated in our activity statistics, we get a fairly steady number of requests every month and nearly all of them are answered a in a prompt manner as a few of our more active contributors can attest to. odder (talk) 16:20, 28 October 2024 (UTC)[reply]
    @Odder, as I said before I do not blame anyone. I am a very active user among the Wikimedia projects. My aim is to help oversighters. Best wishes, Kadı Message 16:36, 28 October 2024 (UTC)[reply]
    As someone who has sent a fair deal of oversight requests, I can confirm that 95% of the time, I get a 0-2 hr Response. I don't see any downsides with another oversighter. Normally the overnighters are very active, but I have had reports that took more than 24 hrs (IMHO the max time an oversight request can take), and another OS would be helpful, especially with @Kadı's timezone and editing patterns. As to @GPSLeo's concerns, WMF Legal will make the call as to if being in turkey is a problem, that's not our job. All the Best -- Chuck Talk 16:56, 29 October 2024 (UTC)[reply]
    On my concerns: I just think we need to be more careful with such problems. For the other topic: For real emergencies there is the WMF T&S team and emergency cases do not have to be handled by volunteers. And it is always possible to contact a regular admin in parallel to perform a regular deletion before the suppression by an oversighter. GPSLeo (talk) 18:17, 29 October 2024 (UTC)[reply]
  • You live in country that blocked Wikipedia in the past and the situation regarding democracy did not become better since then. I have the fear that giving you access to such sensitive information you bring you and the project into danger as authorities could try to force you to give information to them. GPSLeo (talk) 16:18, 28 October 2024 (UTC)[reply]
    @GPSLeo, In trwiki we have OS user group. All of the trwiki oversighters do not gave information to anyone. Your fear is irrelevant. Kadı Message 16:34, 28 October 2024 (UTC)[reply]
    There were multiple of such cases in other countries where the WMF had to ban the users to protect them. GPSLeo (talk) 16:51, 28 October 2024 (UTC)[reply]
    @GPSLeo, I am also in VRT. I guarantee that I would never do that. Kadı Message 16:57, 28 October 2024 (UTC)[reply]

See also