ଉଇକିପିଡ଼ିଆ:Protection policy

"WP:PP" redirects here. You may be looking for Wikipedia:Lists of protected pages, Wikipedia:Perennial proposals or WikiProject Parliamentary Procedure.

"WP:PROTECT" redirects here. You may be looking for Wikipedia:Child protection.

ଏହି ପୃଷ୍ଠାଟି ଉଇକିପିଡ଼ିଆ ନୀତି ବାବଦରେ ଇଂରାଜିରେ ବର୍ଣ୍ଣିତ, ସଭିଙ୍କ ଦେଇ ଗ୍ରହଣ କରାଯାଇଥାଏ ଯାହାକୁ ସବୁ ଦାତା ସମାନ ଭାବରେ ମାନି ପାରିବେ । ବଦଳ ସବୁ ବହୁମତ ଦେଇ କରାଯାଇପାରିବ ।

Shortcuts WP:PP WP:PROTECT

This page in a nutshell: Editing or moving of a page can be restricted by administrators. As Wikipedia is built around the principle that anyone can edit it, this should only be done in certain situations.

Fully protected

Semi-protected

Pending changes protected (level 1)

Pending changes protected (level 2)

Create protected

Move protected

Upload protected

Permanently protected

Protected by Office

Administrators are able to protect a page to restrict editing or moving of that page, and remove such protection. Protection can be indefinite, or expire after a specified time.

• Full protection prevents editing by everyone except administrators. Fully protected media files cannot be overwritten by new uploads.
• Semi-protection prevents editing by unregistered contributors and contributors with accounts which are not autoconfirmed.
• Creation protection prevents a page (normally a previously deleted one) from being recreated (also known as "salting").
• Move protection protects the page solely from moves.
• Upload protection protects the file from reupload, does not protect the file page from editing.
• Pending-changes protection means edits are not visible to readers who are not logged in, until the edits are checked by a reviewer.

Any type of protection or unprotection may be requested at Wikipedia:Requests for page protection. Changes to a fully protected page should be proposed on the corresponding talk page, and carried out if they are uncontroversial or if there is consensus for them.

Except in the case of office actions (see 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. Contacting the administrator who originally protected the page is advised in unclear circumstances. A log of protections and unprotections is available at Special:Log/protect.

A fully protected page can be edited only by 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 in another appropriate forum for discussion. Administrators can make changes to the protected article reflecting consensus. Placing the {{editprotected}} template on the talk page will draw the attention of administrators for implementing uncontroversial changes.

On pages that are experiencing edit warring, temporary full protection can force the parties to discuss their edits on the talk page, where they can reach consensus. Isolated incidents of edit warring, and persistent edit warring by particular users, may be better addressed by blocking, so as not to prevent normal editing of the page by others.

When protecting a page because of a content dispute, administrators normally protect the current version, except where the current version contains content that clearly violates content policies, such as vandalism, copyright violations, or defamation of living persons. Since protecting the most current version sometimes rewards edit warring by establishing a contentious revision, administrators may also revert to an old version of the page predating the edit war if such a clear point exists. Pages that are protected because of content disputes should not be edited except to make changes which are uncontroversial or for which there is clear consensus (see above).

Administrators should not protect or unprotect a page to further their own positions in content disputes.

Pre-emptive full protection of articles is contrary to the open nature of Wikipedia. Brief periods of full protection are used in rare cases when a large number of autoconfirmed accounts are used to make a sustained vandalism attack on an article. Persistent vandalism, or the possibility of future vandalism for highly trafficked articles, rarely provides a basis for full-protection. Semi-protection is used for articles, such as Jesus, that have a pattern of heavy sustained vandalism.

If a deleted page is undergoing 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 restore the page, blank it or replace the contents with {{TempUndelete}} or a similar notice, and fully protect the page to prevent further editing. The previous contents of the page are then accessible to non-admins via the page history.

Generic image names such as File:map.jpg or File:Photo.jpg are tagged with {{Protected generic image name}} and fully protected to prevent new versions being uploaded.

Semi-protection prevents edits from unregistered users (IP addresses), as well as edits from any account that is not autoconfirmed (is at least four days old and has ten or more edits to Wikipedia) or confirmed.

Such users can request edits to a semi-protected page by proposing them on its talk page, using the {{Edit semi-protected}} template if necessary to gain attention. If the page in question and its talk page are both protected please make your edit request at Wikipedia:Request for edit instead. New users may also request the confirmed user right by visiting Requests for permissions.

Administrators may apply indefinite semi-protection to pages which 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 pre-emptive measure against vandalism that has not yet occurred, nor should it be used solely to prevent editing by unregistered and newly registered users, nor to privilege registered users over unregistered users in 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) when blocking individual users is not a feasible option.
• Subject to edit-warring where all parties involved are unregistered or new editors (i.e., in cases in which full-protection would otherwise be applied). This does not apply when autoconfirmed users are involved.
• Subject to vandalism or edit-warring where unregistered editors are engaging in IP-hopping by using different computers, obtaining new addresses by using dynamic IP allocation, or other address changing schemes such as IP address spoofing.
• Article discussion pages, when 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. If the page in question and its talk page are both protected please make your edit request at Wikipedia:Request for edit instead.
• Talk pages of blocked IP addresses that are being used for continued inappropriate editing, including repeated abuse of the {{unblock}} template, or continued uncivil or offensive remarks. The protection should be timed so as to not exceed the length of the block. Although administrators may also choose to change the block settings to block the user from editing their talk page instead, since there is no need to synchronize the block period with the page protection time period with this method.

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

Administrators can prevent the creation of a page through the protection interface. This is useful for articles that have been deleted but repeatedly recreated by an editor. Such protection is case-sensitive. A list of protected titles may be found at Special:Protectedtitles (see also 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". Contributors wishing to re-create a salted title with more appropriate content should contact an administrator or use the deletion review process.

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 vandalism.
• Pages subject to a page-name dispute.
• Highly visible pages that have no reason to be moved, such as the Administrators' noticeboard.

Fully protected pages are also move-protected.

As with full protection, administrators should avoid favoring one name over another, and protection should not be considered an endorsement of the current name. An obvious exception to this rule is when pages are protected due to page-move vandalism. 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.

Upload protected files cannot be replaced with new versions except by an administrator. Upload protection does not protect file pages from editing. Upload protection 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.

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

Policy shortcuts: WP:PCPP WP:WHITELOCK WP:ORANGELOCK

For a trial period that began on June 15, 2010, articles could be protected by pending-changes protection. The trial is now over.

The protection policy that was applied during the trial can be seen in this page's version from September 2, 2010.

Some areas of Wikipedia are permanently protected by the MediaWiki software. The MediaWiki namespace, which defines parts of the site interface, is fully protected; it is impossible for administrators to remove this protection. In addition, user CSS and JavaScript pages, such as User:Example/monobook.css and User:Example/cologneblue.js, are automatically fully protected. Only accounts that are associated with these pages or administrators are able to edit them. This protection applies to any user subpage with a ".css" or ".js" extension, whether an equivalent MediaWiki skin exists or not. Administrators may modify these pages, for example, to remove a user script that has been used in an inappropriate way.

In addition to the hard-coded protection, the following are usually permanently protected:

• Pages that are very visible, such as the Main Page or File:Wiki.png.
• Pages that should not be modified for copyright or legal reasons, such as the general disclaimer or the local copy of the site copyright license.
• Pages that are very frequently transcluded, such as {{tl}} or {{ambox}}, to prevent vandalism or denial of service attacks. This includes images or templates used in other highly visible or frequently transcluded pages. See Wikipedia:High-risk templates for more information.
• Files are indefinitely move-protected, though file movers and administrators may still move them.

As outlined at Wikipedia:Office actions, pages may be protected by Wikimedia Foundation staff in response to issues such as copyright or libel. Such actions override community consensus. Administrators should not edit or unprotect such pages without permission from Wikimedia Foundation staff. A list of pages under the scrutiny of the Wikimedia Foundation can be found here.

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 English Wikipedia. Files stored on Commons will not be protected by cascading protection, and need to be temporarily uploaded to English Wikipedia or protected at Commons. Cascading protection:

• Should be used only to prevent vandalism when placed on particularly visible pages such as the Main Page.

• Is available only for fully protected pages; it is disabled for semi-protected pages as it represents a security flaw. See Bugzilla:8796 for more information.

• Is not instantaneous; it may be several hours before it takes effect. See Bugzilla:18483 for more information.

• 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. See the "Templates" section below for alternatives.

The following table compares the effects on editors, of different protection tools.

Highly visible templates which are used on an extremely large number of pages or substituted with great frequency are particularly vulnerable to vandalism, as vandalism to the template may introduce vandalism to hundreds of other pages. Therefore, they are frequently semi- or fully protected based on the degree of visibility, type of use, content, and other factors.

Semi and fully 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 a protected template. Only manually add {{pp-template}} to protected templates that don't use {{documentation}} (mostly the stub and 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 full set of subtemplates is transcluded whenever the main template is trancluded, transclude the main template on Wikipedia:Cascade-protected items or a similar page.
• 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 (which can, however, be overridden by account creators)

User pages and subpages are sometimes protected at the user's request, or if there is evidence of vandalism or disruption. User talk pages are rarely protected, and are semi-protected for short durations only in the most severe cases of vandalism from IP users.

Users whose talk page is semi-protected for lengthy or indefinite periods of time should have an unprotected user talk subpage linked conspicuously from their main talk page to allow good faith comments from non-autoconfirmed users.

In the event of the confirmed death of a user, his or her user page, but not talk page, should be fully protected.

Retired users may have their user pages protected upon request. Talk pages of retired editors are not usually protected except with limited duration to deal with vandalism. A user's request to have his or her own talk page protected due to retirement is not a sufficient rationale to protect the page.

Blocked users' user pages and user talk pages should not ordinarily be protected, as this interferes with the user's ability to contest their block through the normal process. In extreme cases of abuse, such as abuse of the {{unblock}} template, the talk page may be protected for a short time to prevent abusive editing. When required, it should be implemented for a brief period which should not exceed the length of the block, whichever is shorter. Consider disabling the user's talk page access via the block feature instead. In cases where the user has been blocked indefinitely, they should be informed of off-wiki ways to appeal their block, such as the unblock-en-l mailing list or ban appeals subcommittee of the Arbitration Committee. Confirmed socks of registered users should be dealt with in accordance with Wikipedia:Sockpuppetry; their pages are not normally protected.

Wikipedia:Sandbox and other sandboxes should also not ordinarily be protected since their purpose is to let new users test and experiment with wiki syntax. These pages are automatically cleaned every 12 hours, although they are frequently overwritten by other testing users much faster than that. Those who do use the sandboxes for malicious purposes, or to violate policies such as no personal attacks, civility, and copyrights, should instead be warned and/or blocked.

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

On redirect pages, add Category:Protected redirects below the redirect line. A protection template may also be added below the redirect line, but it will only serve to categorize the page, as it will not be visible on the page.

• MediaWiki:Protectedpagetext
• Special:Protectedpages
• Special:Protectedtitles
• Wikipedia:Edit lock
• Wikipedia:List of indefinitely protected pages
• Wikipedia:Requests for page protection
• Wikipedia:Rough guide to semi-protection
• Wikipedia:Make protection requests sparingly, an essay
• m:Protected pages considered harmful
• m:The Wrong Version