The following page documents an officialcross-project policy. This page has been developed and approved by the community and its compliance is mandatory for all users. It must not be modified without priorcommunity approval.

For legal and security reasons, theWikimedia Foundation requirestwo-factor authentication for this role.

Global sysops are highly trusted users with a strong track record of cross-wiki contributions that havesysop andinterface administrator privileges on most public wikis, for the purposes of antivandalism and routine maintenance. They are not users with sysop tools onall wikis and they haveno extra editorial control over content or the local community.

By default, global sysops may use this global user group's permissions on wikis that meet one or both of the following criteria:

• fewer thanten administrators exist;
• fewer thanthree administrators have made a logged action within the past two months.

Bots and the abuse filter pseudo-account are not counted as administrators for the above calculations.

Awiki set is used to specify a list of wikis where global sysops donot have access (list). This wiki set was originally populated in 2010. Since then, wikis that met the criteria have been removed from the wiki set, but wikis that stopped meeting the criteria have not been added.

Projects may be added or removed at their own discretion if they obtain local consensus. Simply informthe stewards of the community's decision.

Most global sysops also haveglobal rollback. Unlike the global sysop rights, global rollbackis truly global. Global sysops are permitted to get global rollback upon request to any steward or atSteward requests/Global permissions.

Should a wiki have an existing local policy regarding the global sysops' scope, global sysops must ensure to conform to the relevant policy before acting.

Links to existing rights policies (where known):

• English Wikibooks:b:en:Wikibooks:Global rights policy#Global sysops
  • Note: English Wikivoyage uses the same local policy:voy:en:Wikivoyage:Administrators#Non-regular administrators
• English Wikinews:n:en:Wikinews:Global rights usage#Global sysops
  • Note: Wikispecies uses the same local policy:species:Wikispecies:Administrators#Global sysops
• MediaWiki:Project:Administrators
  • Note: Wikitech uses the same policy:wikitech:Wikitech:Administrators
• Serbian Wikipedia::w:sr:Википедија:Корисничка права на глобалном нивоу#Глобални администратори
• Simple English Wiktionary:wikt:simple:Wiktionary:Administrators#Non-regular administrators
• Spanish Wikivoyage:voy:es:Wikiviajes:Maquinistas
  • Note: Spanish Wikivoyage allows global sysops (andstewards) to carry out non-controversial admin tasks and use role permissions unless local sysops acted in the past month or it's an emergency.
• Vietnamese Wikipedia:vi:Wikipedia:Quyền truy cập của thành viên#Bảo quản viên toàn cục

Requests for global sysop rights should be placed onSteward requests/Global permissions. The request will be approved by a steward if there is a consensus for the user to become a global sysop after a period of discussion ofno less than two weeks. The discussion is not a vote; comments must present specific points in favor of or against the user's approval.

Continued global sysop access depends on both activityand the continued support of the Wikimedia community.

Inactivity:

Global sysops will automatically lose their access if in six months they've not used the respective rights outside of wikis on which they have local rights.

Vote of confidence:

Any steward may remove a global sysop's rights at any time if they feel the tools have been misused, or if arequest for comment has shown that a significant minority does not trust the global sysop. If this occurs and the global sysop wants the tools back, avote of confidence shall occur, where the global sysop must retain the consensus of the community in order to return their access.

This is the list of permissions, with explanations, whichglobal sysops have. The permissions are nearly identical to those ofregular administrators; however, these permissions apply to any Wikimedia Foundation project that has not opted out of the global sysops' access list. They are not capable of changing any local user rights either (unless they also have appropriate local permissions).

Global sysops must have user pages on every wiki they use their global sysop access on, which provide contact information or link to their primary user page (creation bot available currently). Generally aglobal user page on Meta will cover that requirement, and those users are asked to include auser language declaration ("Babel").

For urgent help from a global sysop, join the IRC channel#wikimedia-gs^connect and type!gs in the channel to get the attention of global sysops.

If a user cannot resolve a dispute by talking to the global sysop, they can place a complaint onTalk:Global sysops, or contact anysteward.

Global sysops may contact each other via theprivate mailing list.

• Last updated:2026-01-08  [edit]

• Global sysops:global permission ·global groups (toolforge) ·member list ·group changelog
• Global groups
• Previous proposals
• Local discussions
• Statistics

• Cross-project policies
• User groups that require two-factor authentication
• User groups
• Global sysops
• Global user groups
• Global maintenance

• Pages using the EasyTimeline extension
• Indefinitely semi-protected