Page semi-protected

Wikipedia:Protection policy

Source: Wikipedia, the free encyclopedia.

Gold padlock
Fully-protected
Goldlock
Brown padlock
Interface protected
Redlock
Pink padlock
Template-protected
Pinklock
Silver padlock
Semi-protected
Silverlock
Blue padlock
Create protected
Skybluelock
Green padlock
Move protected
Greenlock
Purple padlock
Upload protected
Purplelock
White padlock
Pending changes protected
Whitelock
Dark blue padlock
Extended confirmed protected
Bluelock
Black padlock
Protected by Office
Blacklock
Turquoise padlock
Cascade protected
Turquoiselock

In some circumstances, pages may need to be protected from modification by certain groups of editors. Pages are protected when a specific damaging event has been identified that can not be prevented through other means such as a block. Otherwise, Wikipedia is built on the principle that anyone can edit it, and it therefore aims to have as many of its pages as possible open for public editing so that anyone can add material and correct errors. This policy states in detail the protection types and procedures for page protection and unprotection and when each protection should and should not be applied.

Protection is a technical restriction applied only by

wikitext
) of the page can still be viewed and copied by anyone.

A protected page is marked at its top right by a padlock icon, usually added by the {{

pp-protected
}} template.

Pre-emptive protection

Applying page protection as a preemptive measure is contrary to the open nature of Wikipedia and is generally not allowed if applied solely for these reasons. However, brief periods of an appropriate and reasonable protection level are allowed in situations where blatant vandalism, disruption, or abuse is occurring by multiple users and at a level of frequency that requires its use in order to stop it. The duration of the protection should be set as short as possible, and the protection level should be set to the lowest restriction needed in order to stop the disruption while still allowing productive editors to make changes.

Types of protection

The following technical options are available to administrators for protecting different actions to pages:

  • Edit protection protects the page from being edited.
  • Move protection protects the page from being
    moved or renamed
    .
  • Creation protection prevents a page (normally a previously deleted one) from being created (also known as "salting").
  • Upload protection prevents new versions of a file from being
    uploaded
    , but it does not prevent editing to the file's description page (unless edit protection is applied).

The following technical options are available to administrators for adding protection levels to the different actions to pages:

  • Pending changes protection (only available for edit protection) requires any edits made to the page by unregistered users and accounts that are not confirmed to be approved by a pending changes reviewer or an administrator before the changes become visible to readers who are not logged in.
  • Semi-protection prevents the action by unregistered users and users with accounts that are not confirmed.
  • Extended confirmed protection, also known as 30/500 protection, prevents the action if the user's account has not yet reached at least 30 days of tenure, and has not made at least 500 edits on the English Wikipedia. In most cases, it should not be a protection level of first resort, and should be used where semi-protection has proven to be ineffective. Activation or application of this protection level is logged at the
    Administrators' noticeboard
    .
  • Template protection prevents the action by everyone except template editors and administrators (who have this right as part of their toolset).
  • Full protection prevents the action by everyone except administrators.

Any type of protection (with the exception of

edit request. From there, if the requested changes are uncontroversial or if there is consensus
for them, the changes can be carried out by a user who can edit the page.

Except in the case of

Requests for unprotection. Note that such requests will normally be declined if the protecting administrator is active and was not consulted first. A log of protections and unprotections is available at Special:Log/protect
.

Interaction of Wikipedia user groups and page protection levels
  Unregistered or newly registered Confirmed or autoconfirmed Extended confirmed Template editor Admin Interface admin Appropriate for
No protection normal editing The vast majority of pages. This is the default protection level.
all users can edit
Edits by unregistered or new editors (and any subsequent edits by anyone) are hidden from readers who are not logged in, until reviewed by a pending changes reviewer or admin. Logged-in editors see all edits, whether accepted or not.
Infrequently edited pages with high levels of vandalism,
BLP
violations, edit-warring, or other disruption from unregistered and new users.
cannot edit normal editing Pages that have been persistently vandalized by anonymous and registered users. Some highly visible templates and modules.
cannot edit normal editing* Specific topic areas authorized by ArbCom, pages where semi-protection has failed, or high-risk templates where template protection would be too restrictive.
cannot edit normal editing High-risk or very-frequently used templates and modules. Some high-risk pages outside of template space.
cannot edit normal editing Pages with persistent disruption from extended confirmed accounts. Critical templates and modules.
cannot edit normal editing Scripts, stylesheets, and similar objects central to operation of the site or that are in other editors' user spaces.
* In order to edit through extended confirmed protection, a template editor must also be extended confirmed, but in practice this is essentially always the case.
Other modes of protection:


Semi-protection

Silver padlock

Semi-protected pages cannot be edited by

biographies of living persons who have had a recent high level of media interest. An alternative to semi-protection is pending changes
, which is sometimes favored when an article is being vandalized regularly, but otherwise receives a low amount of editing.

Such users can request edits to a semi-protected page by proposing them on its talk page, using the {{

Wikipedia:Requests for page protection instead. New users may also request the confirmed user right at Wikipedia:Requests for permissions/Confirmed
.

Guidance for administrators

Administrators may apply indefinite semi-protection to pages that are subject to heavy and persistent vandalism or violations of content policy (such as biographies of living persons, neutral point of view). Semi-protection should not be used as a preemptive measure against vandalism that has not yet occurred or to privilege registered users over unregistered users in (valid) content disputes.

In addition, administrators may apply temporary semi-protection on pages that are:

  • Subject to significant but temporary vandalism or disruption (for example, due to media attention) if blocking individual users is not a feasible option.
  • Subject to edit warring if all parties involved are unregistered or new editors. This does not apply when autoconfirmed users are involved.
  • Subject to
    dynamic IP
    allocation, or other address-changing schemes.
  • Article discussion pages, if they have been subject to persistent disruption. Such protection should be used sparingly because it prevents unregistered and newly registered users from participating in discussions. A page and its talk page should not normally be protected at the same time. If a page and its talk page are both protected, the talk page should direct affected editors to
    Wikipedia:Request for edit
    through the use of a non-iconified page protection template, to ensure that no editor is entirely prevented from contributing.
  • Protection should be used sparingly on the talk pages of blocked users, including IP addresses. Instead the user should be re-blocked with talk page editing disallowed. When required, or when re-blocking without talk page editing allowed is unsuccessful, protection should be implemented for only a brief period not exceeding the duration of the block.

Today's featured article may be semi-protected just like any other article. However since the article is subject to sudden spurts of vandalism during certain times of day, administrators should semi-protect it for brief periods of time in most instances. For the former guideline, see Wikipedia:Main Page featured article protection.

Pending changes protection

White padlock

Pending changes protection is a tool used to suppress

pending changes reviewer
.

When a page under pending changes protection is edited by an

unregistered (IP addresses) editor or a new user, the edit is not directly visible to the majority of Wikipedia readers, until it is reviewed and accepted by an editor with the pending changes reviewer right. When a page under pending changes protection is edited by an autoconfirmed user
, the edit will be immediately visible to Wikipedia readers, unless there are pending edits waiting to be reviewed.

Pending changes are visible in the page history, where they are marked as pending review. Readers that are not logged in (the vast majority of readers) are shown the latest accepted version of the page; logged-in users see the latest version of the page, with all changes (reviewed or not) applied. When editors who are not reviewers make changes to an article with unreviewed pending changes, their edits are also marked as pending and are not visible to most readers.

A user who clicks "edit this page" is always, at that point, shown the latest version of the page for editing regardless of whether the user is logged in or not.

Reviewing of pending changes should be resolved within reasonable time limits.

When to apply pending changes protection

Pending changes may be used to protect articles against:

Pending changes protection should not be used as a preemptive measure against violations that have not yet occurred. Like semi-protection, PC protection should never be used in genuine content disputes, where there is a risk of placing a particular group of editors (unregistered users) at a disadvantage. Pending changes protection should not be used on articles with a very high edit rate, even if they meet the aforementioned criteria. Instead, semi-protection should be considered.

In addition, administrators may apply temporary pending changes protection on pages that are subject to significant but temporary vandalism or disruption (for example, due to media attention) when blocking individual users is not a feasible option. As with other forms of protection, the time frame of the protection should be proportional to the problem. Indefinite PC protection should be used only in cases of severe long-term disruption.

Removal of pending changes protection can be requested of any administrator, or at

requests for unprotection
.

The reviewing process is described in detail at Wikipedia:Reviewing pending changes.

Creation protection (salting)

Blue padlock

Administrators can prevent the creation of pages. This type of protection is useful for pages that have been

historical lists
).

Pre-emptive restrictions on new article titles are instituted through the title blacklist system, which allows for more flexible protection with support for substrings and regular expressions.

Pages that have been creation-protected are sometimes referred to as "salted". Editors wishing to re-create a salted title with appropriate content should either contact an administrator (preferably the protecting administrator), file a request at Wikipedia:Requests for page protection#Current requests for reduction in protection level, or use the deletion review process. To make a convincing case for re-creation, it is helpful to show a draft version of the intended article when filing a request.

Administrators should choose the appropriate level of create protection—autoconfirmed, extended-confirmed,

mainspace
; thus, semi-creation protection should be rare, used only for protection of pages outside of mainspace.

While creation-protection is usually permanent, temporary creation protection may be applied if a page is repeatedly recreated by a single user (or

sockpuppets
of that user, if applicable).

Move protection

Green padlock

Move-protected pages, or more technically, fully move-protected pages, cannot be moved to a new title except by an administrator. Move protection is commonly applied to:

Fully edit-protected pages are also implicitly move-protected.

As with full edit protection, protection because of edit warring should not be considered an endorsement of the current name. When move protection is applied during a requested move discussion, the page should be protected at the location it was at when the move request was started.

All

files are implicitly move-protected; only file movers
and administrators can rename files.

Upload protection

Purple padlock

Upload-protected files, or more technically, fully upload-protected files, cannot be replaced with new versions except by an administrator. Upload protection does not protect file pages from editing. It may be applied by an administrator to:

  • Files subject to persistent upload vandalism.
  • Files subject to a dispute between editors.
  • Files that should not be replaced, such as images used in the interface or transcluded to the main page.
  • Files with common or generic names. (e.g., File:Map.png)

As with full edit protection, administrators should avoid favoring one version over another, and protection should not be considered an endorsement of the current version. An exception to this rule is when they are protected due to upload vandalism.

Extended confirmed protection

Dark blue padlock

Extended confirmed protection, also known as 30/500 protection, only allows edits by editors with the extended confirmed user access level, granted automatically to registered users with at least 30 days tenure and at least 500 edits.

As escalation from semi-protection

Where semi-protection has proven to be ineffective, administrators may use extended confirmed protection to combat disruption (such as

High-risk templates may be extended-confirmed protected at administrator discretion when template protection would be too restrictive and semi-protection would be ineffective to stop widespread disruption.[3]

As general sanction enforcement

Two topic areas are under

community general sanction. The extended confirmed restriction slightly differs from the earlier "30/500 restriction", which was independent of extended confirmed status. Administrators are authorized to enforce this restriction through extended confirmed protection or any other means.[4]
It applies to:

Logging and edit requests

As of September 23, 2016, a bot posts a notification in a subsection of AN when this protection level is used.[9] Any protection made as arbitration enforcement must be logged at Wikipedia:Arbitration enforcement log. A full list of the 4058 pages under 30/500 protection can be found here.

Users can request edits to an extended confirmed-protected page by proposing them on its talk page, using the {{Edit extended-protected}} template if necessary to gain attention.

Template protection

Pink padlock

A template-protected page can be edited only by administrators or users in the Template editors group. This protection level should be used almost exclusively on

modules
. In cases where pages in other namespaces become transcluded to a very high degree, this protection level is also valid.

This is a protection level

extended confirmed protection or lower may be applied to high risk templates that the general editing community still needs to edit regularly. A full list of the pages under template protection can be found here
.

Editors may request edits to a template-protected page by proposing them on its talk page, using the {{Edit template-protected}} template if necessary to gain attention.

Full protection

Gold padlock

A fully protected page cannot be edited or moved by anyone except administrators. The protection may be for a specified time or may be indefinite.

Modifications to a fully protected page can be proposed on its talk page (or at another appropriate forum) for discussion. Administrators can make changes to the protected article reflecting consensus. Placing the {{Edit fully-protected}} template on the talk page will draw the attention of administrators for implementing uncontroversial changes.

Content disputes

While content disputes and

uninvolved administrators, allowing normal page editing by other editors at the same time, the protection policy provides an alternative approach as administrators have the discretion to temporarily fully protect an article to end an ongoing edit war. This approach may better suit multi-party disputes and contentious content, as it makes talk page consensus a requirement for implementation of requested edits
.

When protecting a page because of a content dispute, administrators have a duty to avoid protecting a version that contains policy-violating content, such as

stable
, or pre-edit-war version.

Fully protected pages may not be edited except to make changes that are uncontroversial or for which there is clear consensus. Editors convinced that the protected version of an article contains policy-violating content, or that protection has rewarded edit warring or disruption by establishing a contentious revision, may identify a stable version prior to the edit war and request reversion to that version. Before making such a request, editors should consider how independent editors might view the suggestion and recognize that continuing an edit war is grounds for being blocked.

Administrators who have made substantive content changes to an article are considered

involved
and must not use their advanced permissions to further their own positions. When involved in a dispute, it is almost always wisest to respect the editing policies that bind all editors and call for input from an uninvolved administrator, rather than to invite controversy by acting unilaterally.

"History only" review

If a deleted page is going through

restore the page, blank it or replace the contents with {{Temporarily undeleted}} template or a similar notice, and fully protect the page to prevent further editing. The previous contents of the page are then accessible to everyone via the page history
.

Protected generic file names

Generic file names such as File:Photo.jpg, File:Example.jpg, File:Map.jpg, and File:Sound.wav are fully protected to prevent new versions from being uploaded. Furthermore, File:Map.jpg and File:Sound.wav are salted.

Permanent protection

Brown padlock

Administrators cannot change or remove the protection for some areas on Wikipedia, which are permanently protected by the MediaWiki software:

  • Edits to the
    interface administrators
    .
    • Edits to system-wide CSS and JavaScript pages such as
      interface administrators
      .
  • Edits to personal CSS and JavaScript pages such as User:Example/monobook.css and User:Example/cologneblue.js are restricted to the associated user and interface administrators. Interface administrators may edit these pages, for example, to remove a user script that has been used in an inappropriate way. Administrators may delete (but not edit or restore) these pages.
  • Edits to personal JSON pages such as User:Example/data.json are restricted to the associated user and administrators.

Such protection is called Permanent, Interface, or Indefinite protection; and pages under this protection level can only be edited by those with

interface administrator
permissions.

In addition to hard-coded protection, the following are usually fully protected for an indefinite period of time (though not necessarily with interface protection):

Office actions

Black padlock

As outlined in Meta-Wiki:Office actions#Use of advanced rights by Foundation staff, pages may be protected by Wikimedia Foundation staff in response to issues such as copyright infringement or libel. Such actions override community consensus. Administrators should not edit or unprotect such pages without permission from Wikimedia Foundation staff.[11]

Cascading protection

Turquoise padlock

Cascading protection fully protects a page, and extends that full protection automatically to any page that is

transcluded onto the protected page, whether directly or indirectly. This includes templates, images and other media that are hosted on the English Wikipedia. Files stored on Commons are not protected by any other wiki's cascading protection and, if they are to be protected, must be either temporarily uploaded to the English Wikipedia or explicitly protected at Commons (whether manually or through cascading protection there). When operational, KrinkleBot cascade-protects Commons files transcluded at Wikipedia:Main Page/Tomorrow, Wikipedia:Main Page/Commons media protection and Main Page. As the bot's response time varies, media should not be transcluded on the main page (or its constituent templates) until after it has been protected. (This is particularly relevant to Template:In the news, for which upcoming images are not queued at Wikipedia:Main Page/Tomorrow
.) Cascading protection:

The list of cascading-protected pages can be found at Wikipedia:Cascade-protected items. Requests to add or remove cascading protection on a page should be made at Wikipedia talk:Cascade-protected items as an edit request.

Former deleted protections

Superprotect

Superprotect was a level of protection, allowing editing only by Wikimedia Foundation employees who are in the Staff global group. It was implemented on August 10, 2014, and used the same day to override community consensus regarding the use of the Media Viewer on the German Wikipedia's primary site JavaScript, common.js. It was never used on the English Wikipedia. On November 5, 2015, the WMF decided to remove superprotect from all Wikimedia wikis.

Restricted namespace protections

The Gadget and Gadget definition namespaces have namespace-wide protection, and the permissions to edit them are only available to WMF Staff. There is one page on the English Wikipedia in these namespaces. A request for local access to this namespace has been pending since 2019.

Cascading semi-protection

Cascading semi-protection was formerly possible, but it was disabled in 2007 after users noticed that non-administrators could fully protect any page by transcluding it onto the page to which cascading semi-protection had been applied by an administrator.

Pending changes protection level 2

Originally, two levels of pending changes protection existed, where level 2 required edits by all users who are not pending changes reviewers to be reviewed. Following a community discussion, level 2 was retired from the English Wikipedia in January 2017. It was suggested then that "Pending changes level 1" be referred to in the future as simply "Pending changes".[12]

Protection by namespace

Article talk pages

Modifications to a protected page can be proposed on its

Edit protected
}} template on the talk page will draw the attention of administrators for implementing uncontroversial changes.

Talk pages are not usually protected, and are semi-protected only for a limited duration in the most severe cases of vandalism.

User talk pages

User talk pages are rarely protected. However, protection may be applied if there is severe vandalism or abuse. Users whose talk pages are protected may wish to have an unprotected user talk subpage linked conspicuously from their main talk page to allow good-faith comments from users that the protection restricts editing from.

A user's request to have their own talk page protected is not a sufficient rationale by itself to protect the page, although requests may be considered if a reason is provided.

Blocked users

Blocked users' user talk pages should not ordinarily be protected, as this interferes with the user's ability to contest their block through the normal process. It also prevents others from being able to use the talk page to communicate with the blocked editor.

In extreme cases of abuse by the blocked user, such as abuse of the {{

UTRS tool interface or, as a last recourse, the Arbitration Committee
.

When required, protection should be implemented for only a brief period, not exceeding the duration of the block.

Confirmed socks of registered users should be dealt with in accordance with Wikipedia:Sockpuppetry; their pages are not normally protected.

User pages

Base user pages (for example, the page User:Example, and not User:Example/subpage or User talk:Example) are automatically protected from creation or editing by unconfirmed accounts and anonymous IP users. An exception to this includes an unconfirmed registered account attempting to create or edit their own user page. IP editors and unconfirmed accounts are also unable to create or edit user pages that do not belong to a currently-registered account. This protection is enforced by an edit filter.[13] Users may opt-out of this protection by placing {{unlocked userpage}} anywhere on their own user page.

User pages and subpages within their own user space may be protected upon a request from the user, as long as a need exists. Pages within the user space should not be automatically or pre-emptively protected without good reason or cause.[14][15] Requests for protection specifically at uncommon levels (such as template protection) may be granted if the user has expressed a genuine and realistic need.

When a filter is insufficient to stop user page vandalism, a user may choose to create a ".css" subpage (ex. User:Example/Userpage.css), copy all the contents of their user page onto the subpage, transclude the subpage by putting {{User:Example/Userpage.css}} on their user page, and then ask an administrator to fully protect their user page. Because user space pages that end in ".css", ".js", and ".json" are editable only by the user to which that user space belongs (and interface administrators), this will protect one's user page from further vandalism.

Deceased users

In the event of the confirmed death of a user, the user's user page (but not the user talk page) should be fully protected.

Protection of templates

Highly visible templates – those used on a large number of pages or frequently substituted – are often edit protected based on the degree of visibility, type of use, content, and other considerations.

Protected templates should normally have the {{documentation}} template. It loads the unprotected /doc page, so that non-admins and IP-users can edit the documentation, categories and interwiki links. It also automatically adds {{pp-template}} to protected templates, which displays a small padlock in the top right corner and categorizes the template as protected. Only manually add {{pp-template}} to protected templates that don't use {{documentation}} (mostly the flag templates).

Cascading protection should generally not be applied directly to templates, as it will not protect transclusions inside <includeonly> tags or transclusions that depend on template parameters, but will protect the template's documentation subpage. Instead, consider any of the following:

  • If the set of subtemplates is static (even if large), protect them using normal protection mechanisms.
  • If the set of subtemplates is unbounded, use MediaWiki:Titleblacklist to protect all subtemplates using a particular naming format (as is done for editnotice templates and subtemplates of Template:TFA title).

Note: All editnotice templates (except those in userspace) are already protected via MediaWiki:Titleblacklist. They can be edited by admins, template editors and page movers only.

Sandboxes

Sandboxes should not ordinarily be protected since their purpose is to let new users test and experiment with

wiki syntax. Most sandboxes are automatically cleaned every 12 hours, although they are frequently overwritten by other testing users. The Wikipedia:Sandbox is cleaned every hour. Those who use sandboxes for malicious purposes, or to violate policies such as no personal attacks, civility, or copyrights
, should instead be warned and/or blocked.

Available templates

The following templates may be added at the very top of a page to indicate that it is protected:

Module:Protection banner

On redirect pages, use the {{Redirect category shell}} template, which automatically categorizes by protection level, below the redirect line. A protection template may also be added below the redirect line, but it will serve only to categorize the page, as it will not be visible on the page, and it will have to be manually removed when protection is removed.

See also

Notes

  1. ^ a b Wikipedia:Requests for comment/Extended confirmed protection policy 2.
  2. ^ Wikipedia:Requests for comment/Extended confirmed protection policy.
  3. ^ Should we use ECP on templates? discussion at the village pump.
  4. ^ a b c Wikipedia:Arbitration Committee/Noticeboard/Archive 13 § Extended confirmed restriction omnibus motion.
  5. ^ Originally authorised in Wikipedia:Arbitration/Requests/Case/Palestine-Israel articles 3.
  6. ^ Proposal: Extended-confirmed restriction for all articles related to the Russia-Ukraine War.
  7. ^ AN discussion authorizing India-Pakistan general prohibition
  8. ^ Wikipedia:Administrators' noticeboard/Archive337 § Community review: WP:GS/IPAK sanctions; cf. Wikipedia talk:Requests for arbitration/India-Pakistan § Amendment request: India-Pakistan (October 2021)
  9. ^ Wikipedia talk:Protection Policy discussion to remove manual posting requirement
  10. ^ Created October 2013 as a result of Wikipedia:Requests for comment/Template editor user right‎
  11. WP:SUPERPROTECT
    , admins technically can still edit or unprotect these pages, however, they should not do so without permission.
  12. ^ VPR RfC to remove PC2
  13. ^ Please refer to Wikipedia:Requests for comment/Protect user pages by default and its talk page for community discussion related to a preventative measure for user pages.
  14. ^ Per discussion at Wikipedia talk:Protection policy/Archive 15#Own userspace pages protection policy, June 2013
  15. ^ Per discussion at Wikipedia:Administrators' noticeboard/Archive314#Protecting an editor's user page or user space per their request, September 2019