FAMEPedia:User access levels

From FAMEPedia, The free encyclopedia

The user access level of editors affects their abilities to perform specific actions on FAMEPedia. 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 FAMEPedian is logged in, the account's age and edits, and what manually assigned rights the account has.

Anyone can use the basic functionalities of FAMEPedia 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 in 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 | edit source]

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 four days old and has ten 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 FAMEPedia:Requests for permissions and FAMEPedia:Bots/Requests for approval). Others, such as sysop and bureaucrat, are given only after community discussion and consensus at FAMEPedia:Requests for adminship. Users are made members of such groups as oversight and checkuser only with the approval of the Arbitration Committee locally, after signing the Miraheze Limited's confidentiality agreement for nonpublic information.

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.

Permissions requested at Requests for permissions only have local rights on the FAMEPedia wiki. Members of global user groups have rights across all Miraheze Limited wikis, although that access can sometimes be restricted by local wiki policies. Users registered at Miraheze wikis also have registered user rights to other Miraheze wikis if their account is a SUL or unified login account. Both local and global user group membership across Miraheze wikis can be viewed at Special:CentralAuth.

User groups[edit | edit source]

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

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

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 FAMEPedia 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. All users may also query the site API in 500-record batches.

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

You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to a user name, among other benefits.

Registered (new) users[edit | edit source]

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 will be accepted, but will not be immediately visible to non-logged in users until they have been reviewed and approved. They may save books to their userspace, but not the Books namespace. They may also customize their Miraheze interface and its options as they wish - either via Special:Preferences, or by adding personal CSS or JavaScript rules to their common.css or common.js files.

Autoconfirmed and confirmed users[edit | edit source]

You are not logged in, so you are not autoconfirmedYour account is autoconfirmedis not autoconfirmed.

Several actions on FAMEPedia (such as article creation) are restricted to user accounts that are at least 4 days old and have made at least 10 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 FAMEPedia user accounts that are more than four days old and have made at least 10 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), move pages (except for move-protected pages), edit semi-protected pages, and upload files (including new versions of existing files, except for upload-protected files). Edits that they make to a page that is under pending changes protection will be accepted and immediately visible to non-logged in users without requiring review or approval. Autoconfirmed users are no longer required to enter a CAPTCHA for most edits, including, but not limited to, adding external links. Autoconfirmed users may email users that have their allow emails from brand-new users checkbox off. 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.

In some situations, it is necessary for accounts to skip the customary confirmation period and to be confirmed right away. The confirmed group contains the exact same rights as the autoconfirmed pseudo-group, but can be granted by administrators and event coordinators as necessary. It is redundant to grant the confirmed right to an account that is already autoconfirmed since it provides the exact same abilities. To request this permission, see FAMEPedia:Requests for permissions/Confirmed. See Special:ListUsers/confirmed for a list of the 3 confirmed users.

Extended confirmed users[edit | edit source]

You are not logged in, so you are not extended confirmedYour account is extended confirmedis not extended confirmed.

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 and create pages that are under extended confirmed protection. On FAMEPedia, it also enables editors to use the Content Translation tool. 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.

See Special:ListUsers/extendedconfirmed for a list of the 1 extended confirmed users.

Administrators and bureaucrats[edit | edit source]

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

Administrators[edit | edit source]

Administrators, also commonly referred to as "admins" or sometimes "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 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. They are not the staff of the Miraheze Limited and should not be confused with Miraheze system administrators ("sysadmins").

See Special:ListUsers/sysop for a full list of the 8 FAMEPedia administrators.

Bureaucrats[edit | edit source]

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 and remove users from the bureaucrat, administrator, bot, interface administrator and other user groups.

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

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

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

Pending changes reviewer[edit | edit source]

Members of this group can review other users' edits to articles placed under pending changes protection. This right is automatically assigned to administrators.

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

Rollback[edit | edit source]

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 4 rollbackers.

Autopatrolled[edit | edit source]

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.

See Special:ListUsers/autopatrolled for a list of the 8 autopatrolled users.

New page patroller (Patroller)[edit | edit source]

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 1 new page patrollers.

Template editor[edit | edit source]

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 the FAMEPedia 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 1 template editors.

Interface administrators[edit | edit source]

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 FAMEPedia:Bureaucrats' noticeboard.

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

Functionary user levels[edit | edit source]

CheckUser[edit | edit source]

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 FAMEPedia, 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 the Miraheze Limited's non-disclosure 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.

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

Oversight[edit | edit source]

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 Miraheze Limited's non-disclosure 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 | edit source]

Bots[edit | edit source]

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. Bot accounts can query the API in batches of 5,000 rather than 500.

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

Founder[edit | edit source]

The founder group was created on FAMEPedia by Ugo Chima Joseph, without community input, as a unique group for Founders of FAMEPedia. The group gives founders full access to user rights excluding CheckUser, Oversight and interwiki administrators.

Blocked users[edit | edit source]

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 FAMEPedia to be edited.

Blocked users are listed on Special:BlockList.

Indefinitely blocked users[edit | edit source]

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.

Global rights[edit | edit source]

Global rights have effects on all public Miraheze wikis, but their use may be restricted by local policy, see FAMEPedia:Global rights policy. For an automatically generated list of global groups with all their permissions, see Special:GlobalGroupPermissions. For a list of users along with their global groups, see Special:GlobalUsers.

Stewards[edit | edit source]

Stewardship is an elected role, and stewards are appointed globally across all Miraheze wikis.

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 the Miraheze Limited which allows open account creation. This group is set on MetaWiki, and may use meta:Special:Userrights to set permissions on any Miraheze wiki; they may add or remove any user from any group configured on metawiki. 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 sysadmins and Trust and Safety department.

Stewards 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.

Other global user groups[edit | edit source]

Other global groups include sysadmins (system administrators); global sysops. See Global rights policy and meta:User groups for information on these, as well as a full list.

Table[edit | edit source]

  • Generally, bureaucrats on FAMEPedia are also administrators, and so have all the permissions of the sysop user group in addition to those rights from the bureaucrat group. However, this is not a requirement of the MediaWiki software nor is it a formal requirement of the Requests for Bureaucratship process; it is technically possible for a user to be a bureaucrat without also being an admin.
  • Deprecated permissions are either no longer assigned to any group or the group to which they are assigned is no longer populated.

Allows user(s) to… All
Registered accounts[b] Autoconfirmed
and Confirmed
Bots Administrators Bureaucrats other groups[c]
abusefilter-hidden-log View hidden abuse log entries OS
abusefilter-hide-log Hide entries in the abuse log
abusefilter-log View the abuse log ☑Y

abusefilter-log-detail View detailed abuse log entries ☑Y ☑Y ☑Y GR
abusefilter-log-private View edit filters marked as private ☑Y
abusefilter-modify Modify abuse filters EFM
abusefilter-modify-restricted Modify edit filters with restricted actions ☑Y
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 ☑Y
abusefilter-view View non-private abuse filters ☑Y
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 ☑Y ☑Y Researchers
applychangetags Apply tags along with one's changes ☑Y
autoconfirmed Not be affected by IP-based rate limits ☑Y ☑Y ☑Y PCR, GR, IE
autopatrol Automatically mark all edits made by the user as patrolled ☑Y ☑Y AP, GR
autoreview Automatically mark all revisions made by the user as "accepted" ☑Y / ☒N[d] ☑Y ☑Y PCR
bigdelete Delete pages with over 5,000 revisions Stewards
block Block an IP address, user account, or range of IP addresses, from editing ☑Y
blockemail Block a user from sending email ☑Y
bot Edit without their edits showing up in recent changes ☑Y
browsearchive Search deleted pages ☑Y CU, OS, Researchers
centralauth-merge Merge their account ☑Y
changetags Add and remove arbitrary tags on individual revisions and log entries ☑Y ☑Y 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 ☑Y
collectionsaveasuserpage Save books as user subpage ☑Y ☑Y
createaccount Create a new user account for themselves or another user ☑Y ☑Y
createpage Create a new page ☑Y
createpagemainns Create a new mainspace page (users without this right are redirected to the Article Creation Workflow landing page) ☑Y
createtalk Create a new talk page ☑Y ☑Y
delete Delete a page with ≤ 5,000 revisions ☑Y
deletechangetags Delete tags from the database ☑Y
deletedhistory View the history of a deleted page or a user's deleted contributions, provided it is not CSS or JS ☑Y CU, OS, Researchers
delete-redirect Delete single revision redirects PMR
deletedtext View the text of deleted revisions, provided the page is not CSS or JS ☑Y CU, Ombuds, OS, Researchers
deletelogentry Access the RevisionDelete tool and change the public visibility of log entries ☑Y OS
deleterevision Access the RevisionDelete tool and change the public visibility of edit revisions ☑Y

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

Allows user(s) to… All
Registered accounts[b] Autoconfirmed
and Confirmed
Bots Administrators Bureaucrats other groups[c]
nuke Mass delete pages ☑Y
oathauth-enable Enable two-factor authentication ☑Y ☑Y CU, EFM, Founder, IMP, IA, OS, TE, TWI
override-antispoof Allows the creation of accounts with mixed-script, confusing and similar usernames ☑Y ☑Y 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 ☑Y New page reviewers
protect Change protection levels, edit and move protected pages, and edit cascade-protected pages ☑Y IE
purge Purge a page by adding &action=purge to the URL ☑Y
read Read pages ☑Y ☑Y
renameuser Change the name of an existing account Global renamers, Stewards
reupload Overwrite an existing unprotected file ☑Y ☑Y
reupload-own Overwrite existing files uploaded by oneself ☑Y
reupload-shared Override files on the shared media repository locally ☑Y
review Mark revisions as being "accepted" ☑Y PCR
rollback Use a special link to more easily revert a bad edit ☑Y RBK, GR[e]
sendemail E-mail a user (using Special:EmailUser/username) who have associated an email address with themselves ☑Y
skipcaptcha Perform CAPTCHA-triggering actions without having to go through the CAPTCHA ☑Y ☑Y ☑Y GR
spamblacklistlog View the spam blacklist log ☑Y EFH
stablesettings Configure how the latest accepted revision is selected and displayed ☑Y
suppressionlog View private logs OS
suppressredirect Not create a redirect from the old name when moving a page ☑Y ☑Y ☑Y GR[e], 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 ☑Y ☑Y TE, PMR, IE
tboverride-account Override the username blacklist ACCP
templateeditor Edit pages under template protection ☑Y TE, IE
titleblacklistlog View title blacklist log ☑Y

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 ☑Y ☑Y
transcode-status View information about the current transcode activity ☑Y
undelete Undelete a previously deleted page or specific revisions from it, view deleted revisions ☑Y
unwatchedpages View a list of pages which are not on anyone's watchlist ☑Y
upload Upload a media file ☑Y ☑Y
urlshortener-create-url Create short URLs ☑Y ☑Y
userrights Edit all user rights Stewards, Jimbo Wales
viewmyprivateinfo View your own private data (e.g. email address, real name) ☑Y
viewmywatchlist View your own watchlist ☑Y
viewsuppressed View revisions hidden from any user OS
vipsscaler-test Use the VIPS scaling test interface ☑Y
writeapi Use of the write API ☑Y ☑Y ☑Y

Allows user(s) to… All
Registered accounts[b] Autoconfirmed
and Confirmed
Bots Administrators Bureaucrats other groups[c]
  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 FAMEPedia: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 but has no effect since M wikis use mw:Extension:TorBlock instead of the default MediaWiki proxy blocker. 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.[1] Account creations are subject to an IP based limit, set at 6 for M wikis, but users with noratelimit are unaffected.

User access level changes[edit | edit source]

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

Pictogram voting info.svg 1Because 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).

See also[edit | edit source]

Notes[edit | edit source]