Jump to content

Steward requests/Permissions

From Meta, a Wikimedia project coordination wiki
(Redirected from Srp)
Shortcut:
SRP

This page is for requests to have stewards grant or revoke administrator, bureaucrat, checkuser, and oversight rights on Wikimedia projects which do not have a local permissions procedure. Minimum voting requirement are listed here.

Old sections are archived. The list of archives is below.

  • Requests for bot flags are handled at SRB, and requests for global permissions are handled at SRGP.
  • If you are requesting adminship or bureaucratship, and your wiki has a local bureaucrat, submit your request to that user or to the relevant local request page (index).
  • For urgent requests, such as to combat large-scale vandalism on a small wiki, contact a steward in the #wikimedia-stewardsconnect IRC channel. In emergencies, type !steward in the channel to get the attention of stewards. Otherwise, you can type @steward for non-urgent help.

Other than requests to remove your own access or emergencies, please only make requests here after gaining the on-wiki approval of your local community.

Quick navigation: Administrator | Interface administrator | Bureaucrat | CheckUser | Oversight | Removal of access | Miscellaneous | Global permissions

Cross-wiki requests
Meta-Wiki requests

Using this page

[edit]

1. Place the following code at the bottom of the appropriate section below:

==== Username@xxproject ====
{{sr-request
 |status    = <!-- Don't change this line -->
 |domain    = <!-- Such as en.wikibooks -->
 |user name = 
 |discussion= 
}}
(your remarks) ~~~~

2. Fill in the values:

  • domain: the wiki's URL domain (like "ex.wikipedia" or "meta.wikimedia").
  • user name: the name of the user whose rights are to be changed (like "Exampleuser"). In case this is for multiple users, leave this field blank and give a list of these users in your remarks.
  • discussion: a link to the local vote or discussion about the rights change (for example, "[[ex:Wikipedia:Requests_for_adminship#ExampleUser]]"). This should normally be for at least one week, but no more than three weeks (if so, you'll need to restart the process).

3. If anything is missing from your request, a steward will request more information.

Confirmation of signing confidentiality agreement

[edit]

Certain permissions (notably CheckUser and Oversight) additionally require users to sign a confidentiality agreement. Users requesting these permissions must make a request below, and must also sign the confidentiality agreement with the Wikimedia Foundation. The request is placed on hold temporarily, until the receipt has been formally confirmed by the Office.

Requests

[edit]

COPY THE FOLLOWING CODE to the bottom of the appropriate section below:


==== User name@xxproject ====
{{sr-request
  |status     = <!--don't change this line-->
  |domain     =<!-- Such as en.wikibooks -->
  |user name  =
  |discussion = 
}}

Administrator access

[edit]

See Administrator for information about this user group.

  • MediaWiki interface translations are done at translatewiki.net. Please do not request administrator access solely for that purpose; your request will be declined.

  • Stewards: Please use {{Systmp}} for approved temporary requests.

Requests for removal of access should be posted at the section below.

Please start a new discussion about requesting the permission on the local village pump, administrators' noticeboard or a designated page for requesting permissions each time you request or renew adminship.

  • Discussions should be open for seven days. Please request adminship here seven days after discussions started. This page is not the place for any discussions or votes. (For wikis with few active users, it is OK to have no comments.)
  • If you only want adminship for specific tasks, please state for how long and for which tasks you need it. Otherwise stewards will decide whether to assign permanent adminship and the duration of adminship. See Steward requests/Permissions/Minimum voting requirements.

Brwynog@kwwiki

[edit]

I would like to continue being Cornish wikipedia's administrator. It looks like our other administrator has not requested to continue, so it is important that we have someone to patrol edits made Brwynog (talk) 13:08, 13 March 2025 (UTC)[reply]

Done Granted for 1 year to expire on 2026-03-14. To prolong your (interface) adminship, please start another election a few days before your temporary access expires, and after a week post your request again to this page. Thanks. —MdsShakil (talk) 22:49, 14 March 2025 (UTC)[reply]

Kambai Akau@kcgwiktionary

[edit]

Greetings! I am here to apply for Permanent Adminship in the Tyap Wiktionary. I have served once previously and I'm on the second one currently soon to expire. Please find the discussion link above. Thanks and warm regards, Kambai Akau (talk) 21:42, 14 March 2025 (UTC)[reply]

Comment Comment kcg.wiktionary does not have a community large enough for permanent administrators. AramilFeraxa (talk) 10:31, 15 March 2025 (UTC)[reply]
Done Granted for 2 years to expire on 2027-03-15. To prolong your (interface) adminship, please start another election a few days before your temporary access expires, and after a week post your request again to this page. Thanks.. AramilFeraxa (talk) 10:31, 15 March 2025 (UTC)[reply]
Thanks, @AramilFeraxa. I will do that. Warm regards, Kambai Akau (talk) 10:54, 16 March 2025 (UTC)[reply]

Radramboo@id.wikiquote

[edit]

Hello. This request is for renewal administrator access. Regards, Ezagren (talk) 18:27, 15 March 2025 (UTC)[reply]

Done Granted for 1 year to expire on 2026-03-15. To prolong your (interface) adminship, please start another election a few days before your temporary access expires, and after a week post your request again to this page. Thanks.. AramilFeraxa (talk) 22:44, 15 March 2025 (UTC)[reply]

Meruleh@es.wikiversity

[edit]

Seven days ago, I announced my intention to apply for 3-month temp sysop in the Spanish Wikiversity. The project has two admins: one inactive for years and another who contributes sporadically. I aim to support the project by fixing templates, organizing sections, and removing long-standing problematic content, a task I've started with the Global Sysops. My proposal remains open for community comments, but I've received no feedback. Meruleh {talk} 00:47, 17 March 2025 (UTC)[reply]

Interface administrator access

[edit]

See Interface admin for information about this user group.

  • If you are requesting adminship and the interface admin at the same time, you can file one request in administrator section and state you want interface adminship as well.
  • MediaWiki interface translations are done at translatewiki.net. Please do not request interface administrator access solely for that purpose; your request will be declined.
  • Since the end of 2018, all interface administrators are required to have two-factor authentication (2FA) enabled. Please, enable it before posting your request here.

  • Stewards: Please use {{Systmp}} for approved temporary requests.

Requests for removal of access should be posted at the section below.

Please start a new discussion about requesting the permission on the local village pump, administrators' noticeboard or a designated page for requesting permissions each time you request or renew interface adminship.

  • Discussions should be open for seven days. Please request interface adminship here seven days after discussions started. This page is not the place for any discussions or votes. (For wikis with few active users, it is OK to have no comments.)
  • If you only want interface adminship for specific tasks, please state for how long and for which tasks you need it. Otherwise stewards will decide whether to assign permanent interface adminship and the duration of interface adminship. See Steward requests/Permissions/Minimum voting requirements.

Bureaucrat access

[edit]
See Bureaucrat for information about this user group.
  • In principle, requests for temporary bureaucrat access are not granted.
  • A small project does not need bureaucrats. Currently whether a promotion is valid or not is decided by stewards. See here for a guideline.

Requests for removal of access should be posted at the section below.

Turgut46@trwiktionary

[edit]

Turgut46 02:40, 12 March 2025 (UTC)[reply]

Per MVR#Bureaucrat there must be at least 15 votes (the linked discussion has 8 votes, despite announcements via trwiktionary sitenotice [2] and trwiki village pump [3]) and the community must be large enough to even need bureaucrats. With just four admins it doesn't seem like there is a need for crats at trwiktionary (which might change in the future if more admins are getting elected). --Johannnes89 (talk) 08:35, 12 March 2025 (UTC)[reply]
I'm also not really convinced there is a need or a community large enough for local bureaucrats. For reference:
  • In the last 3 years (after the previous local bureaucrat resigned) there have been two rights changes [4], one bot request and one adminship request.
  • MVR has a general requirement of around 15 votes - as mentioned above there have only been eight in this case.
  • There are four permanent admins on the project (three of them appointed while there was still a local bureaucrat so they are reasonably permanent), while MVR generally requires around six permanent administrators.
  • Out of the 67 users who have contributed in the last 30 days only 13 have more than five edits - most of the others are either global renamers/global patrollers or non-community members.
With that being said I'm not really inclined to grant this, though I won't reject either. I'll leave to another steward to give a 2O. EPIC (talk) 09:37, 12 March 2025 (UTC)[reply]
Thank you for your review and detailed response. I understand the concerns regarding the size of the community and the number of votes. However, I would like to highlight a few points in favor of appointing a local bureaucrat for trwiktionary:
One of the core principles of Wikimedia projects is fostering self-sufficient local governance whenever feasible. The absence of a local bureaucrat in trwiktionary means that even minor rights changes—such as granting bot status or handling admin promotions—require the intervention of Meta stewards. While stewards play a crucial role in the broader Wikimedia ecosystem, their primary focus is on global matters, not on the day-to-day operations of individual projects.
By appointing a local bureaucrat, trwiktionary would gain the ability to handle such tasks independently, reducing the need for external intervention. This would not only streamline administrative processes but also empower the local community to take responsibility for its own affairs. In the long run, minimizing reliance on Meta for routine matters contributes to a more sustainable and efficient governance model.
Moreover, the absence of a bureaucrat can create unnecessary delays, as requests must compete for the attention of stewards managing multiple projects.
Considering these factors, granting bureaucrat status would be a step toward strengthening local autonomy and ensuring that trwiktionary can operate smoothly without external stewards.
Best regards. Turgut46 11:02, 12 March 2025 (UTC)[reply]
Just as a note on the point regarding absence of a local bureaucrat - one of the reasons why we are generally restrictive with granting bureaucrat rights is namely because it delays our response times for permission requests for wikis with an inactive bureaucrat. The stewards then have to contact the local bureaucrat to give them a chance to review locally and wait some time for any potential response, before proceeding with doing it ourselves. This has been the case in the past as well, e.g. [5] and [6]. EPIC (talk) 11:07, 12 March 2025 (UTC)[reply]

CheckUser access

[edit]
See CheckUser policy for information about this user group and the policy governing the use of this tool.
  • To request CheckUser information, see Steward requests/Checkuser. This is the place to request CheckUser access.
  • One-time CheckUser access is not permitted and temporary access is only used by Stewards or when the mandate of the CUs has an expiry date specified in local policies.

Johannnes89@meta

[edit]

With unanimous support and minimum number of votes surpassing the requirements in WM:CU, Johannes89 has been elected as a Meta CheckUser. M/ (talk) 07:25, 9 March 2025 (UTC)[reply]

Done and as a steward, there should be no further accesses to handle here. EPIC (talk) 07:33, 9 March 2025 (UTC)[reply]
@EPIC As a Meta admin, are you actually allowed to do this under the homewiki policy? Leaderboard (talk) 09:43, 12 March 2025 (UTC)[reply]
@Leaderboard, first of all, a clear definition of home wiki could help, especially leaving out "non-content wiki" or service wikies such as meta.wiki itself. Please note that this request should also not considered controversial in any way, since votings has been regularly held and has had an unanimous result. Thanks for your consideration, --M/ (talk) 09:49, 12 March 2025 (UTC)[reply]
Meta is generally seen as an exception to the homewiki policy. For requests like this, it's really not possible to completely avoid COI both as 21/34 stewards have Meta adminship and steward work is performed on Meta for the most part, and there really won't be much less of that regardless of who performs the action, and most stewards wouldn't see Meta as a home wiki, mainly because it's not a content wiki. But as M7 mentioned above there shouldn't be much controversy here either way - there was unanimous support, all requirements were met and I did not vote in the request myself. EPIC (talk) 09:51, 12 March 2025 (UTC)[reply]
I didn't know that "Meta is generally seen as an exception to the homewiki policy" actually - that's new to me especially given things like Meta:MSR. Now personally I don't care who promoted the user, but this tends to be a thorny issue for quite a few people here, hence the query. Leaderboard (talk) 10:34, 12 March 2025 (UTC)[reply]
Yeah I don't think it's an unreasonable query from Leaderboard at all. //shb (tc) 10:57, 12 March 2025 (UTC)[reply]
Given how strictly MSR is interpreted, many stewards just run for meta admin to make sure there are no issues with any of their metawiki actions. I don't think this automatically makes meta a home wiki for the 20 stewards (out of 34) with admin permissions on this project.
But the policy never intended to include metawiki, otherwise one could easily argue that all stewards are "active community members" (= home wiki) given how often all stewards visit meta (simply for doing steward work). When I removed Steward requests/Permissions#Svartava@metawiki it would have never occurred to me that the home wiki rule might be involved (although as a self-requested removal it would have been allowed anyway). Johannnes89 (talk) 11:11, 12 March 2025 (UTC)[reply]

柏尾菓子@jawiki

[edit]

This user was appointed as a CheckUser based on the results of a community vote, receiving 48 votes in favor and achieving a 100% confidence rate.Thank you in advance. W.CC (talk) 15:09, 12 March 2025 (UTC)[reply]

 On hold pending on the candidate's signature of the confidentiality agreement for nonpublic information (see instructions) and Wikimedia Foundation confirmation of the same. EPIC (talk) 15:10, 12 March 2025 (UTC)[reply]
Done as the signature was just confirmed. Emailing list admins for remaining stuff. EPIC (talk) 19:52, 14 March 2025 (UTC)[reply]

BetoCG@eswiki

[edit]

With a result of 71 votes in favor and 5 opposes (93.42% support), the user has been chosen as CheckUser by the eswiki community. Please grant him the relevant access. Thanks. --Pólux (talk) 05:08, 18 March 2025 (UTC)[reply]

I've already signed the confidentiality agreement. Thank you. BetoCG (talk) 05:24, 18 March 2025 (UTC)[reply]
Done and congrats! List admins should handle remaining accesses. EPIC (talk) 05:40, 18 March 2025 (UTC)[reply]

Oversight access

[edit]
See Oversight policy for information about this user group and the policy governing the use of this tool.
  • To request to have content oversighted, ask for a steward in #wikimedia-stewardsconnect and contact a steward privately. This section is for requesting access to the Oversight tool.
  • For contact details about oversighters across the wikis, refer to this page.
  • Note that temporary Oversight access is not permitted and temporary status is only used by Stewards .

  • When a new user is assigned to this group, please add them to this list.

Miscellaneous requests

[edit]

Requests for permissions that don't fit in other sections belong here. Importer rights can be granted on most wikis by stewards only. Please gain local community consensus before posting a new section here.

Note that the following types of permissions requests belong on separate pages:

  • SRB — Local or global bot status
  • SRGP — Global permissions

account creator for Ginelly.Q@papwiki

[edit]

(Copied from SRM) — xaosflux Talk 22:48, 18 March 2025 (UTC)[reply]

account creator for Rarends297@papwiki

[edit]

(Copied from SRM) — xaosflux Talk 22:48, 18 March 2025 (UTC)[reply]

Removal of access

[edit]
  • If you're requesting the removal of your own permissions, make sure you're logged in to your account. If you have multiple flags, specify which you want removed. Stewards may delay your request a short time to ensure you have time to rethink your request (see previous discussion on 24 hour delays); the rights will not be restored by stewards once they are removed.
  • To request the removal of another user's permissions, you must gain consensus on the local wiki first. When there is community consensus that the user's access should be removed, provide a link to the discussion, with a brief explanation of the reason for the request, and summarize the results of discussion. However, as bureaucrats of some wikis may remove users from the administrator or bureaucrat group, please see also a separate list of these specific wikis.
  • To request the removal of another user's permissions for inactivity, link to your local inactivity policy. If your site does not have inactivity policy, the global policy Admin activity review applies.
  • See the instructions above for adding new requests. Please post new requests at the bottom of the section.

Helmoony@arwikibooks

[edit]

The user has stated that he is retired and access permission can be removed --Mohanad (talk) 09:17, 11 March 2025 (UTC)[reply]

Since this is part of the AAR process I think this could rather be removed by then at the same time as the other removals are performed, also considering that the user also hasn't specified that they want their rights immediately removed (and for example if they do happen to change their mind until then). I don't object to removing them by now either, though, I'll leave this up to someone else. EPIC (talk) 09:26, 11 March 2025 (UTC)[reply]

The user stated that "You're right, I'm currently retired and have resigned from all my administrative permission except this one. The idea at the time was to facilitate obtaining a local bureaucratic permission for the project. This would put the project under the management of the Arabic community. It seems nothing has moved in a while. You can remove the permission if self-management of the project is no longer a goal. I'd love to talk with you." --Alaa :)..! 19:37, 12 March 2025 (UTC)[reply]

Jamshid Nurkulov@uz.wikipedia

[edit]

Hi, I am one of the administrators of the Uzbek Wikipedia and I voluntarily want to be released from my duties as an administrator. The reason for this is corruption among some administrators and persecution and bullying of dissidents in various Telegram groups. @Lemonaka: mentioned corruption earlier, and he was right. I do not want to be part of this toxic group. If you need more information, you can write to me by email: jamshidnurkulov@gmail.com. Jamshid Nurkulov (talk) 09:24, 12 March 2025 (UTC)[reply]

 On hold for 1 day, standard for resignation of advanced permissions. EPIC (talk) 09:38, 12 March 2025 (UTC)[reply]
I'm sorry…… I didn't have enough competence to stop them... Lemonaka (talk) 10:02, 12 March 2025 (UTC)[reply]
Done. Thank you for your service. AramilFeraxa (talk) 10:03, 13 March 2025 (UTC)[reply]
Extensive discussion on users behaviour rather than the request itself, please discuss locally, or in case you believe there are UCoC violations on any side, refer to U4C --KonstantinaG07 (talk) 12:29, 14 March 2025 (UTC)[reply]
@Lemonaka, if I may ask, do you even speak a word of Uzbek? Just because an admin, who violated no local policy to my knowledge, wasn't desysopped or blocked locally doesn't mean the entire community is corrupt. (By the way, I ultimately supported banning the user).
@Jamshid Nurkulov decided to jump the gun, and that is entirely his right. However, that does not mean there will be no consequences for his egregious policy violations, including sharing (and making sure the link worked) on Wikipedia an audio message sent by another admin in a private group of flatmates (which had absolutely nothing to do with Wikipedia) and running at least two sock accounts through which he published other people's work (one of which is called Vikitarjimonlar klubi, meaning the "Club of Wikitranslators")! Nataev talk 12:21, 13 March 2025 (UTC)[reply]
@Nataev You have two sysops, performing sockpuppetry, one sysop, leaking others' privacy just in a short time. Even I didn't speak a word of Uzbek, this can be learned just from the meta. I believe this community really need the Wikimedia foundation to take action. Lemonaka (talk) 04:10, 14 March 2025 (UTC)[reply]
The fact that we’re actively taking action against violators shows that we’re not ‘corrupt,’ right? You shouldn’t make sweeping accusations just because we’re putting in the effort to address the issues as they arise. Nataev talk 12:20, 14 March 2025 (UTC)[reply]

Ellin Beltz@commonswiki

[edit]

Please remove bureaucrat rights. Thanks! -- CptViraj (talk) 00:17, 13 March 2025 (UTC)[reply]

Done with thanks for their service. EPIC (talk) 04:36, 13 March 2025 (UTC)[reply]

Lkcl_it@itwikivoyage

[edit]

Please remove my advanced rights for inactivity. Thanks Lkcl it (talk) 19:26, 13 March 2025 (UTC)[reply]

 On hold for 1 day, standard for resignation of advanced permissions. EPIC (talk) 19:38, 13 March 2025 (UTC)[reply]
Done Thank you for your service. EPIC (talk) 19:50, 14 March 2025 (UTC)[reply]

Goto@plwiki

[edit]

According to our policy, please remove administrator access due no edit for 365 days. (The policy requires both edit and log action) AramilFeraxa (talk) 16:47, 15 March 2025 (UTC)[reply]

Done with thanks for their service. EPIC (talk) 16:54, 15 March 2025 (UTC)[reply]

JanZerebecki@testwikidata

[edit]

User is globally inactive since more than seven years and has been informed on their talk page twice. Ameisenigel (talk) 18:56, 16 March 2025 (UTC)[reply]

Is there any local inactivity policy or consensus for removal? EPIC (talk) 18:57, 16 March 2025 (UTC)[reply]
There is no policy, so I have started a request at the RFP page. Since this is a test wiki you cannot expect much participation in such a request. --Ameisenigel (talk) 19:05, 16 March 2025 (UTC)[reply]
This is a bit of a complicated case - on one hand there seems to be no local inactivity policy and no participation in the linked request, on the other hand it is indeed a test wiki with no real community and I suppose removing the flag isn't that big of a deal either since it can basically be restored without prejudice. EPIC (talk) 07:01, 17 March 2025 (UTC)[reply]

Beno@plwiki

[edit]

According to our policy, please remove administrator access due no admin log action for 365 days. (The policy requires both edit and log action). Note that [7] shows the last log action on 2024-10-10 but it is redirect delete which can be done by a normal user without admin rights. In fact the last log action was 2024-02-13. AramilFeraxa (talk) 12:10, 17 March 2025 (UTC)[reply]

The admin in question did perform an admin action shortly after this request [8]. Since the edit requirement is otherwise met I think we could consider them active enough per policy at this point, since doing otherwise would be a pretty strict interpretion of policy. EPIC (talk) 13:34, 17 March 2025 (UTC)[reply]
It should be noted here that the policy linked above was adopted in its current form precisely to eliminate reminder notifications (quoting "Od 7 czerwca 2024 po przeprowadzonym głosowaniu zrezygnowano z wysyłania wcześniejszych powiadomień przypominających"). If we assume that performing a logged action or editing after after the notification appears on the Steward requests/Permissions page is sufficient to maintain admin rights, the plwiki community's vote expressed in this vote will be invalidated. --Teukros (talk) 15:28, 17 March 2025 (UTC)[reply]
+ 1 to @Teukros. The recent decision of the community was exactly to tighten the policy (that is the general sentiment expressed in the discussion(s)), explicitly to not allow sysops maintain their tools when they are only active after a notification. Nadzik (talk) 16:15, 17 March 2025 (UTC)[reply]
I hadn't noticed the change in policy. I'll just note that we are currently discussing this specific case and will return here soon. EPIC (talk) 17:25, 17 March 2025 (UTC)[reply]
More than a month has passed since 2025-02-13. Please follow the internal policies adopted by the pl wiki community. SpiderMum (talk) 17:54, 17 March 2025 (UTC)[reply]
Done considering that the community has explicitly expressed that their policy should be for automatic removal and after second opinions among the stewards. EPIC (talk) 17:58, 17 March 2025 (UTC)[reply]

See also

[edit]