Bharatpedia:User access levels

From Bharatpedia, an open encyclopedia
Jump to navigation Jump to search

The user access level of editors affects their abilities to perform specific actions on Bharatpedia. The user access level depends on which rights (also called permissions, user groups, bits, or flags) are assigned to accounts. There are two types of access leveling: automatic, and requested. User access levels are determined by whether the Bharatpedian is logged in, the account's age and edits, and what manually assigned rights the account has.

Anyone can use the basic functionalities of Bharatpedia even if they are not logged in. Unless they are blocked, they may freely edit most pages. Being logged in gives users many advantages, such as having their public IP address hidden and the ability to track one's own contributions. Additionally, once user accounts are more than a certain number of days old and have made more than a certain number of edits, they automatically become autoconfirmed or extended confirmed, allowing the direct creation of articles, the ability to move pages, to edit semi-protected and extended-protected pages, and upload files. Further access levels need to be assigned manually by a user with the appropriate authority. An editor with more experience and good standing can attempt to become an administrator, which provides a large number of advanced permissions. Many other flags for specialized tasks are also available.

Overview[edit]

All visitors to the site, including unregistered users, are part of the '*' group, and all logged-in registered users are also part of the 'user' group. Users are automatically promoted into the autoconfirmed/confirmed users pseudo-group of established users when their account is more than five days old and has twenty edits, and the 'extended confirmed' user group later on.

Other flags are only given upon request; some, such as 'rollbacker', 'pending changes reviewer', or 'bot', are granted unilaterally if the user demonstrates a need for them (see Bharatpedia:Requests for permissions and Bharatpedia:Bots/Requests for approval). Others, such as 'sysop' and 'bureaucrat', are given only after community discussion and consensus at Bharatpedia:Requests for adminship. Users are made members of such groups as 'oversight' and 'checkuser' only with the approval of the Arbitration Committee.

User groups have one or more rights assigned to them; for example, the ipblock-exempt (IP block exemptions) group have the 'ipblock-exempt' and 'torunblocked' rights. All members of a particular user group will have access to these rights. The individual rights that are assigned to user groups are listed at Special:ListGroupRights. Terms like rights, permissions, bits and flags can refer to both user groups and the individual rights assigned to them.

User groups[edit]

The system-generated technical permissions are listed at Special:ListGroupRights.

Unregistered (IP or not logged in) users[edit]

Users who are not logged in are identified by their IP address rather than a user name, whether or not they have already registered an account. They may read all Bharatpedia pages (except restricted special pages), and edit pages that are not protected (including pending changes protected/move-protected articles). They may create talk pages in any talk namespace but need to ask for help to create pages in some parts of the wiki. They cannot upload files or images. They must answer a CAPTCHA if they wish to make an edit which involves the addition of external links, and click a confirm link to purge pages.

Edit screens of unregistered users are headed by a banner that reads:

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you [$1 log in] or [$2 create an account], your edits will be attributed to your username, along with other benefits.

Registered (new) users[edit]

Registered users may immediately e-mail other users if they activate an email address in their user preferences. All logged-in users may mark edits as minor. They may purge pages without a confirmation step, but are still required to answer a CAPTCHA when adding external links. Edits that they make to a page that is under pending changes protection immediately go live, unless other pending changes need to be reviewed. They may save books to their userspace but not the Books namespace.

Autoconfirmed and confirmed users[edit]

Several actions on Bharatpedia are restricted to user accounts that are at least 5 days old and have made at least 20 edits to the encyclopedia. Users who meet these requirements are considered part of the pseudo-group 'autoconfirmed'. The conditions for autoconfirmed status are checked every time a user attempts to perform a restricted action; if they are met, permission is granted automatically by the MediaWiki software. Although the precise requirements for autoconfirmed status vary according to circumstances, most Bharatpedia user accounts that are more than five days old and have made at least 20 edits (including deleted edits) are considered autoconfirmed. However, users with the IP block exemption flag and who are editing through the Tor network are subjected to much stricter autoconfirmed thresholds: 90 days and 100 edits.

Autoconfirmed or confirmed users can create articles (except for create-protected pages), edit semi-protected pages, and upload files (including new versions of existing files, except for upload-protected files). Autoconfirmed users are no longer required to enter a CAPTCHA for most edits, including, but not limited to, adding external links. They also may save books to the Books namespace. In addition, the Edit filter has a number of warning settings that will no longer affect editors who are autoconfirmed.

Extended confirmed users[edit]

A registered editor becomes 'extendedconfirmed' automatically when the account is both at least 30 days old and has made at least 500 edits (including deleted edits). This user access right allows editors to edit pages that are under extended confirmed protection. This access is included and bundled in the 'bot' and 'sysop' (administrator) user groups. This group was primarily created to deal with specific arbitration remedies and community issues; the arbitration committee has since left community-use decisions up to the community.

Administrators and bureaucrats[edit]

Administrators and bureaucrats are requested from pages other than Bharatpedia:Requests for permissions.

Administrators[edit]

Administrators, also commonly referred to as "admins" or "sysops" (system operators), are editors who are granted the rights by the community following a Request for Adminship (RfA). The RfA process involves in-depth and considerable discussion and examination of the candidate's activity and contributions as an editor and are granted the rights by the community consensus. Administrators have exclusive access to a number of tools to allow them to carry out certain functions on the wiki. The tools cover processes such as page deletion, page protection, blocking and unblocking users, and the ability to edit fully protected pages. Administrators also have the ability to grant and remove most access rights to other users (account creator, autopatrolled, confirmed, file mover, edit filter helper, edit filter manager, event coordinator, extended confirmed, IP block exempt, mass message sender, new page reviewer, page mover, pending changes reviewer, rollback, template editor, and AutoWikiBrowser) and to their own alternate accounts. By convention, administrators also normally take responsibility for judging the outcome of certain discussions requiring these technical controls (such as deletions). Administrators are not granted more editorial control over article content than other editors. They are required to follow all policies and guidelines and are held to the same level of accountability as non-administrators.

Bureaucrats[edit]

Bureaucrats are exceptionally trusted editors who have the capability to perform certain actions on other users' accounts. These capabilities are granted by the community following a successful Requests for Bureaucratship (RfB).

Bureaucrats have access to Special:UserRights, enabling them to add users to the 'bureaucrat' group (but not remove them), and add users to and remove users from the 'administrator', 'bot', and 'interface administrator' user groups.

See Special:ListUsers/bureaucrat for a list of the 2 bureaucrats.

Flags granted to users giving access to specialized functions[edit]

Unless otherwise noted, see Bharatpedia:Requests for permissions to request the following rights. Some of these rights are automatically assigned to administrators.

Pending changes reviewer[edit]

Members of this group can review other users' edits to articles placed under pending changes protection. This right is automatically assigned to administrators. Prior to September 2014, this right was known as 'reviewer'.

See Special:ListUsers/reviewer for a list of the 0 reviewers.

Rollback[edit]

Users who are given the rollback flag ('rollbacker' user group) may revert consecutive revisions of an editor using the rollback feature. This right is automatically assigned to administrators.

See Special:ListUsers/rollbacker for a list of the 0 rollbackers.

Autopatrolled[edit]

Members of this group have 'autopatrol', which allows them to have their pages automatically patrolled on the New Pages list. This right is automatically assigned to administrators.

New page reviewer (patroller)[edit]

Members of this group have 'patrol', which allows them to mark pages created by others as patrolled or reviewed. This right is automatically assigned to administrators.

See Special:ListUsers/patroller for a list of the 4 new page reviewers.

File mover[edit]

The file mover user right is intended to allow users experienced in working with files to rename them, subject to policy, with the ease that autoconfirmed users already enjoy when renaming Bharatpedia articles. This right is automatically assigned to administrators.

See Special:ListUsers/filemover for a list of the 0 additional filemovers.

Page mover[edit]

The page mover user right ('extendedmover' user group) is intended to allow users who have demonstrated a good understanding of Bharatpedia page naming system to rename pages and subpages without leaving redirects, subject to policy. They are also able to create and edit editnotices as well as move categories. This right is automatically assigned to administrators.

See Special:ListUsers/extendedmover for a list of the 0 page movers.

Account creator[edit]

The account creator user right ('accountcreator' user group) is intended for users involved in the request an account process (ACC). They are not affected by the 6 account creation limit per day per IP, and can create accounts for other users without restriction. Users in this group can also override the anti-spoof checks on account creation. Additionally, account creators are able to create accounts with names that are otherwise blocked by the title blacklist. This right is automatically assigned to administrators and bureaucrats.

See Special:ListUsers/accountcreator for a list of the 0 account creators.

Event coordinator[edit]

The eventcoordinator flag ('eventcoordinator' user group) is intended for individuals involved with off-wiki outreach events to create accounts for their attendees. Event coordinators are not affected by the 6 account creation limit per day per IP. In addition, they can allow their event attendees to create new articles by temporarily adding newly created accounts to confirmed user group.

See Special:ListUsers/eventcoordinator for a list of the 0 event coordinators.

Template editor[edit]

Users who are given the templateeditor flag ('templateeditor' user group) are allowed to edit pages protected with template protection, as well as create and edit editnotices. Template protection is only applied to pages in the template and module namespaces, as well as a few pages in Bharatpedia namespace. This right is intended to allow experienced template and module coders to make changes without having to request that an administrator make the edits for them. This right is automatically assigned to administrators.

See Special:ListUsers/templateeditor for a list of the 0 template editors.

IP block exemption[edit]

Users who are given the ipblock-exempt flag ('ipblock-exempt' user group) are not affected by autoblocks, blocks of IP addresses and ranges that are made with the "Prevent logged-in users from editing" option enabled, and by Tor blocks.

The flag is intended for trusted users in good standing who are unfortunately affected by such blocks. Requests for this permission may be included with your unblock request. If you are affected by an IP address range block, you must send your unblock request using the Unblock Ticket Request System. If you are trying to edit through a blocked anonymous proxy or a VPN service, you must instead send your request to [email protected], or contact a CheckUser directly.

This right is automatically assigned to administrators and bots. If known, an administrator is also free to grant the right to affected good-faith editors without waiting for an unblock request.

See Special:ListUsers/ipblock-exempt for a list of the 0 affected users.

Edit filter managers[edit]

Members of the edit filter manager group can create, modify, enable, disable, and delete edit filters as well as view private filters and their associated logs. This right is not assigned to administrators by default but they are allowed to grant the user right to themselves. These capabilities can also be granted to non-admins following a successful request at Bharatpedia:Edit filter noticeboard.

See Special:ListUsers/abusefilter for a list of the 0 edit filter managers. All users can check their log entries on the Special:AbuseFilter pages.

Edit filter helpers[edit]

Members of the edit filter helper group can view private edit filters and their associated logs. This access is also included in the administrator groups. These capabilities can also be granted to non-admins following a successful request at Bharatpedia:Edit filter noticeboard.

See Special:ListUsers/abusefilter-helper for a list of the 0 edit filter helpers. All users can check their log entries on the Special:AbuseFilter pages.

Mass message sender[edit]

Members of this group may send messages to multiple users at once. This right is automatically assigned to administrators.

See Special:ListUsers/massmessage-sender for a list of the 0 mass message senders.

Interface administrators[edit]

Users who are given the interface administrator flag ('interface-admin' user group) have the ability to edit site-wide CSS, JavaScript and JSON pages (pages such as MediaWiki:Common.js or MediaWiki:Vector.css, or the gadget pages listed on Special:Gadgets), CSS/JS/JSON pages in another user's userspace, and pages in the Mediawiki namespace. Interface administrator access, along with access to another group that has undelete access is required to view deleted versions of pages only editable by this group. Because it provides the potential to send malicious CSS/JS/JSON code to execute in other users' browsers, this right may only be granted to existing administrators, with two-factor authentication enabled on their accounts. These capabilities can be granted following a successful request at Bharatpedia:Bureaucrats' noticeboard.

See Special:ListUsers/interface-admin for a list of the 2 Interface administrators.

Functionary user levels[edit]

CheckUser[edit]

Users who are given the CheckUser flag ('checkuser' user group) have access to Special:CheckUser, a function page that allows them to view a list of all IP addresses used by a user account to edit Bharatpedia, an extended list of all edits made from an IP (which includes edits that were made by any user accounts while using the specific IP), or a list of all user accounts that have used a given IP address. They also have access to the Checkuser log, which logs each time a Checkuser uses their tools to view any of the information listed. This user right is only granted to exceedingly few users and after a high level of scrutiny and review by the community, and after review and the support of the Arbitration Committee. Users must also be at least 18 years old and have signed our confidentiality agreement for nonpublic information. As CheckUsers have access to deleted revisions, they are also required to have passed an "RFA or RFA-identical process" first.[1]

See Special:ListUsers/checkuser for a list of the 2 CheckUsers.

Oversight[edit]

Users who are given the oversight flag ('oversight' user group) have access to additional functions on the page deletion, revision deletion, and block function pages through which they can hide logs or revisions of pages (partially or entirely) from any form of usual access by all other users, including administrators. They also have access to the suppression log, where they can view actions made by other oversighters, as well as the content of the hidden revisions. This user right is only granted to exceedingly few users and after a high level of scrutiny and review by the community, and after review and the support of Arbitration Committee. Users must also be at least 18 years old and have signed the confidentiality agreement for nonpublic information. Oversighters are also required to have passed a "RfA or RfA-identical process" first. See Special:ListUsers/oversight for a list of the 0 Oversighters.

Other flagged accounts[edit]

Bots[edit]

Accounts used by approved bots to make pre-approved edits can be flagged as such. Bot accounts are automated or semi-automated, the nature of their edits is well defined, and they will be quickly blocked if their actions vary from their given tasks, so they require less scrutiny than human edits.

For this reason, contributions from accounts with the bot flag ('bot' user group) are not displayed in recent changes or watchlists to users who have opted to hide bot edits. Minor edits made by bot accounts to user talk pages do not trigger the "you have new messages" banner.

See Special:ListUsers/bot for a list of the 7 bots.

Copyright violation bots[edit]

A 'copyviobot' is an approved bot that is given the (pagetriage-copyvio) permission, allowing it to use the API to tag pages listed on Special:NewPagesFeed as likely copyright violations.


Blocked users[edit]

Any user account can be blocked, regardless of which user group(s) it belongs to. During the duration of the block, the blocking flag disables the user or IP's existing editing privileges depending on which block options are set by the administrator. A partial block still allows some parts of Bharatpedia to be edited.

Blocked users are listed on Special:BlockList.

Indefinitely blocked users[edit]

In general, rights of editors blocked indefinitely should be left as is. Rights specifically related to the reason for blocking may be removed at the discretion of the blocking or unblocking administrators. This also applies to the user rights of site banned editors.

Stewards[edit]

Users who are members of the 'steward' user group may grant and revoke any permission to or from any user on any wiki operated by Bharatpedia which allows open account creation. Stewards generally act only when there is no user on a particular wiki that can make the necessary change. This includes granting of the 'administrator' or 'bureaucrat' access levels on wikis which do not have any local bureaucrats, and removing such flags if the user resigns or the account is acting maliciously. Stewards are also responsible for granting and revoking access levels such as 'oversight' and 'checkuser', as no other group is capable of making such changes except.

Stewards can also act as checkusers, oversighters, bureaucrats or administrators on wikis which do not have active local members of those groups. For example, if a wiki has a passing need for an edit to be oversighted, a steward can add themselves to the 'oversight' user group on that wiki, perform the necessary function, and then remove themselves from the 'oversight' group using their steward rights.

Most steward actions are logged at meta:Special:Log/rights or meta:Special:Log/gblrights (some go to meta:Stewards/Additional log for global changes). See Special:GlobalUsers/steward or meta:Special:ListUsers/steward for a list of users in this group.

Table[edit]

  • Generally, bureaucrats on Bharatpedia are also administrators, and so have all the permissions of the 'sysop' user group in addition to those rights from the 'bureaucrat' group.
  • Deprecated permissions are either no longer assigned to any group or the group to which they are assigned is no longer populated.

Permission
 
Allows user(s) to… All
users[lower-alpha 1]
Registered accounts[lower-alpha 2] Autoconfirmed
and Confirmed
Bots Administrators Bureaucrats other groups[lower-alpha 3]
abusefilter-hidden-log View hidden abuse log entries OS
abusefilter-hide-log Hide entries in the abuse log
abusefilter-log View the abuse log checkY


abusefilter-log-detail View detailed abuse log entries checkY checkY checkY GR
abusefilter-log-private View edit filters marked as private checkY
abusefilter-modify Modify abuse filters EFM
abusefilter-modify-restricted Modify edit filters with restricted actions checkY
abusefilter-privatedetails View private data (IP addresses) in the abuse log CU
abusefilter-privatedetails-log View the AbuseFilter private details access log
abusefilter-revert Revert all changes by a given abuse filter checkY
abusefilter-view View non-private abuse filters checkY
abusefilter-view-private View edit filters marked as private CU, EFH, EFM, OS
apihighlimits Request API queries in batches of 5,000, rather than 500 checkY checkY Researchers
applychangetags Apply tags along with one's changes checkY
autoconfirmed Not be affected by IP-based rate limits checkY checkY checkY PCR, GR, IE
autopatrol Automatically mark all edits made by the user as patrolled checkY checkY AP, GR
autoreview Automatically mark all revisions made by the user as "accepted" checkY / ☒N[lower-alpha 4] checkY checkY PCR
bigdelete Delete pages with over 5,000 revisions Stewards
block Block an IP address, user account, or range of IP addresses, from editing checkY
blockemail Block a user from sending email checkY
bot Edit without their edits showing up in recent changes checkY
browsearchive Search deleted pages checkY CU, OS, Researchers
centralauth-merge Merge their account checkY
changetags Add and remove arbitrary tags on individual revisions and log entries checkY checkY EFM
checkuser View all IP addresses used by a user account or show all edits from a given IP address CU, Ombuds
checkuser-log View the checkuser log
collectionsaveascommunitypage Save books as community page in the book namespace checkY
collectionsaveasuserpage Save books as user subpage checkY checkY
createaccount Create a new user account for themselves or another user checkY checkY
createpage Create a new page checkY
createpagemainns Create a new mainspace page (users without this right are redirected to the Article Creation Workflow landing page) checkY
createtalk Create a new talk page checkY checkY
delete Delete a page with ≤ 5,000 revisions checkY
deletechangetags Delete tags from the database checkY
deletedhistory View the history of a deleted page or a user's deleted contributions, provided it is not CSS or JS checkY CU, OS, Researchers
deletedtext View the text of deleted revisions, provided the page is not CSS or JS checkY CU, Ombuds, OS, Researchers
deletelogentry Access the RevisionDelete tool and change the public visibility of log entries checkY OS
deleterevision Access the RevisionDelete tool and change the public visibility of edit revisions checkY

Permission
 
Allows user(s) to… All
users[lower-alpha 1]
Registered accounts[lower-alpha 2] Autoconfirmed
and Confirmed
Bots Administrators Bureaucrats other groups[lower-alpha 3]
edit Edit any page which is not protected checkY checkY IE
editcontentmodel Edit the content model of a page checkY TE, IE
editinterface Edit the MediaWiki namespace to affect the interface checkY IA, IE
editmyoptions Edit your own preferences checkY
editmyprivateinfo Edit your own private data (e.g. email address, real name) checkY
editmyusercss Edit your own user .css files checkY
editmyuserjs Edit your own user .js files checkY
editmyuserjson Edit your own user .json files checkY
editmywatchlist Edit your own watchlist checkY
editprotected Edit fully-protected pages checkY IE
editsemiprotected Edit semi-protected pages checkY checkY checkY PCR, GR, IE
editsitecss Edit sitewide .css files IA, IE
editsitejs Edit sitewide .js files
editsitejson Edit sitewide .json files checkY
editusercss Edit other users' .css files IA, IE
edituserjs Edit other users' .js files
edituserjson Edit other users' .json files checkY IA
extendedconfirmed Edit 30/500 protected pages checkY checkY XC, IE
globalblock-whitelist Disable global blocks locally checkY
hideuser Block a username, hiding it from the public OS
import Import pages from other wikis checkY IMP, TWI
importupload Import pages from a locally stored XML file IMP
ipblock-exempt Be unaffected by blocks applied to the user's IP address or a range (CIDR) containing it checkY checkY IPBE
managechangetags Create and (de)activate tags checkY EFM
markbotedits Mark rollback as bot edits, to keep them out of recent changes checkY GR[lower-alpha 5]
massmessage Send a message to multiple users at once checkY MMS
mergehistory Merge the history of pages checkY
minoredit Make an edit marked as 'minor' checkY
move Change the title of a page by moving it checkY checkY PMR, GR
move-categorypages Change the title of a category by moving it checkY checkY PMR
movefile Change the title of a file by moving it checkY FMV
move-rootuserpages Move root user pages checkY checkY
move-subpages Move pages with their subpages checkY checkY PMR
movestable Move pages under pending changes checkY / ☒N[lower-alpha 4] checkY GR
mwoauthmanagemygrants Manage OAuth grants checkY
nominornewtalk Minor edits by this user to user talk pages do not trigger the "you have new messages" banner checkY
noratelimit Not be affected by rate limits checkY checkY checkY ACCP, EVC, GR[lower-alpha 5], Stewards

Permission
 
Allows user(s) to… All
users[lower-alpha 1]
Registered accounts[lower-alpha 2] Autoconfirmed
and Confirmed
Bots Administrators Bureaucrats other groups[lower-alpha 3]
nuke Mass delete pages checkY
oathauth-enable Enable two-factor authentication checkY checkY CU, EFM, Founder, IMP, IA, OS, TE, TWI
override-antispoof Allows the creation of accounts with mixed-script, confusing and similar usernames checkY checkY ACCP
pagetriage-copyvio Tag pages in the Special:NewPagesFeed as likely copyright violations, through the pagetriage-tagcopyvio API Copyright violation bots
patrol State that they have checked a page that appeared in Special:Newpages checkY New page reviewers
protect Change protection levels, edit and move protected pages, and edit cascade-protected pages checkY IE
purge Purge a page by adding &action=purge to the URL checkY
read Read pages checkY checkY
renameuser Change the name of an existing account Global renamers, Stewards
reupload Overwrite an existing unprotected file checkY checkY
reupload-own Overwrite existing files uploaded by oneself checkY
reupload-shared Override files on the shared media repository locally checkY
review Mark revisions as being "accepted" checkY PCR
rollback Use a special link to more easily revert a bad edit checkY RBK, GR[lower-alpha 5]
sendemail E-mail a user (using Special:EmailUser/username) who have associated an email address with themselves checkY
skipcaptcha Perform CAPTCHA-triggering actions without having to go through the CAPTCHA checkY checkY checkY GR
spamblacklistlog View the spam blacklist log checkY EFH
stablesettings Configure how the latest accepted revision is selected and displayed checkY
suppressionlog View private logs OS
suppressredirect Not create a redirect from the old name when moving a page checkY checkY checkY GR[lower-alpha 5], PMR, IE
suppressrevision Access the RevisionDelete tool and change the public and administrator visibility of edit revisions and logs OS
tboverride Override the title blacklist checkY checkY TE, PMR, IE
tboverride-account Override the username blacklist ACCP
templateeditor Edit pages under template protection checkY TE, IE
titleblacklistlog View title blacklist log checkY


torunblocked Bypass automatic blocks of Tor exit nodes IPBE
transcode-reset Reset failed or transcoded videos so they are inserted into the job queue again checkY checkY
transcode-status View information about the current transcode activity checkY
undelete Undelete a previously deleted page or specific revisions from it, view deleted revisions checkY
unwatchedpages View a list of pages which are not on anyone's watchlist checkY
upload Upload a media file checkY checkY
urlshortener-create-url Create short URLs checkY checkY
userrights Edit all user rights Stewards, Jimbo Wales
viewmyprivateinfo View your own private data (e.g. email address, real name) checkY
viewmywatchlist View your own watchlist checkY
viewsuppressed View revisions hidden from any user OS
vipsscaler-test Use the VIPS scaling test interface checkY
writeapi Use of the write API checkY checkY checkY

Permission
 
Allows user(s) to… All
users[lower-alpha 1]
Registered accounts[lower-alpha 2] Autoconfirmed
and Confirmed
Bots Administrators Bureaucrats other groups[lower-alpha 3]
  1. 1.0 1.1 1.2 1.3 Includes IP users. Any permission granted to all users will be inherited by the other user groups.
  2. 2.0 2.1 2.2 2.3 Any permission granted to registered accounts will be inherited by the other (registered) user groups.
  3. 3.0 3.1 3.2 3.3 Any user listed in this column has the relevant permission. Italics indicate a global permission.
  4. 4.0 4.1 Only autoconfirmed
  5. 5.0 5.1 5.2 5.3 Per Bharatpedia:Global rights policy, Global rollbackers are only allowed to use this right in the context of counter-vandalism efforts
  • The userright proxyunbannable is assigned to administrators. Administrators are not exempt from tor blocks, only users in the IP block exemptions usergroup are, due to the torunblocked userright.
  • IPs and new users are limited to 8 edits per minute. Autoconfirmed or confirmed users who are in no usergroup with the noratelimit userright are limited to 8 moves per minute. Rollbackers in the same situation are limited to 100 rollbacks per minute. Account creations are subject to an IP based limit, set at 6 for WMF wikis, but users with noratelimit are unaffected.

User access level changes[edit]

Key to Rights
Yes No
checkY
Key to Project
Local Global Restricted
     
Event coord. Administrator Bureaucrat Steward Founder
Confirmed give checkY checkY checkY checkY checkY
take ☒N
Extended confirmed checkY checkY checkY
New page reviewer checkY checkY checkY
Rollbacker checkY checkY checkY
Autopatrolled checkY checkY checkY
Edit Filter helper,
Edit Filter manager
checkY checkY checkY
Event coordinator checkY checkY checkY
Page mover,
File mover
checkY checkY checkY
Template editor checkY checkY checkY
Mass message sender checkY checkY checkY
IP Block Exempt give checkY ☒N checkY checkY
take checkY
Pending changes reviewer checkY checkY checkY checkY
Account Creator checkY checkY checkY checkY
Bot,
Copyright violation bot
checkY checkY checkY
Administrator,
Interface Administrator
checkY checkY1 checkY
Bureaucrat give checkY checkY checkY
take ☒N
Checkuser, Oversight checkY checkY
Import checkY checkY
Event coord. Administrator Bureaucrat Steward Founder

^1 Because bureaucrats were granted the ability to do this, stewards would refer most ordinary requests for removal of the sysop permission to them, but retain the right to remove the sysop permission when appropriate (such as emergencies or requests from the Arbitration Committee).

Notes[edit]

  1. Cite error: Invalid <ref> tag; no text was provided for refs named wmf