Wikipedia:Requests for permissions
Archived requests
- Administrator / Bureaucrat / Checkuser / Oversighter
- Rollbacker
- Patroller
- Transwiki Importer
Permissions
There are many kinds of special permissions that users can be granted. These include:
- Rollbacker is a user who can quickly revert changes by other users. See Wikipedia:Rollback feature.
- Flood is a very short-term permission that a user can get from any administrator to make lots of small edits in a row. When using the flood permission, a user’s edits will be hidden by default from Special:RecentChanges.
- Patroller is a user who can review new pages that other users make by marking them "patrolled". Any pages a patroller makes do not have to be reviewed by others.
- Administrator (also called an "admin" or "sysop") is a user who can delete and protect pages and block users. Admins can also grant the rollback, flood and patroller permissions.
- Bureaucrat (also called a "crat") is a user who can grant and revoke the admin and bot permissions.
- Checkuser is a user who can see private information about editors (for example, their IP addresses).
- Oversight is a user who can hide private information from everyone except other oversighters and stewards.
- Transwiki importer is a user who has use of the import tool to move pages here from other projects. This is not to be confused with importer, who can upload XML files using the import tool. *Importer is not granted on this wiki.
- Uploader is a user who can upload files locally on this wiki. This permission is granted temporarily and will be removed once the task is complete.
- IP block exempt is a right given to trusted named users who may edit from an IP address that would otherwise be blocked through no fault of their own.
Adding a new request
Rollbacker
You must be an active member of Simple English Wikipedia, preferably with some experience in reverting vandalism.
Rollback must never be used to revert in edit wars, or to remove good-faith changes. Use the undo feature for this, and give a reason. Rollback does not let you give a reason when reverting. It must only be used to revert bad changes. It can and will be revoked if misused.
Click here to request rollback.
Flood
Requests for the temporary (short-term) flood permission should be made on an administrator’s talk page, on the #wikipedia-simple connect IRC channel, or at the Administrators' noticeboard.
Uploader
Requests for temporary (short-term) file upload permissions should be made on the Administrators' noticeboard. An administrator should be notified once the uploads are done so that the permission can be removed.
Image uploads are not allowed, this should only be requested for uploading other media (such as audio clips)
Administrator
Please read the criteria for adminship before nominating another user or yourself, to make sure the nominated user meets the criteria for becoming an administrator. You may want to look at the archives first so you can see why other people’s requests have succeeded or failed.
Administrator tools are there to better help the community. They do not make certain users better than others. To nominate a candidate for adminship, please follow these instructions:
- In the input box below, replace USERNAME with the username of the person you are nominating for adminship.
- Complete the fields given to you.
- Once the user has accepted, add {{Wikipedia:Requests for adminship/<insert name of person nominated>}} underneath the Current requests for adminship heading below, at the very top of the list.
- Optional: Add {{rfa-notice}} to the candidate's userpage.
Notes: This is not the place to get "constructive feedback from others", if you want feedback from others in a less formal environment, please see Simple Talk. If a candidate is successful, an administrator or bureaucrat should add them to MediaWiki:Gadget-HighlightAdmins.js.
Bureaucrat, Checkuser, or Oversight
For the bureaucrat, checkuser, or oversight permission, a user first needs to be an administrator. There are special requirements at Wikipedia:Criteria for adminship for these users.
Current requests for rollback
- None at this time
Current requests for patroller
- None at this time
Current requests for transwiki importer
- None at this time
Current requests for adminship
- None at this time
Current requests for bureaucratship
- None at this time
Current requests for checkusership
Fehufanga
Hello, I'm Fehufanga. I've been an admin on Simple for just a bit over two years now, and an oversighter for over a year. I am here to nominate myself for checkusership. Over the years, Simple has been faced with serial sockpuppeteers, from vandals using throwaway accounts to UPE account farms creating promotional articles. I have relied on behavioural patterns to determine cases of sockpuppetry. The checkuser tool will help me with dealing with cases of sockpuppetry that are harder to track. I am knowledgeable in computer networks and am familiar with how IP addresses work. As an oversighter, I deal with personal information that cannot be shown publicly, I know better than to disclose these. I am familiar with and have signed the confidentiality agreement. I also have cross-wiki experience that is sometimes necessary when dealing with sockpuppets on this project. Thank you for your consideration.— *Fehufangą ♮ ✉ Talk page 12:52, 17 September 2024 (UTC)
Candidate's acceptance: Self-nomination. — *Fehufangą ♮ ✉ Talk page 12:52, 17 September 2024 (UTC)
Support
- Support. Why not?--BRP ever 12:55, 17 September 2024 (UTC)
- Having another CU & OS admin would be helpful to review blocks made by both CU & OS reasons. I look forward to working with the new CU. MathXplore (talk) 13:09, 17 September 2024 (UTC)
- Weak support Experienced editor, already an oversighter, no reason I can think of to oppose. However, I am a bit sceptical of the need for more CUs, hence why I am weak supporting.- FusionSub (Talk page) (Contributions) 13:12, 17 September 2024 (UTC)
- We really do need another active CU. There is a lot of work to do. fr33kman 18:02, 17 September 2024 (UTC)
- Support Back when I was a global sysop before I was a steward, I found having CU here and GS went well together because I came across a fair few smaller wiki vandals that had also hit simplewiki and was able to confirm them as socks using our DB and then block their small wiki socks and/or report them to the stewards. All the best fr33kman 16:34, 17 September 2024 (UTC)
- Support we apparently need more CUs, and I think that Fehufanga will do great and be helpful. Me Da Wikipedian (talk) 21:45, 17 September 2024 (UTC)
- Support Peterdownunder (talk) 10:25, 18 September 2024 (UTC)
- XXBlackburnXx (talk) 12:59, 18 September 2024 (UTC)
- Support Fehufanga, as an oversighter, has already helped me in an excellent way, so I trust him with private information. ✩ Dream Indigo ✩ 21:02, 18 September 2024 (UTC)
- Changed to Weak support Cactus🌵 spiky ouch 12:23, 18 September 2024 (UTC)
- Support Rather have too many than not enough, and Fr33kman has been busy of late. Fehufanga is already an oversighter, so trust is alrady there. I'll take them at their work on their networking knowledge. Ravensfire (talk) 12:19, 19 September 2024 (UTC)
- 110% Support - Fehufanga does amazing work here blocking the trolls/vandals and so without a shadow of doubt they'd be an asset to the CU team. Honestly can't think of a more perfect candidate for CU than Fehufanga tbh, Easy support. –Davey2010Talk 18:11, 20 September 2024 (UTC)
- Support I feel my initial comment addressing the amount of checkusers we have might have been misinterpreted – Fehufanga is no doubt an excellent candidate, I was simply unsure on expanding our number of checkusers and didn't want to alter the existing team. That being said, I don't think this needs to be addressed by any change to the existing inactive admins policy – the two checkusers inactive for the moment have done an exceptional amount of CheckUser work in the fairly recent past and will likely return to activity in the future. Peterdownunder also commented his intention to resign as checkuser. This was all a minor concern I had, not about Fehufanga of course, that I don't think was a big deal. Fehufanga is already experienced and active in cross-wiki and oversight work and would make a great fit into the checkuser team, this is a very obvious support. --Ferien (talk) 19:44, 20 September 2024 (UTC)
- Support.--Gordonrox24 | Talk 23:41, 21 September 2024 (UTC)
- Jianhui67 T★C 11:49, 22 September 2024 (UTC)
- Support Ternera (talk) 13:22, 22 September 2024 (UTC)
- Support I hope to see you join the team. Operator873 connect 01:27, 25 September 2024 (UTC)
- Support Active administrator, will do very well for a CheckUser. Kurnahusa (talk) 23:59, 27 September 2024 (UTC)
- SupportQueen of Hearts (talk) 06:35, 30 September 2024 (UTC)
- Support I don't see a reason not to grant CU. Justarandomamerican (t • c) 14:29, 5 October 2024 (UTC)
Oppose
Weak oppose per ferien Cactus🌵 spiky ouch 08:01, 18 September 2024 (UTC)- Cactusisme, if you have changed your vote, please move it to the relevant section. --Ferien2 (talk) 13:47, 18 September 2024 (UTC)
Comments
- @Fehufanga Aren't you a global sysop? Cactus🌵 spiky ouch 12:55, 17 September 2024 (UTC)
- @Cactusisme I am, but I feel that that's not too relevant with my chcekusership request.— *Fehufangą ♮ ✉ Talk page 12:59, 17 September 2024 (UTC)
- I know, just a question. Sorry Cactus🌵 spiky ouch 13:00, 17 September 2024 (UTC)
- @Cactusisme Global sysops don't have anything to do with checkusers (global or local).- FusionSub (Talk page) (Contributions) 13:01, 17 September 2024 (UTC)
- No, but the two roles can overlap as I mentioned above. fr33kman 18:01, 17 September 2024 (UTC)
- @Cactusisme I am, but I feel that that's not too relevant with my chcekusership request.— *Fehufangą ♮ ✉ Talk page 12:59, 17 September 2024 (UTC)
- Let me stress that this is a brilliant editor for the role and I do not intend to oppose this request, especially not based on the candidate. If the checkusers say there is a need then I will believe them and agree there is likely a need, but I do understand the concerns from FusionSub. Should this request pass, a majority of administrators will also be checkusers (8 out of 15). I appreciate we are currently at a low administrator count overall over the past few years, but that is still a really large amount. It'd put as as the wiki with the third most checkusers of all Wikimedia projects, tied with MetaWiki, but they have 68 administrators. Itwiki have over 100 admins for 10 checkusers, and enwiki have 850 for 50 checkusers. I don't think it's unreasonable to consider that we would have a disproportionate number of checkusers for our wiki, even accounting for the abuse we get from enwiki. It's not that I don't trust Fehufanga with the CheckUser information of course, but that that sort of information should be in as few people's hands as possible. --Ferien (talk) 19:29, 17 September 2024 (UTC)
- It's not that there aren't enough people with the flag, it's that there isn't enough people using the tool. For RFCU it's basically almost just me and Eptalon servicing the requests. The semi-active admins may be editing but they're not using the tool. Bsadowski1 and Vermont are using the tool regularly but those uses are almost always xwiki/lta/SPI uses. I know Eptalon works full time and he's finding hard to keep up as am i. Each request can take minutes to over an hour to complete. Another CU working the queue will help out a lot. fr33kman 19:38, 17 September 2024 (UTC)
- Perhaps a policy should be written that'd state what criteria would denote an in-active CU and when the tool should be removed as we did with the inactive admins policy. fr33kman 19:43, 17 September 2024 (UTC)
- @Fr33kman the policy globally is
Any user account with CheckUser status that is inactive for more than one year will have their CheckUser access removed
(m:Checkuser policy). If I remember correctly, local policies can be stricter, such as mandating a reelection every six month or so, I believe this is the case in some wikis. — *Fehufangą ♮ ✉ Talk page 22:35, 17 September 2024 (UTC)- Yeah, I know the global policy, I propose it be stricter policy locally. I can assure you that because of our closer relationship with enwiki we get more than should be our statical share of the CU actions per month. When I was a steward I noticed that wikis with similar size and language group gets far less investigations monthly. I think asking each user with the check user flag should be active enough to do at least one time using CU is not to much or unfair to ask in the spirit of our RfCU elections. The people taking park in the election expect that the user would actively use them. And not hold off 9 months or whatever doesn't have the time to take a case on RfCU now and again is unfair. I'm proposing that we RfDCU those haven't been an '''active''' CU during that time has not shown a need for the hat. You shouldn't have it. It's not a beauty contest , (joke)(joke). Seriously every CU could proform a set number of CU actions during 6 months .I proposed [[WP:Inactive administrators]] and that has deadmined a few admins. I hate to say it, "use it or lose it". It's not fair two or sometimes three people on average, have to exclusively service RfCU requests. We're volunteers 🙂 fr33kman 00:55, 18 September 2024 (UTC)
- Agree with the above. I would prefer/like to step down as CU as it is a role that has become more technically complex than I am prepared to deal with. I think it is a tool that requires a more active editor than I am able to do in the foreseeable future. Peterdownunder (talk) 10:30, 18 September 2024 (UTC)
- @Peterdownunder you can always request the removal of your own permissions... Me Da Wikipedian (talk) 22:11, 18 September 2024 (UTC)
- Agree with the above. I would prefer/like to step down as CU as it is a role that has become more technically complex than I am prepared to deal with. I think it is a tool that requires a more active editor than I am able to do in the foreseeable future. Peterdownunder (talk) 10:30, 18 September 2024 (UTC)
- Yeah, I know the global policy, I propose it be stricter policy locally. I can assure you that because of our closer relationship with enwiki we get more than should be our statical share of the CU actions per month. When I was a steward I noticed that wikis with similar size and language group gets far less investigations monthly. I think asking each user with the check user flag should be active enough to do at least one time using CU is not to much or unfair to ask in the spirit of our RfCU elections. The people taking park in the election expect that the user would actively use them. And not hold off 9 months or whatever doesn't have the time to take a case on RfCU now and again is unfair. I'm proposing that we RfDCU those haven't been an '''active''' CU during that time has not shown a need for the hat. You shouldn't have it. It's not a beauty contest , (joke)(joke). Seriously every CU could proform a set number of CU actions during 6 months .I proposed [[WP:Inactive administrators]] and that has deadmined a few admins. I hate to say it, "use it or lose it". It's not fair two or sometimes three people on average, have to exclusively service RfCU requests. We're volunteers 🙂 fr33kman 00:55, 18 September 2024 (UTC)
- @Fr33kman the policy globally is
- Perhaps a policy should be written that'd state what criteria would denote an in-active CU and when the tool should be removed as we did with the inactive admins policy. fr33kman 19:43, 17 September 2024 (UTC)
- It's not that there aren't enough people with the flag, it's that there isn't enough people using the tool. For RFCU it's basically almost just me and Eptalon servicing the requests. The semi-active admins may be editing but they're not using the tool. Bsadowski1 and Vermont are using the tool regularly but those uses are almost always xwiki/lta/SPI uses. I know Eptalon works full time and he's finding hard to keep up as am i. Each request can take minutes to over an hour to complete. Another CU working the queue will help out a lot. fr33kman 19:38, 17 September 2024 (UTC)
Current requests for oversightership
- None at this time
Current requests for removal of rights
- None at this time