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:H:i, j F Y (T)|+5 days}}''
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:H:i, j F Y (T)|+2 week}}''
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:H:i, j F Y (T)|+2 week}}''
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.
I'm volunteering as a renamer as I am interested in working on rename requests. I think I can be a useful member in the team since I am fairly active globally and also have decent linguistic skills, as said at my last request. I'm right now not too intimately acquainted with rename-related stuff other than global rename policy and some reading related to usurpations, so I would intend to gradually familiarize myself and view it as an opportunity to somewhat expand my field of working by gaining new experiences and learning new things along the way. – Svārtava (tɕ) 15:11, 16 June 2025 (UTC)[reply]
Very easy support, and their linguistic skills can benefits renamer team especially on Indic languages that can help processing related rename request, thanks for volunteering. aqurs🍧15:19, 16 June 2025 (UTC)[reply]
Still fairly high rate of getting permissions, but Support regardless - the last refusal was one of the most "down-to-the-wire" refusals I've seen (and even potentially dubious). Leaderboard (talk) 17:12, 16 June 2025 (UTC)[reply]
(Edit conflict.) Support per my support on the last one, I don't think Svartava was hat-collecting even then, and especially not now based on the activity and competence I've seen from him as a metawiki sysop and global sysop. He will definitely make good use of renamer. --Ferien (talk) 17:19, 16 June 2025 (UTC)[reply]
Strong support I do agree 2 months is enough time to get accustomed to GS (the last req) – not that there have been any (actual) issues with the use of GS either. //shb (t • c) 00:04, 17 June 2025 (UTC)[reply]
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.
I am a user who currently lives in China and would need a global IP block exemption to make contributions to metaWiki, thanks, --Zophas (talk) 12:30, 31 May 2025 (UTC)[reply]
I'm sorry for the confusion. I cannot create local accounts in other wikimedia projects such as the Chinese wikiquote (“Auto-creation of a local account failed”) due to a global ban on the IP addresses of the proxies I'm using. Zophas (talk) 12:07, 1 June 2025 (UTC)[reply]
I requested an extension to my existing exemption on 14 June but it was reviewed as 'not done'. The reply stated that the underlying block was no longer in place. However if I try to edit when not logged in, I still get a warning message:
Your account or IP address has been blocked.
136.226.0.0/16, you have been blocked by Xaosflux until 15:47, 17 June 2026, because: Open proxy/Webhost
Will leave for another. It seems that this user sometimes uses a blocked proxy, and sometimes doesn't (such as back when this was reviewed on 14-JUN). Other option may be to not use a proxy, such as by whitelisting our domains in their proxy software. — xaosfluxTalk18:10, 18 June 2025 (UTC)[reply]
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 {{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 -->
}}
<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.
Note that the captcha permission is usually not a vote. However have you tried User:Krinkle/Tools/Global SUL? Which would help you bypass the captcha issue on most of the wikis after a few days, and you seems to have reached autoconfirmed on some large wikis. You are not a file renamer that need to deal with replace related thing a lot, I guess the script above will provide enough help. aqurs🍧12:28, 18 June 2025 (UTC)[reply]
Support regardless - the last refusal was one of the most "down-to-the-wire" refusals I've seen (and even potentially dubious). Leaderboard (talk) 17:12, 16 June 2025 (UTC)
Strong support Should've passed last time. JJPMaster (she/they) 17:18, 16 June 2025 (UTC)
