View source for Project:Protection policy

{{pp-move-indef|small=yes}}
{{pp-semi-indef}}
{{See also||Project:Requests for page protection|Project:Lists of protected pages}}
{{redirect2|WP:PP|WP:PROTECT|other uses|Project:Perennial proposals|and|Project:WikiProject Parliamentary Procedure|and|Project:Party and person|and|Project:Child protection|and|Project:WikiProject Protected areas}}
{{policy|subcategory=enforcement|WP:PP|WP:PROTECT}}
{{nutshell|While {{SITENAME}} strives to be as open as possible, sometimes it is necessary to limit editing of certain pages in order to prevent [[WP:VD|vandalism]], [[WP:EW|edit warring]], or other [[WP:DE|disruptive edits]].}}
{{Right place
|desc=documents the protection policy on {{SITENAME}}
|action1=make a request to protect or unprotect a page
|page1=see [[Project:Requests for page protection]]
|action2=make a request to edit a page
|page2=see [[Project:Edit requests]]
|action3=obtain user rights to edit protected pages
|page3=[[WP:RFPERM|request user rights]]
|action4=report a user for persistent vandalism or spam
|page4=[[WP:AIV|file a vandalism report]]
|action5=report a user for [[WP:EW|edit warring]] or violating revert restrictions
|page5=[[WP:ANEW|open an edit warring report]]
}}
{{Enforcement policy list}}
{| class="wikitable floatright"
|+ Protection icons
|-
! Icon !! Mode
|-
| [[File:Pending-protection-shackle.svg|40px|Pending changes protected|alt=White padlock]] White || [[#pending|Pending changes protected]]
|-
| [[File:Semi-protection-shackle.svg|40px|Semi-protected|alt=Silver padlock]] Silver || [[#semi|Semi-protected]]
|-
| [[File:Extended-protection-shackle.svg|40px|Extended confirmed protection|alt=Dark blue padlock]] Blue || [[#extended|Extended confirmed protected]]
|-
| [[File:Template-protection-shackle.svg|40px|Template-protected|alt=Pink padlock]] Pink || [[#template|Template-protected]]
|-
| [[File:Full-protection-shackle.svg|40px|Fully protected|alt=Gold padlock]] Gold || [[#full|Fully protected]]
|-
| [[File:Interface-protection-shackle.svg|40px|alt=Brown padlock]] Red || [[#interface|Interface protected]]
|-
| [[File:Move-protection-shackle.svg|40px|Move protected|alt=Green padlock]] Green || [[#move|Move protected]]
|-
| [[File:Create-protection-shackle.svg|40px|Create protected|alt=Blue padlock]] Skyblue || [[#create|Create protected]]
|-
| [[File:Upload-protection-shackle.svg|40px|Upload protected|alt=Purple padlock]] Purple || [[#upload|Upload protected]]
|-
| [[File:Cascade-protection-shackle.svg|40px|Cascade protected|alt=Turquoise padlock]] Turquoise || [[#cascade|Cascade protected]]
|-
| [[File:Office-protection-shackle.svg|40px|Protected by Office|alt=Black padlock]] Black || [[#office|Protected by Office]]
|}

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 cannot be prevented through other means such as a [[WP:Blocking policy|block]]. Otherwise, {{SITENAME}} is built on the principle that [[wiki|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 [[Project:Administrators|administrators]], although any user may [[WP:Requests for page protection|request protection]]. Protection can be [[Project:List of indefinitely protected pages|indefinite]] or expire after a specified time. The various levels of protection are detailed below, and they can be applied to the page edit, page move, page create, and file upload actions. Even when a page is protected from editing, the {{wt|source code}} ({{wt|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 {{tlx|pp-protected}} template.

== Preemptive protection ==
{{Policy shortcut|WP:NO-PREEMPT|WP:PREEMPTIVE}}

Applying page protection as a preemptive measure is contrary to the open nature of {{SITENAME}} 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.

Exceptions are largely confined to the Main Page, which is fully protected (along with its templates and images), and [[Project:Today's featured article|Today's Featured Article]], which is semi-protected from the day before being featured until the day after it leaves the Main Page.

== Requesting protection ==

=== Protection types ===
{{Policy shortcut|WP:PPLIST}}

The following protection types are available to administrators for protecting different actions to pages:
*'''[[#Edit protection|Edit protection]]''' protects the page from being [[Help:Editing|edited]].
*'''[[#Move protection|Move protection]]''' protects the page from being [[Help:Moving a page|moved or renamed]].
*'''[[#Creation protection (salting)|Creation protection]]''' prevents a page (normally a previously [[Project:Deletion policy|deleted]] one) from being created (also known as "salting").
*'''[[#Upload protection|Upload protection]]''' prevents new versions of a file from being [[Help:upload|uploaded]], but it does not prevent editing of the file's description page (unless edit protection is applied).

=== Protection levels ===
The following protection levels are available to administrators for adding protection 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 [[Project:User access levels#Autoconfirmed users|confirmed]] to be approved by a [[Project:User access levels#Reviewer|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''', previously known as '''30/500 protection''', prevents the action if the user's account is not extended confirmed (at least 30 days old with at least 500 edits). 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 [[WP:AN|Administrators' noticeboard]].
*'''Template protection''' prevents the action by everyone except [[Project:Template editor|template editors]] and [[Project:Administrators|administrators]] (who have this right as part of their toolset).
*'''Full protection''' prevents the action by everyone except [[Project:Administrators|administrators]].

=== Submitting requests ===
Any of the above protections can be requested at [[Project:Requests for page protection]]. Changes to a protected page should be proposed on the corresponding [[WP:Talk page|talk page]], and then (if necessary) requested by adding an [[WP:ER|edit request]]. From there, if the requested changes are uncontroversial or if there is [[Project:Consensus|consensus]] for them, the changes can be carried out by a user who can edit the page.

{{anchor|RemovingProtection}}Except in the case of [[Project:Office actions|office actions]] (see [[#Office actions|below]]), [[Project:AC|Arbitration Committee]] remedies, or pages in the MediaWiki namespace (see [[#Permanent protection|below]]), administrators may unprotect a page if the reason for its protection no longer applies, a reasonable period has elapsed, and there is no consensus that continued protection is necessary. Editors desiring the unprotection of a page should, in the first instance, ask the administrator who applied the protection unless the administrator is inactive or no longer an administrator; thereafter, requests can be made at [[WP:RFUP|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]].

=== Comparison table ===
{{anchor|Comparison table}}
{{Protection table|yes}}
== Protection levels ==
Each of these levels is explained in the context of edit protection, but each can be applied to other types of protection except for pending changes.

=== Pending changes protection<span class="anchor" id="pending"></span><span class="anchor" id="Pending-changes protection (trial)"></span><span class="anchor" id="pc1"></span><span class="anchor" id="pc2"></span><!--former tags allow section referencing while accommodating section name changes. DO NOT REMOVE IT.--> ===
{{see|Project:Pending changes}}
[[File:Pending-protection-shackle.svg|64px|upright=0.4|right|alt=White padlock|link=]]
{{Policy shortcut|WP:PCPP|WP:WHITELOCK}}

Pending changes protection allows unregistered and new users to edit pages, while keeping their edits hidden from most readers (specifically, unregistered editors{{snd}}the vast majority of visitors to {{SITENAME}} articles) until those changes are accepted by a [[WP:RPC|pending changes reviewer]] or administrator. An alternative to semi-protection, it is used to suppress [[Project:Vandalism|vandalism]] and certain other persistent problems while allowing all users to continue to submit edits. Pending changes is technically implemented as a separate option, with its own duration, and it yields to other edit protection levels in cases of overlap.

When a page under pending changes protection is edited by an [[WP:IP|unregistered]] (IP addresses) editor or a [[Project:User access levels#New users|new user]], the edit is not directly visible to the majority of {{SITENAME}} readers, until it is reviewed and accepted by an editor with the [[Project:User access levels#Pending changes reviewer|pending changes reviewer right]]. When a page under pending changes protection is edited by an [[Project:User access levels#Autoconfirmed users|autoconfirmed user]], the edit will be immediately visible to {{SITENAME}} 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 who 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''.
*If the editor is not logged in, their changes join any other changes to the article awaiting review{{snd}}for the present they remain hidden from not-logged-in users. (This means that when the editor looks at the article after saving, the editor won't see the change made.)
*If the editor is logged in and a pending changes reviewer, and there are pending changes, the editor will be prompted to review the pending changes before editing{{snd}}see [[Project:Pending changes]].
*If the editor is logged in and not a pending changes reviewer:
**If there are no unreviewed pending edits waiting, this editor's edits will be visible to everyone immediately; but
**If there are unreviewed pending edits waiting, then this editor's edits will be visible only to other logged-in users (including themself) immediately, but not to readers not logged in.

Reviewing of pending changes should be resolved within reasonable time limits.<!-- <<what does this mean, and how does it help to say it? -->

==== When to apply pending changes protection ====
Pending changes can be used to protect articles against:
* Persistent vandalism
* Violations of the [[Project:biographies of living persons|biographies of living persons]] policy
* [[WP:CV|Copyright violations]]

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 [[Project:RFUP|requests for unprotection]].

{{anchor|Reviewing}}The reviewing process is described in detail at [[Project:Reviewing pending changes]].

=== Semi-protection<span class="anchor" id="semi"></span><span class="anchor" id="semi-user"></span><!--former tag allows section referencing while accommodating section name changes. DO NOT REMOVE IT.--> ===
{{See also|Project:Rough guide to semi-protection}}
[[File:Semi-protection-shackle.svg|64px|upright=0.4|right|alt=Silver padlock|link=]]
{{Policy shortcut|WP:SEMI|WP:SILVERLOCK}}

Semi-protected pages like this page cannot be edited by [[Project:User access levels#Unregistered users|unregistered users]] ({{wt|IP address}}es), as well as accounts that are not [[Project:User access levels#Confirmed users|confirmed]] or [[Project:User access levels#Autoconfirmed users|autoconfirmed]] (accounts that are at least 4 days old with at least 10 edits on English {{SITENAME}}). Semi-protection is useful when there is a significant amount of disruption or [[Project:Vandalism|vandalism]] from new or unregistered users, or to prevent [[WP:SOCK|sockpuppets]] of blocked or banned users from editing, especially when it occurs on [[WP:BLP|biographies of living persons]] who have had a recent high level of media interest. An alternative to semi-protection is [[Project:Pending changes|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 {{Tl|Edit semi-protected}} template if necessary to gain attention. If the page in question and its talk page are ''both'' protected, the edit request should be made at [[WP:RFED|Project:Requests for page protection]] instead. New users may also request the confirmed user right at [[Project:Requests for permissions/Confirmed]].

==== Guidance for administrators ====
Semi-protection should {{em|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.

Administrators may apply {{em|temporary}} semi-protection on pages that are:
* Subject to significant but temporary vandalism or disruption (for example, due to [[Project:{{SITENAME}} in the media|media attention]]) if [[Project:Blocking policy|blocking]] individual users is not a feasible option.
* Subject to [[Project:Edit warring|edit warring]] if {{em|all}} parties involved are unregistered or new editors. This does {{em|not}} apply when autoconfirmed users are involved.
* Subject to [[Project:Vandalism|vandalism]] or [[Project:Edit warring|edit warring]] where unregistered editors are engaging in [[IP address#Dynamic IP|IP hopping]] by using different computers, obtaining new addresses by using {{wt|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.
* 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.

In addition, administrators may apply {{em|indefinite}} semi-protection to pages that are subject to heavy and persistent [[Project:Vandalism|vandalism]] or violations of [[:Category:{{SITENAME}} content policies|content policy]] (such as [[Project:Biographies of living persons|biographies of living persons]], [[Project:Neutral point of view|neutral point of view]]).

A page and its talk page should not normally be protected at the same time. In exceptional cases, if a page and its talk page are both protected, the talk page should direct affected editors to [[WP:RFED|Project:Request for edit]] through the use of a non-iconified page protection template, to ensure that no editor is entirely prevented from contributing.

[[Project:Today's featured article|Today's featured article]] is, since 2023, always semi-protected. [[Project:Main Page featured article protection|This was historically not the case]], however.

=== Extended confirmed protection<span class="anchor" id="30/500"></span><span class="anchor" id="extended"></span><span class="anchor" id="Arbitration 30/500 protection"></span><!--former tags allow section referencing while accommodating section name changes. DO NOT REMOVE IT.--> ===
{{see also|Project:Rough guide to extended confirmed protection}}
[[File:Extended-protection-shackle.svg|64px|upright=0.4|right|alt=Dark blue padlock|link=]]
{{policy shortcut|WP:ECP|WP:30/500|WP:BLUELOCK}}
Extended confirmed protection, previously known as 30/500 protection, allows edits only by editors with the [[Project:User access levels#Extendedconfirmed|extended confirmed]] user access level, granted automatically to registered users at least 30 days old with at least 500 edits on English {{SITENAME}}.

==== As escalation from semi-protection ====
Where semi-protection has proven to be ineffective, administrators may use extended confirmed protection to combat disruption (such as [[WP:VD|vandalism]], abusive [[WP:SOCK|sockpuppetry]], [[WP:WAR|edit wars]], etc.) on any topic.<ref>[[Project:Requests for comment/Extended confirmed protection policy]].</ref> Extended confirmed protection should not be used as a preemptive measure against disruption that has not yet occurred, nor should it be used to privilege extended confirmed users over unregistered/new users in valid content disputes (except as general sanction enforcement; see below).<ref name="ECPRFC2">[[Project:Requests for comment/Extended confirmed protection policy 2]].</ref>

==== Contentious topics ====
When necessary to prevent disruption in [[WP:CTOP|designated contentious topic areas]], administrators are authorized to make protections at any level. (This is distinct from the extended confirmed restriction below.) Some [[Project:General_sanctions#Community-authorised_discretionary_sanctions|community-authorized discretionary sanctions]] grant similar authorizations.

==== Extended confirmed restriction ====
Some topic areas are under Arbitration Committee [[Project:Arbitration Committee/Procedures#Extended confirmed restriction|extended confirmed restriction]] as a general sanction.<ref>The extended confirmed restriction was previously known as the "500/30 rule" which differed slightly.</ref> When such a restriction is in effect in a topic area, only extended-confirmed users may make edits related to the topic area. Enforcement of the restriction on articles primarily in the topic area is preferably done with extended confirmed protection, but it's not required  (other enforcement methods are outlined in the policy). As always, review the policy before enforcing it.

Community general sanctions, applying a similar extended confirmed restriction, have also been authorized by the community.

[[Project:General sanctions|General sanctions]] has a list of the active general sanctions that incorporate the extended confirmed restriction.

==== Other cases ====
[[WP:HRT|High-risk templates]] can be extended-confirmed protected at administrator discretion when template protection would be too restrictive and semi-protection would be ineffective to stop widespread disruption.<ref>[[Special:Diff/1042239556#Should we use ECP on templates?|Should we use ECP on templates?]] discussion at the village pump.</ref>

Extended confirmed protection can be applied at the discretion of an administrator when creation-protecting a page.<ref name="ECPRFC2"/>

==== Logging and edit requests ====
As of September 23, 2016, a bot posts a notification in a subsection of [[Project:Administrators' noticeboard#Pages_recently_put_under_extended-confirmed_protection|AN]] when this protection level is used.<ref>[[Special:Diff/740835205|{{SITENAME}} talk:Protection Policy discussion to remove manual posting requirement]]</ref> Any protection made as arbitration enforcement must be logged at [[Project:Arbitration enforcement log]]. Community-authorized discretionary sanctions must be logged on a page specific to the topic area. A full list of the {{User:MusikBot/ECPMonitor/Total}} pages under extended confirmed protection can be found <span class="plainlinks">[{{fullurl:Special:ProtectedPages|level=extendedconfirmed}} here]</span>.

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

=== Full protection<span class="anchor" id="full"></span><!--former tag allows section referencing while accommodating section name changes. DO NOT REMOVE IT.--> ===
[[File:Full-protection-shackle.svg|64px|upright=0.4|right|alt=Gold padlock|link=]]
{{policy shortcut|WP:FULL|WP:GOLDLOCK}}
A fully protected page cannot be edited or moved by anyone except [[Project:Administrators|administrators]].

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

==== Content disputes<span class="anchor" id="full-dispute"></span><!--former tag allows section referencing while accommodating section name changes. DO NOT REMOVE IT.--> ====
{{See also|Project:Stable version}}
{{redirect|WP:PREFER|what title name should be preferred|Project:Disambiguation#Primary topic}}
While content disputes and [[Project:Edit war|edit warring]] can be addressed with user [[Project:Blocking policy|blocks]] issued by [[WP:UNINVOLVED|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 [[Project:Consensus|consensus]] a requirement for implementation of [[Project:Edit requests|requested edits]].

{{anchor|PREFER|prefer}}<!--former tags allow section referencing while accommodating section name changes. DO NOT REMOVE IT.-->
{{Policy shortcut|WP:PREFER}}
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 [[WP:Vandalism|vandalism]], [[WP:COPYVIO|copyright violations]], [[WP:Libel|defamation]], or [[WP:BLP|poor-quality coverage of living people]]. Administrators are deemed to remain uninvolved when exercising discretion on whether to apply protection to the current version of an article, or to an older, [[WP:STABLE|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 [[Project:Edit requests|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 [[WP:INVOLVED|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 ====
{{Policy shortcut|WP:PPDRV}}
If a deleted page is going through [[Project:Deletion review|deletion review]], only administrators are normally capable of viewing the former content of the page. If they feel it would benefit the discussion to allow other users to view the page content, administrators may [[Project:Restore|restore]] the page, blank it or replace the contents with {{tlx|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 [[Help:Page history|page history]].

==== <span id="Protected generic image names"></span> 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 [[#Creation protection|salted]].

=== Template protection<span class="anchor" id="template"></span><!--former tags allow section referencing while accommodating section name changes. DO NOT REMOVE IT.--> ===
{{main|Project:Template editor}}
[[File:Template-protection-shackle.svg|64px|upright=0.4|right|alt=Pink padlock|link=]]
{{Policy shortcut|WP:TPROT|WP:PINKLOCK}}
A template-protected page can be edited only by administrators or users in the {{int:group-templateeditor}} group. This protection level should be used almost exclusively on [[Project:High-risk templates|high-risk templates]] and [[WP:LUA|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<ref>Created October 2013 as a result of [[Project:Requests for comment/Template editor user right‎]]</ref> that replaces [[WP:FULL|full protection]] on pages that are merely protected due to high transclusion rates, rather than content disputes. It should be used on templates whose risk factor would have otherwise warranted full protection. It should not be used on less risky templates on the grounds that the [[WP:TPE|template editor]] user right exists—the existence of the right should not result in more templates becoming uneditable for the general editing community. In borderline cases, [[WP:ECP|extended confirmed protection]] or lower can 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 <span class="plainlinks">[{{fullurl:Special:ProtectedPages|level=templateeditor}} here]</span>.

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

== Protection types ==
=== Edit protection ===
Edit protection restricts editing of a page, often due to vandalism or disputes, ensuring only experienced users can make changes (see above for more information).

=== Creation protection (salting)<span class="anchor" id="salt"></span><span class="anchor" id="create"></span><span class="anchor" id="Creation protection"></span><!--former tag allows section referencing while accommodating section name changes. DO NOT REMOVE IT.--> ===
[[File:Create-protection-shackle.svg|64px|upright=0.4|right|alt=Blue padlock|link=]]
{{policy shortcut|WP:SALT|WP:SKYBLUELOCK}}

Administrators can prevent the creation of pages. This type of protection is useful for pages that have been [[Project:Deletion policy|deleted]] but repeatedly recreated. Such protection is case-sensitive. There are several levels of creation protection that can be applied to pages, identical to the levels for edit protection. A list of protected titles can be found at [[Special:ProtectedTitles]] (see also [[WP:Protected titles/Historical|historical lists]]).

Preemptive restrictions on new article titles are instituted through the [[MediaWiki:Titleblacklist|title blacklist]] system, which allows for more flexible protection with support for {{wt|substring}}s and {{wt|regular expression}}s.

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

Administrators should choose the appropriate level of create protection—autoconfirmed, extended-confirmed,<ref name="ECPRFC2"/> or full. Due to the implementation of [[WP:ACPERM|ACPERM]], non-confirmed editors cannot create pages in [[WP:MAINSPACE|mainspace]]; thus, semi-creation protection should be used only for protection of pages outside of mainspace.

While creation-protection is usually permanent, temporary creation protection can be applied if a page is repeatedly recreated by a single user (or [[WP:SOCK|sockpuppets]] of that user, if applicable).

=== Move protection<span class="anchor" id="move"></span><!--former tag allows section referencing while accommodating section name changes. DO NOT REMOVE IT.--> ===
[[File:Move-protection-shackle.svg|64px|upright=0.4|right|alt=Green padlock|link=]]
{{Policy shortcut|WP:MOVP|WP:GREENLOCK}}

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:

* Pages subject to persistent page-move [[Project:Vandalism|vandalism]].
* Pages subject to a page-name dispute.
* Highly visible pages that have no reason to be moved, such as the [[Project:Administrators' noticeboard|administrators' noticeboard]] and articles selected as "[[Project:Today's featured article|Today's featured article]]" on the main page.

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

As with full edit protection, protection because of edit warring [[:meta:The Wrong Version|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 [[WP:FILE|files]] and [[WP:CATEGORY|categories]] are implicitly move-protected, requiring [[WP:File mover|file movers]] or administrators to rename files, and [[WP:Page mover|page movers]] or administrators to rename categories.

=== Upload protection<span class="anchor" id="upload"></span><!--former tag allows section referencing while accommodating section name changes. DO NOT REMOVE IT.--> ===
[[File:Upload-protection-shackle.svg|64px|upright=0.4|right|alt=Purple padlock|link=]]
{{Policy shortcut|WP:UPLOAD-P|WP:PURPLELOCK}}
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 can be applied by an administrator to:
* Files subject to persistent upload [[Project:Vandalism|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.

== Uncommon protections ==
=== Cascading protection<span class="anchor" id="cascade"></span><!--former tag allows section referencing while accommodating section name changes. DO NOT REMOVE IT.--> ===
{{redirect|WP:CASCADE|text=You may also be looking for [[Help:Cascading Style Sheets]] or [[Project:Cascade-protected items]].}}
[[File:Cascade-protection-shackle.svg|64px|upright=0.4|right|alt=Turquoise padlock|link=]]
{{Policy shortcut|WP:CASCADE|WP:TURQUOISELOCK}}
Cascading protection fully protects a page, and extends that full protection ''automatically'' to any page that is [[Project:Transclusion|transcluded]] onto the protected page, whether directly or indirectly. This includes templates, images and other media that are hosted on the English {{SITENAME}}. 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 {{SITENAME}} or explicitly protected at Commons (whether manually or through cascading protection there). When operational, [[c:User:KrinkleBot|KrinkleBot]] cascade-protects Commons files transcluded at [[Project:Main Page/Tomorrow]], [[Project:Main Page/Commons media protection]] and {{wt|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 [[Project:Main Page/Tomorrow]].) Cascading protection:
*Should be used only to prevent [[Project:Vandalism|vandalism]] when placed on particularly visible pages, such as the main page.
*Is available only for fully protected pages; it is disabled for lower levels of protection as it represents a workflow flaw. See [[#Cascading semi-protection|below]] as well as [[Phabricator:T10796|this bug ticket]] for more information.
*Is not instantaneous; it can be several hours before it takes effect. See [[Phabricator:T20483]] for more information.
*Should generally not be applied directly to templates or [[WP:LUA|modules]], as it will not protect transclusions inside {{tag|includeonly|o}} tags or transclusions that depend on template parameters, but ''will'' protect the [[Project:Template documentation|documentation subpage]]. {{Xref|See {{slink||Protection of templates}} below}}, for alternatives.

The list of cascading-protected pages can be found at [[Project:Cascade-protected items]]. Requests to add or remove cascading protection on a page should be made at [[{{SITENAME}} talk:Cascade-protected items]] as an [[Project:Edit requests|edit request]].

=== Permanent protection<span class="anchor" id="perm"></span><span class="anchor" id="indef"></span><span class="anchor" id="interface"></span><span class="anchor" id="Interface protection"></span><!--former tag allows section referencing while accommodating section name changes. DO NOT REMOVE IT.--> ===
[[File:Interface-protection-shackle.svg|64px|upright=0.4|right|alt=Brown padlock|link=|Icon for pages that can be edited only by interface administrators]]
{{Policy shortcut|WP:PPINDEF|WP:INTPROT|WP:REDLOCK}}

Administrators cannot change or remove the protection for some areas on {{SITENAME}}, which are permanently protected by the {{wt|MediaWiki}} software:
*Edits to the [[Help:MediaWiki namespace|MediaWiki namespace]], which defines parts of the site interface, are restricted to administrators and [[WP:IADMIN|interface administrators]].
**Edits to system-wide CSS and JavaScript pages such as [[MediaWiki:common.js]] are further restricted to [[WP:IADMIN|interface administrators]].
*Edits to personal CSS and JavaScript pages such as [[User:Example/monobook.css]] and [[User:Example/vector-2022.js]] are restricted to the associated user and [[WP:IADMIN|interface administrators]]. Interface administrators may edit these pages, for example, to remove a user script that has been used inappropriately. 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 or indefinite protection, and interface protection in the case of CSS and JavaScript pages.

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

* Very visible pages, such as the {{wt|Main Page}}.
* Pages that should not be modified for legal reasons, such as the [[Project:General disclaimer|general disclaimer]] or the [[Project:Text of the Creative Commons Attribution-ShareAlike 4.0 International License|local copy of the site copyright license]].
* Pages that are very frequently [[Project:Transclusion|transcluded]], such as {{tlx|tl}} or {{tlx|citation needed}}, to prevent [[Project:Vandalism|vandalism]] or [[Denial-of-service attack|denial of service]] attacks. This includes images or templates used in other highly visible or frequently transcluded pages. See [[Project:High-risk templates]] for more information.

=== Office actions<span class="anchor" id="office"></span><!--former tag allows section referencing while accommodating section name changes. DO NOT REMOVE IT.--> ===
{{see also|Project:Office actions}}
[[File:Office-protection-shackle.svg|64px|upright=0.4|right|alt=Black padlock|link=]]
{{policy shortcut|WP:WMF-PRO|WP:BLACKLOCK}}

As outlined in {{section link|Foundation:Policy:Office actions|Use of advanced rights by Foundation staff}}, pages can be protected by [[Project:Wikimedia Foundation|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.<ref>Unlike with [[WP:SUPERPROTECT]], admins ''technically'' can still edit or unprotect these pages, however, they should not do so without permission.</ref>

== Deleted protections ==
=== Superprotect ===
{{shortcut|WP:SUPERPROTECT}}
Superprotect was a level of protection<ref>{{cite web |title=Superprotect |website=Wikimedia Meta-Wiki |date=2014-09-08 | url=https://meta.wikimedia.org/wiki/Superprotect |access-date=2024-03-20}}</ref>, allowing editing only by [{{fullurl:Special:GlobalUsers|group=staff}} Wikimedia Foundation employees who were in the Staff global group]. It was [[gerrit:153302|implemented on August 10, 2014]] and [[mw:WMF product development process/2015-11-05|removed on November 5, 2015]]. It was never used on the English {{SITENAME}}.

For several years, the gadget namespace (which no longer exists) could only be edited by WMF staff, which has sometimes been referred to as superprotection even though it is unrelated to the above use.

=== Cascading semi-protection ===
Cascading semi-protection was formerly possible, but it was disabled in 2007 after [[phab:T10796|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&nbsp;2 ===
[[File:Pending_Changes_Protected_Level_2.svg|64px|upright=0.4|right|alt=Orange padlock|link=]]{{Shortcut|WP:ORANGELOCK}}
Originally, two levels of pending changes protection existed, where level{{nbsp}}2 required edits by all users who are not [[WP:Reviewing pending changes|pending changes reviewers]] to be reviewed. Following a community discussion, level{{nbsp}}2 was retired from the English {{SITENAME}} in January 2017. It was suggested then that "Pending changes level{{nbsp}}1" be referred to in the future as simply "Pending changes".<ref>[[Special:Permalink/762319924#Make PC2 no longer available to admins|VPR RfC to remove PC2]]</ref>

== Protection by namespace ==
{{Policy shortcut|WP:PROTNS}}

=== <span id="Talk pages"></span>Article talk pages<span class="anchor" id="Talk pages"></span><span class="anchor" id="full-talk"></span><!--former tag allows section referencing while accommodating section name changes. DO NOT REMOVE IT.--> ===
{{Policy shortcut|WP:ATPROT}}
Modifications to a protected page can be proposed on its [[Project:Talk page|talk page]] (or at another appropriate forum) for discussion. Administrators can make changes to the protected article reflecting [[Project:Consensus|consensus]]. Placing the {{tlx|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 disruption.

=== User talk pages ===
{{Policy shortcut|WP:UTPROT}}
User talk pages are rarely protected. However, protection can 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 can 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 {{tl|unblock}} template, re-blocking the user with talk page access removed should be preferred over applying protection to the page. If the user has been blocked and with the ability to edit their user talk page disabled, they should be informed of this in a block notice, subsequent notice, or message, and it should include information and instructions for appealing their block off-wiki, such as through the [[WP:UTRS|UTRS tool interface]] or, as a last recourse, [[Project:Appealing a block#Routes to unblock|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 [[Project:Sockpuppetry]]; their pages are not normally protected.

=== User pages ===
{{Policy shortcut|WP:UPROT|WP:UPPROT}}

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 [[Special:AbuseFilter/803|an edit filter]].<ref>Please refer to [[Project:Requests for comment/Protect user pages by default]] and [[{{SITENAME}} talk:Requests for comment/Protect user pages by default|its talk page]] for community discussion related to a preventative measure for user pages.</ref> Users may opt-out of this protection by placing {{tlx|unlocked userpage}} anywhere on their own user page.

[[Project:User pages|User pages]] and subpages within their own user space can be protected upon a request from the user, as long as a need exists. Pages within the user space should not be automatically or preemptively protected without good reason or cause.<ref>Per discussion at {{Section link|{{SITENAME}} talk:Protection policy/Archive 15#Own userspace pages protection policy}}, June 2013</ref><ref>Per discussion at {{Section link|Project:Administrators' noticeboard/Archive314#Protecting an editor's user page or user space per their request}}, September 2019</ref> Requests for protection specifically at uncommon levels (such as template protection<!--ArbCom extended confirmed restriction should possibly be mentioned here too-->) can 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 {{tlf|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" and ".js" 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 ====
{{See also|Project:Deceased {{SITENAME}}ns/Guidelines}}

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 ===
{{shortcut|WP:PTPROT}}
{{see also|Project:High-risk templates|Project:Template documentation}}
Highly visible templates{{snd}}those used on a large number of pages or frequently substituted{{snd}}are often edit protected based on the degree of visibility, type of use, content, and other considerations.

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

Cascading protection should generally not be applied directly to templates, as it will not protect transclusions inside {{tag|includeonly|o}} tags or transclusions that depend on template parameters, but ''will'' protect the template's [[Project:Template documentation|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 [[WP:Editnotice|editnotice templates]] and subtemplates of [[Template:TFA title]]).

Note: All [[WP:Editnotice|editnotice templates]] (except those in userspace) are already protected via [[MediaWiki:Titleblacklist]]. They can be edited by admins, [[WP:Template editor|template editors]] and [[WP:Page mover|page movers]] only.

=== Sandboxes ===
{{see also|Project:About the sandbox}}

Sandboxes should not ordinarily be protected since their purpose is to let new users test and experiment with [[Help:wiki markup|wiki syntax]]. Most sandboxes are automatically cleaned every 12 hours, although they are frequently overwritten by other testing users. The [[Project:Sandbox]] is cleaned every hour. Those who use sandboxes for malicious purposes, or to violate policies such as [[Project:no personal attacks|no personal attacks]], [[Project:civility|civility]], or [[Project:Copyrights|copyrights]], should instead be warned and/or blocked.

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

{{Protection templates}}

On redirect pages, use the {{tl|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 ==
* [[MediaWiki:Protectedpagetext]]
* [[Special:ProtectedPages]]
* [[Special:ProtectedTitles]]
* [[Project:Edit lock]]
* [[Project:List of indefinitely protected pages]]
* [[Project:Requests for page protection]]
* [[Project:Rough guide to semi-protection]]
* [[Project:Make protection requests sparingly]], an essay
* [[Project:Salting is usually a bad idea]], an essay
* [[metawiki:Protected pages considered harmful]]
* [[metawiki:The Wrong Version]]
* [[Project:Protection policy/Padlocks]]

== Notes ==
{{reflist|30em}}

{{New admin school|state=collapsed}}
{{{{SITENAME}} policies and guidelines}}

[[Category:{{SITENAME}} vandalism|{{PAGENAME}}]]
[[Category:{{SITENAME}} page protection|{{PAGENAME}}]]