This page hosts requests for global permissions. To make a request, read the relevant policy (global rollback, global sysop, global rename, …) and make a request below. Explain why membership is needed for that group, and detail prior experience or qualifications.
This is not a vote and any active Wikimedia editor may participate in the discussion.
Global rollback and global interface editor requests require no fewer than 5 days of discussion while abuse filter helper and maintainer requests require no fewer than 7 days. Global renamer and global sysop requests require no fewer than 2 weeks of discussion. For requests that are unlikely to pass under any circumstances, they may be closed by a steward without further discussion (after a reasonable amount of input).
Please note that Global rollbackers discussions are not votes. Comments must present specific points in favor of or against a user's approval.
Instructions for making a request
Before requesting, make sure that:
You have sufficient activity to meet the requirements to be allocated the global rollback flag
To make a request
Copy the template below to the bottom of this section and explain of why you need the access and why you're suitable.
=== Global rollback for {{subst:u|{{subst:REVISIONUSER}}}} ===
{{sr-request
|status = <!-- don't change this line -->
|domain = global <!-- don't change this line -->
|user name = {{subst:REVISIONUSER}} <!-- don't change this line unless you're nominating another user -->
}}
::''Not ending before {{subst:#time:j F Y H:i|+5 days}} UTC''
The request will be approved if consensus to do so exists after a period of consideration of no less than 5 days (with rare exceptions, no matter how obvious the result may seem). This is not a vote, and all input is welcome. Stewards will determine whether consensus exists; when doing so it is likely that the weight given to the input of those involved in cross-wiki work will be most influential.
You are logged in on this wiki, and the account is part of your global account;
To make a request
Copy the template below to the bottom of this section and explain of why you need the access and why you're suitable. If you previously requested that right, please add a link to the previous discussion(s).
=== Global sysop for {{subst:u|{{subst:REVISIONUSER}}}} ===
{{sr-request
|status = <!-- don't change this line -->
|domain = global <!-- don't change this line -->
|user name = {{subst:REVISIONUSER}} <!-- don't change this line unless you're nominating another user -->
}}
:''Not ending before {{subst:#time:j F Y H:i|+2 week}} UTC''
The request will be approved if consensus to do so exists after a period of consideration of no less than two weeks (no exceptions are allowed no matter how obvious the result may seem). This is not a vote, and all input is welcome. Stewards will determine whether consensus exists; when doing so it is likely that the weight given to the input of those involved in cross-wiki work will be most influential. Please note: Since 2019 all global sysops are required to have two-factor authentication (2FA) enabled.
When you give someone global rename rights, please add them to the list of global renamers and ask them to subscribe to the global renamers' mailing list.
You are logged in on this wiki, and the account is part of your global account;
You have considered the addition of a user language box to your user page
To make a request
Copy the template below to the bottom of this section and explain of why you need the access and why you're suitable. If you previously requested that right, please add a link to the previous discussion(s).
=== Global rename for {{subst:u|{{subst:REVISIONUSER}}}} ===
{{sr-request
|status = <!-- don't change this line -->
|domain = meta.wikimedia <!-- don't change this line -->
|user name = {{subst:REVISIONUSER}} <!-- don't change this line unless you're nominating another user -->
}}
:''Not ending before {{subst:#time:j F Y H:i|+2 week}} UTC''
The request will be approved if consensus to do so exists after a period of consideration of no less than two weeks (no exceptions are allowed no matter how obvious the result may seem). While all input is welcome, there is a hard 80% support requirement for this role as per the global renamer policy.
Hello everyone. I'd like to request global rename permission to assist rename request. My main focus on bnwiki, meta and as well as others rcquest that's filled by Special:GlobalRenameRequest. I am an crosswiki contributor, an administrator on bnwikibooks, Global rollbacker and VRT permissions agents. I believe, if I get this access then i best use of the tools. Thanks --MdsShakil (talk) 16:49, 23 May 2022 (UTC)[reply]
Comment According to Xtools, you have 6 edits at SRUC and 5 edits at bnwiki renaming page. What would you do if an user who has registered for 2 weeks with 800 edits globally and some extended rights at their homewiki asks for usurpation of an account with 50 edits, all deleted, that was locked 10 years ago for crosswiki abusing? NguoiDungKhongDinhDanh23:49, 23 May 2022 (UTC)[reply]
Thanks for your question. Basically, these two pages are used by global renamers/Stewards and applicants where no other user's assistant is needed, so I did not edit these pages so much.
It's a very new account for usurpation, so this request will initially failed. I think it's better that such this type request (takeover an locked account) is handled by a steward. --MdsShakil (talk) 02:07, 24 May 2022 (UTC)[reply]
Weak support per response to NguoiDungKhongDinhDanh's question, whom I thank for asking a question of MdsShakil. I love to see that in such cases. The answer hit the right points in general terms, but I would also have liked to have seen MdsShakil be a sysop first on the wiki where he's most active (bnwiki). That being said, he's active on Bengali Wikibooks, where there's arguably a greater need for administrators anyway. As well, I know MdsShakil from Miraheze, where they have exhibited technical proficiency and a good understanding of Miraheze global policies. Dmehus (talk) 02:23, 24 May 2022 (UTC)[reply]
Note that I weakly supported due to MdsShakil's inexperience at pages he intended to work on, and that he answered about how the request would end, not what he would do in such a situation. NguoiDungKhongDinhDanh02:28, 24 May 2022 (UTC)[reply]
Question: How would you handle a normal vanishing request (from checks to processing)? Also as you intend to help on meta, how would you handle an usurpation request? Thanks for the answer. ‐‐1997kB (talk) 06:03, 24 May 2022 (UTC)[reply]
Usually, a request for vanishing is made through a special page or VRTS, so such a request can be found here. In the case of a request made through special page, the user does not need to do additional verification, but in the case of an email in VRT, the information that can be guaranteed to confirm the ownership of the applicant's account must be there.
After confirming the ownership, it is necessary to see if there is a valid reason for the request, if there is a good reason, then I will rename the user as 'Rename user xxxxxxxxx', in which case the redirect is usually not kept.
In the case of usurpation, First I will check the applicant is a significant contributor, an old user or h/she is not blocked anywhere and also their is an valid reason for usurpation. Then i will check the target account, if this account has significant/much valid contribution in any project then this rcquest is rejected.
If there are no significant/Not so much valid contribution, then I will send him/her an message at their homewiki and an email in their own language (if available) by using {{Usurpation requested}}, and hold the request for 30 days. If the user does not object later, then the request will be completed. --MdsShakil (talk) 14:55, 24 May 2022 (UTC)[reply]
Thanks for the answers, looks satisfying, so you have my Support. Just some suggestion, requests in queue usually requires more checks as queue interface itself doesn't offer much tools. Like, requests in the queue show very ambiguous indication if the target user had been used previously, so we need to check those manually or user is involved in some conflict locally and renamer handling is not from that project, so we tend to leave those requests for renamers from that project.
Your request might be rejected if you don't follow the instructions. Please review Global IP block exemption. You may request Global IP block exemption via stewardswikimedia.org if you can not edit this page.
Please note: Global IP block exemption does NOT make one immune to locally-created blocks of any sort, only global blocks.
If you want to edit the Chinese Wikipedia, usually global IP block exemptions will not help you. Please see this instruction to request a local IP block exemption.
Instructions for making a request
Before requesting global IP block exemption, make sure that:
You are logged in on this wiki, and the account is part of your global account;
To request global IP block exemption
Copy the template below to the bottom of this section and explain why you need the access and why you're suitable. If needed, link to relevant discussions.
=== Global IP block exempt for {{subst:u|{{subst:REVISIONUSER}}}} ===
{{sr-request
|status = <!--don't change this line-->
|domain = global<!--don't change this line-->
|user name = {{subst:REVISIONUSER}}
}}
<Add an explanation here>, thanks, --~~~~
The request will be approved if there is demonstrated need for the permission, such as bypassing a global block from someone who is not the intended target.
Hey i'm running a bot on Hebrew wikipedia (you can see source code here). The bot supposed to run once a day. I want to run it on AWS Lambda platform that banned with range block (54.190.0.0/16), thanks, Sapper-bot (talk) 08:42, 24 May 2022 (UTC)[reply]
@Sapper-bot: Hello! You have local IP block exempt on the Hebrew Wikipedia, so you are free from this block. Do you want to use your bot in any other project? If no, a local exempt is enough and a global one is not needed. stanglavine msg17:31, 24 May 2022 (UTC)[reply]
I asked for IP block exempt In Hebrew Wikipedia, the admin gave it for two weeks and said that for global block it's better to ask for global IP block exempt. You can see the discussion hereSapper-bot (talk) 20:35, 24 May 2022 (UTC)[reply]
Bots should not be making their own requests, this should come from an operator. With this being only used on a single project that is capable of managing their own IPBE's that seems to be the best course of action to me. — xaosfluxTalk13:21, 25 May 2022 (UTC)[reply]
@החבלן yes, you should ask - for that account. Not use that account to ask. No change in my suggestion that this should just be handled at hewiki. — xaosfluxTalk19:51, 25 May 2022 (UTC)[reply]
@החבלן: Hello, as you can see here a local exempt is enough to deal with a global block. A global exempt is recommended only for cases involving multiple projects, when multiple local exempts are less convenient. Apparently, that is not your case, so I see no reason to set a global exempt for your bot. I suggest you to ask some admin of the Hebrew Wikipedia to extend your local exempt there. Let me know if you have any question, I'll close this request as not done at some point tomorrow or after if you don't have any relevant new input on it. Regards, stanglavine msg22:09, 25 May 2022 (UTC)[reply]
I'm the sysop who sent the "User:החבלן" to ask for a global exemption, because the block is global. The Hebrew Wikipedia prefers to give a local exemption as narrowly as possible, because a local permission bypasses automatic blockages or IP blocks that have been extended to registered users as well. The rationale behind this practice is so that if there is a block that has been activated incorrectly, then it will be brought to our attention through veteran users, and thus we will know how to release it. Global authorization does not bypass local blockages, so I sent it requesting a global exemption. Is there a ban on giving the "החבלן" the permission?
For what it's worth, this seems fine to me. The user's articulated a clear use case, and has the support of a Hebrew Wikipedia administrator. It's conceivable this bot may operate across multiple Hebrew Wikimedia project wikis. Dmehus (talk) 07:02, 29 May 2022 (UTC)[reply]
As part of the policy, gipbe requires edits on multiple projects. Doesn't seem to be the case here. Hence, a local ipbe would do. If there are evidence of multiwiki edits, gipbe would be reasonable. Matanya (talk) 07:08, 29 May 2022 (UTC)[reply]
Not done@דגש and החבלן: Hi, as I said before and Matanya too, GIPBE was designed to deal with situations involving multiple-projects and, if you (as local community/admin team) have the practice to set "local exemption as narrowly as possible", we are even more restricted about GIPBE because they are global rights and, because of that, more sensitive than local IPBE. So, since there is no indication of global contributions for that account at the present moment, a GIPBE is not reasonable now. Of course, you are free to request again in the future if necessary, but for now there is no reason to set GIPBE for your bot. Hope this makes sense to you. Regards, stanglavine msg14:50, 3 June 2022 (UTC)[reply]
Requests for 2 Factor Auth tester permissions
Please be sure to follow the instructions below:
Your request might be rejected if you don't follow the instructions.
Testing this service may result in the loss of your access and is not recommended for inexperienced users.
Instructions for making a request
Before requesting 2FA tester global permissions, make sure that:
Your request might be rejected if you don't follow the instructions.
Instructions for making a request
Before requesting additional global permissions, make sure that:
You are logged in on this wiki;
No specific section on this page exists for the permission you want to request;
To request additional global permissions
Copy the template below to the bottom of this section and explain what kind of access you need and why. If needed, link to relevant discussions. If you hold, or have previously held, the right and are asking for either a renewal or revival of that right, please add a link to the previous discussion.
=== <Add requested permission here> for [[User:Foo|Foo]] ===
{{sr-request
|status = <!--don't change this line-->
|domain = global<!--don't change this line-->
|user name = Username
|discussion=
}}
<Add an explanation here>, thanks, --~~~~
The request will be approved if consensus to do so exists after a short period of consideration. A steward will review the request.
remove global VRT permissions agents for Palnatoke
Comment According to Xtools, you have 6 edits at SRUC and 5 edits at bnwiki renaming page. What would you do if an user who has registered for 2 weeks with 800 edits globally and some extended rights at their homewiki asks for usurpation of an account with 50 edits, all deleted, that was locked 10 years ago for crosswiki abusing? NguoiDungKhongDinhDanh 23:49, 23 May 2022 (UTC)
Weak support NguoiDungKhongDinhDanh 02:17, 24 May 2022 (UTC)
Support Trusted user. AlPaD (talk) 04:22, 24 May 2022 (UTC)
Question: How would you handle a normal vanishing request (from checks to processing)? Also as you intend to help on meta, how would you handle an usurpation request? Thanks for the answer. ‐‐1997kB (talk) 06:03, 24 May 2022 (UTC)
Strong support — SHEIKH (Talk) 15:01, 24 May 2022 (UTC)
Not done @דגש and החבלן: Hi, as I said before and Matanya too, GIPBE was designed to deal with situations involving multiple-projects and, if you (as local community/admin team) have the practice to set "local exemption as narrowly as possible", we are even more restricted about GIPBE because they are global rights and, because of that, more sensitive than local IPBE. So, since there is no indication of global contributions for that account at the present moment, a GIPBE is not reasonable now. Of course, you are free to request again in the future if necessary, but for now there is no reason to set GIPBE for your bot. Hope this makes sense to you. Regards, stanglavine msg 14:50, 3 June 2022 (UTC)
