الفرق بين المراجعتين لصفحة: «كس أمك»

من بيضيبيديا، الموسوعة الفارغة
اذهب إلى التنقل اذهب إلى البحث
تمت إضافة المحتوى تم حذف المحتوى
مرئينص الويكي
لا ملخص تعديل
ط (←‏المصادر: إضافة تصنيف)
 
(55 مراجعة متوسطة بواسطة 36 مستخدماً غير معروضة)
سطر 1: سطر 1:
{| border=1 align=left cellpadding="2" cellspacing=0 width=230 style="margin: 0 0 1em 1em; background:; border: 3px #aaa solid; font-size: 85%;"
|+
|-
| align="center" colspan=2 style="border-bottom:2px" | <font size="+1">
'''يا ويلك و سواد ليلك ان كانت [[هيفاء وهبي|هذه]] امك''' </font>
<br>
|-----
| style="background:#efefef;" align="center" colspan="2" | [[صورة: haifaummak.jpg|200px|]]
|-----
| '''الوظيفة''' || اعادة تأهيلك من [[معنى الحياة|جنين سابق]] الى [[طفل|مواطن زعطوط]]
|-----
| '''دوره في الوحدة العربية''' || كل [[شعب|الشعوب]] العربية تنادي بأسمه من [[الوطن العربي|المحيط الى الخليج]]
|-----
| '''درجة [[الإهانة]]''' || شديدة اللهجة و ما تبشر بخير
|-----
| '''استعمالات اخرى''' || [[تزاوج|حرث لمنجل أبيك يأتيه من أين يشاء]]
|-----
| '''موارد طبيعية''' || دم, مخاط, [[نفط]] , [[الانسان|حضرة جنابك]]
|-----
|}
'''{{C|كس}} [[الأم|امك]]''' لأسباب غير مفهومة تحتل عبارة {{C|كس}} أمك موقع ال[[شتيمة]] الأكثر استفزازا و إهانة من [[الوطن العربي|المخيط الى الخليع]] , لذا فقد تفاجأ عندما تكتشف ان {{C|كس}} امك هو المكان الذي خرجت منه انت و كل هذه [[رجولة|الرجال الغليظة الثخينة]] أيضا قد خرجت من {{C|أكساس}} امهاتها الذليلة , و يعبر عن هذه الدهشة الفسيولوجية بالمثل [[العراق|العراقي]] :'''"شايف مشايف [[عين|شاف]] {{C|كس}} امه و اخترع"''' في دلاله على هول المصيبة باكتشاف ان لأمك {{C|كس}} يمكن ان يدنس [[الرجل|رجولتك]] في أي لحظة . خرجتم من {{C|كس}} امهاتكم عراة حفاة الى هذه [[العالم|الدنيا الواسعة]] فأين العيب إذا ؟ بعد مضي بضعة سنين تستكشف فيها ال[[حياة]] الدنيا قررت انك لا تحب البقاء هنا و اعتذرت من امك في الرجوع مرة اخرى الى [[لجوء سياسي|اللجوء الى الداخل]] حيث ان ارتباط حبل المشيمة الدافئ اهون من [[خازوق|الخوازيق]] التي تستهدفك في كل مكان , رفض طلبك و منذ ذلك اليوم اقمت الدنيا و لم تقعدها على هذا العضو المسكين في سعيك المتواصل لإيجاد ما يربطك بحبل المشيمة مرة أخرى .


يطلق على المهبل باللغة الشوارعية الإنجليزية كلمة Cunt التي تستعمل ك[[شتيمة]] [[المرأة|للمرأة]] العنيدة المزعجة من وجهة نظر [[الرجل]] ولكن ول[[سخرية]] القدر فإن كلمة Cunt مشابهة لكلمات قديمة جدا في قمة المعرفة والروحانيات والاستنارة . فالعضو التناسلي [[المرأة|الأنثوي]] يدعى في اللغة السومرية kunta وتم رسم تلك الإشارات على ألواح [[التراب|الطين]] حوالي 3100 ق.م حيث تم اختراع اللغة التي سميت باللغة المسمارية وهي تدعى بالإنكليزية Cuneiform وهذه التسمية تعني الشكل المهبلي . في لغات الشرق الأدنى و إفريقيا قديما كان يستخدم لفظ Quna للإشارة إلى [[المرأة]] أو مهبلها أو طاقة ال[[حياة]]. حتى كلمة Whore الإنجليزية التي تعني العاهرة أصلها من الفارسية القديمة houri أي حورية كانت تصور أنها مقيمة في السماء السابعة بانتظار [[الرجل]] البطل أو القديس . عند [[العرب]] قديما كانت تدار عبادات الآلهة [[الأم]] بشكل واسع فكلمة اللات تم تذكيرها إلى [[الله]] ، وكلمة العزى تم تذكيرها لتصبح العزيز .
Wikipedia:Protection policy
From Wikipedia, the free encyclopedia
Page semi-protected
"WP:PP" redirects here. You may be looking for Wikipedia:Requests for page protection, Wikipedia:Lists of protected pages, Wikipedia:Perennial proposals or WikiProject Parliamentary Procedure.
"WP:PROTECT" redirects here. You may be looking for Wikipedia:Child protection or Wikipedia:WikiProject Protected areas.
Green check.svg This page documents an English Wikipedia policy, a widely accepted standard that all editors must normally follow. Changes made to it should reflect consensus.
Shortcuts:
WP:PP
WP:PROTECT
Enforcement policies


ولفرج المرأة كذلك تسميات تراثية: التبنة ، الطبون ، الحر ، الفرج ، أبو طرطور ، الشق ، الزرزور ، العص ، الغلمون ،الثقيل ،الدكاك السكوتي، ، القنفود ، أبو خشيم ، النفاخ ، الحسن ، الطلاب ، البشيع ، الفشفاش، المقعور ، أبو بلعوم ، العريض ، الواسع ، أبو جبة ، المؤدي ، الهزاز ، الغربال ، أبو عنكرة ، أبو شفرين ، المقابل ، الملقي ، المسبول ،المغيب ، المعبن ،العضاض، المغمور ، المصفح ، الناوي ، الصبار .
Administrators
==دوره كشتيمة==
Banning policy
{{C|كس}} أمك عبارة لا تقول شيئا . مبتدأ بلا خبر . فاعل ، أو مفعول ، بلا فعل ولا مفعول ، أو فاعل . {{C|كس أمك}} ، هي اقتحام لل[[رجل]] ، أي رجل ، لأنه على حد علمي ، لم يولد رجل حتى الآن بلا [[الأم|أم]] ، وعلى حد علمي أيضا ، لم توجد [[المرأة|امرأة]] حتى الآن بلا {{C|كس}} ، وإن وجدت ، في [[رامبو|خارقة طبيعية]] ، فهي لم تلد ، أي أنها لم تصبح أما ، أي أنه لم يوجد لها رجل طويل عريض يمكن أن يقال له {{C|كس}} امك . حتى [[المسيح]] عليه [[السلام]] كان بلا [[الأب|اب]] ولكنه لا يستطيع الهرب من هذه الشتيمة [[غباء|الغبية]] . قد تكون اختصار لجملة (عير بكس أمك) ، هنا سنكون أمام جملة اسمية مكونة من مبتدأ هو (عير) وخبره شبه جملة مكونة من حرف الجر (ب) وإسم مجرور بحرف الجر (كس) أما (أمك) فهي مضافة الى [[الاسم]] المجرور (كس) ، واختصاراً لطول الجملة حُذِفَ المبتدأ وحُذِف حرف الجر فأصبحت العبارة (كس أمك).
Blocking policy
Protection policy


أن يقول رجل لرجل {{C|كس}} أمك فهذا يعني تمزيقا عنيفا ل[[رجولة|رجولته]] ، تذكيره بأن أمه هي ست في الأول وفي الآخر وهي عار يمكن ان يقتحم في أي لحظة . الاقتحام تنبع قوته من كونه ليس [[علوم|معلوماتيا]] ، أنت لا تقول أمك [[شرموطة]] فيكذب هذه المعلومة ، ولا تصفه بابن الوسخة فيقول لك أنت اللي ابن ستين وسخة . إنها شتيمة بلا منفذ ، مقفولة على نفسها ، غير مفهومة . وإذا كنا نعيش في [[الشعب|مجتمع من العقلاء]] ، فالرد الوحيد على كلمة {{C|كس}} امك هو سؤال مندهش : ماله ؟ مشخور مثل {{C|كس}} أمك يا روح أمك ؟.
v
t
e


ذكورة كل من الجاني والضحية تتحالف لخلق الشتيمة ، بالأصح لخلق كونها شتيمة . المشتوم يشعر ب[[الإهانة]] فورما يتذكر أن أمه هي [[المرأة|امرأة]] ذات فرج ، وأن هذا الفرج ، علامة ضعفها الأزلي ، هو السبب في وجوده ، أن وجوده ملوث بالعار ، ملوث بال{{C|كس}} ، والشاتم يعرف كيفية النفاذ إلى المشتوم بتذكيره بهذا العار الذي لا يمحى . في هذا تتحالف {{C|كس}} امك مع يا ابن المتناكة ، ولأن كلنا [[الحيوانات|كائنات بشرية طبيعية]] فكلنا أولاد متناكة بلا شك ، أو بالأصح ، كلنا أولاد [[الجنس|متناكات]] ، كلنا ملوث بخطيئة وجودنا من صلب كائن يأخذ فيها. غالبا ترتبط كس امك بلفظ اخر مسئ للرجل مثل كس امك يا [[خول]] او كس امك يا معرص وهناك تعبير اخر مثل هطلع كس امك بس محدش عارف هيطلعه منين من الكلوت ولا هيطلعه منين بالظبط وهناك ايضا هنيك كس امك
Gold padlock
==تاريخيا==
Fully protected
كس أمك كغيرها من العبارات النابية في الثقافات الأخرى '''كفك يو''' ب[[بريطانيا|الإنكليزية]] و '''أرش لوخ''' ب[[المانيا|الامانية]] كلمة [[كتابة بريل|لا معنى لها]] لغويا , يعتقد البعض ان الجملة قد تم اختصارها من مصطلحات لغوية أكثر طولا لسهولة اللفظ و كثرة الطلب , قد تذهل عندما تعرف ان [[العرب]] القدماء لم يكونوا يتحرجون من ال[[شتيمة]] كثيرا فهذا [[العالم]] الجليل السيوطي الذي أفنى عمره كله ما بين [[القرآن]] و الفقه و الأيمان و التقوى يتفرغ لتأليف كتاب مشهور أسمه '''نواضر الأيك في معرفة النيك''', تخيل ان [[الشعراوي]] رحمه [[الله]] يكتب كتابا عنوانه : "'''جلي الغمة عمن [[جهل]] قدر {{C|كس}} أمه'''" لتفهم ان تخلف الأمة [[العقلية العربية|تخلف جماعي]] حتى في الشتيمة , من الجمل التي قد تكون أصلا لعبارة {{C|كس}} أمك هي '''يا عاض بظر أمك''' و يبدو انها الشتيمة (الغير مفهومة أيضا) الأكثر استخداما في عصر [[الصحابة]] المحجلين رضوان الله عليهم كما قال سيدنا [[عثمان|ذو النورين]] رضي الله عنه لسيدنا عمار بن ياسر : '''يا عاض [[قضيب|أير]] أبيك'''[1], مع الأخذ بنظر الإعتبار حياء سيدنا عثمان فلا يمكننا ان نتخيل ما سيقوله رجل مهذار مثل [[عمرو بن العاص|عمرو بن العاص]] مثلا .
Pink padlock
Template-protected
Silver padlock
Semi-protected
Blue padlock
Create protected
Green padlock
Move protected
Purple padlock
Upload protected
White padlock
Pending changes protected (level 1)
Orange padlock
Pending changes protected (level 2)
Red padlock
Permanently protected
Black padlock
Protected by Office


كما كان [[الصحابة|الصحابي]] [[ابو بكر]] الصديق بارعا في استعمال هذه العبارة كما جاء في كتاب السيرة الحلبية في فصل غزوة الحديبية حيث قال لعروة بن مسعود الثقفي : اعضض [[بظر]] اللات. والبظر. قطعة تبقى في فرج [[المرأة]] بعد [[الختان]]، وقيل التي تقطعها الخاتنة علما ان اللات ربما لم يتم ختانها لانها اصلا [[تمثال|صنم]] روماني لفينوس العارية منحوت من المرمر واستوردها [[العرب]] من الشام خلال رحلة الصيف وكان [[العرب]] يسجدون لها في الجاهلية ومنهم الصحابي ابو بكر الصديق فأنطبع منظر بظرها في مخيلتهم وجرى على لسانهم.
Wikipedia is built around 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. However, in particular circumstances, because of a specifically identified likelihood of damage resulting if editing is left open, some individual pages may need to be subject to technical restrictions (often only temporary) on who is permitted to modify them. The placing of such restrictions on pages is called protection.
== استعمالاتها ==
* عندما يمر [[سيارة_مفخخة|سائق]] في [[عمان (الأردن)|عمان]] بغير مسربه ويقترب بشدة منك، وحين تطلق الزامور منبها يمد يده بحركة [[عصب]]ية متذمرة أو يخرج لك الأصبع الوسطى.
* عندما تحاول [[الموت|النوم]] ليلا بعد نهار مضني ومتعب ويبدأ ابن الجيران ب[[كأس_العالم_لكرة_القدم|لعب الكرة]] على باب العمارة الحديدي الساعة الواحدة ليلا.
* عندما تطلب من [[مدير]]ك زيادة على راتبك بعد مرور 5 سنوات ويقول لك : [[كذاب|"سأفكر في الموضوع"]].
* عندما تعود الى المنزل وتجد أن [[تزاوج|حرمك المصون]] لم [[خميعة|تطبخ]] رغم أن اليوم يوم عطلتها.
* عندما تنتظر 4 ساعات في [[دائرة حكومية|دائرة الأحوال المدنية]] أو الأراضي وثم يخبرك ال[[موظف]] بأن السيستم معطل وعليك القدوم غدا أو انتظار العناية الالهية ل[[شارون|يستيقظ مجددا فجأة]].
* عندما يسجل جوز شاكيرا هدفا في مرماه أمام [[كريستيانو_رونالدو|ريال مدريد]].
* عندما تكون [[لبنان]]يا و [[وزير]] خارجيتك [[جبران باسيل]]


==بالزنجباري==
Protection can be applied to or removed from pages by Wikipedia's administrators, although any user may request these actions. Protection can be indefinite, or expire after a specified time period.
* '''في [[المغرب|الجنوب]]:''' {{C|طبون}} مك
* '''في [[المغرب|الشمال]]:''' {{C|السوة}} ديماك
==من مشاهير مستخدميها==
* ناتالي بورتمان. (ما هي سبتك المفضلة؟) [https://www.youtube.com/watch?v=xAhff8IxsSI]
===المصادر===
* [1] [[علم الأنساب|أنساب]] الأشراف 5: 54؛ راجع أيضاً: تاريخ اليعقوبي 2: 150؛ طبقات ابن سعد 4: 168؛ المسعودي 1: 438.
* [http://naelaltoukhy.blogspot.com/2007/08/blog-post_10.html نائل الطوخي - في بحث عن معنى لكس أمك] .
* لعبة الكلمات المتقاطعة باب كلمة من حرفين تقال لأحد [[حريم|المحارم]] .


{{جسم الإنسان}}
The most commonly encountered types of protection are full protection, which means that a page can be modified only by administrators, and semi-protection, which means that a page can be modified only by users who are logged in and whose accounts have been confirmed (any account is automatically confirmed if it is at least four days old and has made at least ten edits or posts). Other forms of protection are detailed below. Protected pages are normally marked with a small padlock symbol in the top corner; different color padlocks represent different protection types, as shown in the images at the right. Template:Pp-protected is usually used to display the padlock.
[[تصنيف:تشريح]]

[[تصنيف:مصطلحات]]
Positioning the mouse pointer over the padlock symbol produces an informational tooltip which says "This article is (semi-)protected." If {{Pp-protected}}'s reason parameter is specified, the tooltip also says why the page is protected. If the expiry parameter is specified, the tooltip says for what duration the page is protected.
[[تصنيف:جسم الإنسان]]

[[تصنيف:صفحات للتحقق]]
This policy explains in detail the protection types and procedures for page protection and unprotection, and the reasons for which protection should and should not be applied.

Contents

1 Overview of types of protection
2 Types of protection
2.1 Full protection
2.1.1 Content disputes
2.1.2 Vandalism
2.1.3 "History only" review
2.1.4 Protected generic image names
2.2 Template protection
2.3 Semi-protection
2.3.1 Guidance for administrators
2.4 Creation protection
2.5 Move protection
2.6 Upload protection
2.7 Pending changes protection
2.7.1 When to apply pending changes protection
2.8 Permanent protection
2.9 Office actions
2.10 Cascading protection
2.11 Comparison table
3 Protection by namespace
3.1 Talk pages
3.1.1 User talk pages
3.1.1.1 Blocked users
3.2 User pages
3.2.1 Deceased users
3.3 Protection of templates
3.4 Sandboxes
4 Available templates
5 See also
6 Notes

Overview of types of protection

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

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 that are not confirmed.
Creation protection prevents a page (normally a previously deleted one) from being recreated (also known as "salting").
Move protection protects the page solely from renaming/moving.
Upload protection prevents new versions of a file from being uploaded except by administrators, but it does not prevent editing the file's description page.
Pending-changes protection means edits by unregistered and new contributors are not visible to readers who are not logged in, until the edits are approved by a reviewer or administrator.

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 by an administrator if they are uncontroversial or if there is consensus for them.

Except in the case of office actions (see below) or pages in the MediaWiki namespace (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.
Types of protection

Full protection
Gold padlock
Policy shortcuts:

WP:FPP
WP:FULL
WP:FULL-PRO
WP:GOLDLOCK

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

Content disputes

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.

Policy shortcut:

WP:PREFER

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.
Vandalism
Policy shortcut:

WP:NO-PREEMPT

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.
"History only" review

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.
Protected generic image names

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.

Template protection
Pink padlock
Policy shortcuts:

WP:TEMP-P
WP:TEMP-PRO
WP:TPROT
WP:PINKLOCK

Main page: Wikipedia:Template editor

A template-protected page can be edited only by administrators or users in the Template editors group. This protection level may only be used on high-risk templates and modules, and possibly in rarer cases where pages in other namespaces become transcluded to a very high degree.

This is a new protection level[1] that replaces full protection on pages that are merely protected due to high transclusion rates, rather than content disputes. It should only 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 template editor user right exists – the existence of the right should not result in more templates becoming uneditable for the general editor population.

Semi-protection
Silver padlock
Policy shortcuts:

WP:S-P
WP:SPP
WP:SEMI
WP:SEMI-PRO
WP:SILVERLOCK

See also: Wikipedia:Rough guide to semi-protection

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 at least ten 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.
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, nor should it be used 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) 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. 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, 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 reblocked with talk page editing disallowed. When required, or when reblocking without talk page editing allowed is unsuccessful, protection should be implemented for only a brief period, and not exceeding the duration of the block.

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.

Creation protection
Blue padlock
Policy shortcuts:

WP:SALT
WP:PDP
WP:BLUELOCK

Administrators can prevent the creation of a page through the protection interface. This is useful for articles that have been deleted but repeatedly recreated. 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 (look for one who was previously involved) or use the deletion review process.

There are two levels of creation protection that can be applied to pages. One version is similar to semi-protection which allows autoconfirmed editors to create the page. The other version is similar to full protection which allows only administrators to create the page.

Move protection
Green padlock
Policy shortcuts:

WP:MOVP
WP:MOVE-PRO
WP:GREENLOCK

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 and articles selected as "Today's featured article" on the main page.

Fully protected pages are also move-protected.

As with full protection, protection because of editwarring 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.

Upload protection
Purple padlock
Policy shortcuts:

WP:UPLOAD-P
WP:PURPLELOCK

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.

Pending changes protection
Further information: Wikipedia:Pending changes
Policy shortcuts:

WP:PCPP
WP:WHITELOCK
WP:ORANGELOCK

White padlock Orange padlock

Pending changes protection is a tool used to suppress vandalism and certain other persistent problems, while allowing all users to continue to submit edits. Pending changes protection can be used as an alternative to semi-protection to allow unregistered and new users to edit pages, while keeping the edits hidden to most readers until they are accepted by a 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 reviewer right.

Pending changes are visible in the page history, where they are marked as pending review. The latest accepted revision is displayed to the general public. Logged-in users see the latest revision of the page, with all changes 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.

Both logged-in users and anonymous users who click the "edit this page" tab may edit the latest version as usual. If there are pending changes awaiting review, there will be a dropdown box next to the article title, pointing to the pending changes. For more details, see Help:Pending changes.

Reviewing of pending changes should be resolved within reasonable time limits. Backlog management should be coordinated at a community level.
When to apply pending changes protection

Pending changes may be used to protect articles against:

persistent vandalism
violations of the biographies of living persons policy
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 only be used in cases of severe long-term disruption.

Only what is known as "Pending changes level 1" should be used, which is labeled "Require review for revisions from new and unregistered users". Pending changes level 2, or "Require review for revisions from everyone except Reviewers", should not be used at this time per WP:PC2012/RfC 1.

Removal of pending changes protection can be requested of any administrator, or at requests for unprotection.

The reviewing process is described in detail at reviewing.

Permanent protection
Red padlock
Policy shortcuts:

WP:PPINDEF
WP:PERM-PRO
WP:REDLOCK

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

Office actions
Black padlock
Policy shortcuts:

WP:WMF-P
WP:WMF-PRO
WP:BLACKLOCK

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
Shortcuts:

WP:CASCADE
WP:CASCADING

"WP:CASCADE" redirects here. You may be also looking for Wikipedia:Cascading style sheets.

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 "Protection of templates" section below for alternatives.

Comparison table

The following table compares the effects of protection on Wikipedia users.
Wikipedia users, page protections, and page edits Unregistered, New Autoconfirmed, Confirmed Template editor Reviewer Administrator Appropriate for
No protection can edit;
changes go live* immediately;
no acceptance required The vast majority of pages
Pending changes
level 1 protection can edit;
changes will go live after being accepted by a reviewer can edit;
changes go live immediately (if no previous pending changes remain to be accepted) can edit;
changes go live immediately;**
can accept pending changes Infrequently edited articles that are experiencing high levels of vandalism or BLP violations from unregistered and new users
Semi-protection cannot edit can edit;
changes go live immediately;
no acceptance required Articles experiencing high levels of vandalism or edit warring from unregistered and new users, and for some highly visible templates and modules
Pending changes
level 2 protection can edit;
changes will go live after being accepted by a reviewer can edit;
changes go live immediately;
can accept pending changes No consensus for use on the English Wikipedia per WP:PC2012/RfC 1
Pending changes level 2 with Semi-protection cannot edit can edit;
changes will go live after being accepted by a reviewer can edit;
changes go live immediately;
can accept pending changes No consensus for use on the English Wikipedia per WP:PC2012/RfC 1
Template protection cannot edit can edit;
changes go live immediately;
no acceptance required cannot edit can edit;
changes go live immediately;
no acceptance required High-risk templates and modules
Full protection cannot edit can edit;
changes go live immediately;
no acceptance required Articles experiencing persistent vandalism or edit warring from (auto)confirmed accounts, and for critically important templates and modules
* "Go live" means the edits will be visible to readers who are not logged in. In all cases, edits are always visible to readers logged into Wikipedia.
** When editing articles with un-reviewed pending changes, Administrators and Reviewers are prompted to review the pending changes before saving their edit.
Protection by namespace
Talk pages

Modifications to a 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 protected}} template on the talk page will draw the attention of administrators for implementing uncontroversial changes.

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

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 pages are semi-protected should have an unprotected user talk subpage linked conspicuously from their main talk page to allow good faith comments from non-autoconfirmed users.

A user's request to have his or her own talk page protected is not a sufficient rationale to protect the page.
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 {{unblock}} template, re-blocking the user without talk page access should be preferred over protection. If the user has been indefinitely blocked from editing the talk page, they should be informed of off-wiki ways to appeal their block, such as the UTRS tool interface or ban appeals subcommittee of 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
Policy shortcuts:

WP:UPROT
WP:UPPROT

User pages and subpages can be protected by simple request from the user; this does not apply to the main user talk page. This is common for retired users and talk page archives.
Deceased users
See also: Wikipedia:Deceased Wikipedians/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: Wikipedia:High-risk templates and Wikipedia:Template documentation

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 template-protected based on the degree of visibility, type of use, content, and other factors.

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 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 template editors and account creators).
Sandboxes
See also: Wikipedia:About the Sandbox

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.
Available templates

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

v
t
e

{{pp-meta}} Full Semi Move
Dispute: {{pp-dispute}} {{pp-move-dispute}}
Vandalism: {{pp-vandalism}} {{pp-move-vandalism}}
High visibility templates and modules: {{pp-template}} N/A
User talk of blocked user: {{pp-usertalk}} N/A
Sockpuppetry: {{pp-sock}} N/A
WP:BLP: {{pp-blp}} N/A
Long-term: N/A {{pp-semi-indef}} {{pp-move-indef}}
Generic (other protection): {{pp-protected}} {{pp-move}}
Scrutiny of the Office: {{pp-office}} {{pp-reset}} N/A
Talk page info: {{permanently protected}} {{temporarily protected}} N/A
Create protection: {{pp-create}} N/A
Pending changes protection level 1: {{pp-pc1}} N/A
Pending changes protection level 2: {{pp-pc2}} N/A

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.
See also

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
Category:Wikipedia protected edit requests
Wikipedia:Protection policy/Padlocks

Notes

Created October 2013 as a result of Wikipedia:Requests for comment/Template editor user right‎

[show]

v
t
e

New admin
Categories:

Wikipedia policies
Wikipedia enforcement policies
Wikipedia New admin
Wikipedia vandalism
Wikipedia page protection

Navigation menu

Create account
Log in

Project page
Talk

Read
View source
View history

Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Wikimedia Shop

Interaction

Help
About Wikipedia
Community portal
Recent changes
Contact page

Tools
Print/export
Languages

Afrikaans
Ænglisc
العربية
Aragonés
অসমীয়া
বাংলা
Català
Cebuano
Čeština
Cymraeg
Dansk
Deutsch
ދިވެހިބަސް
Eesti
Ελληνικά
Español
Esperanto
فارسی
Français
Galego
한국어
Հայերեն
Hrvatski
Ilokano
Bahasa Indonesia
Íslenska
Italiano
עברית
Basa Jawa
ქართული
Latina
Lëtzebuergesch
Lietuvių
Magyar
Македонски
Malti
Bahasa Melayu
Монгол
Nederlands
नेपाली
日本語
Norsk bokmål
ଓଡ଼ିଆ
Oʻzbekcha
ភាសាខ្មែរ
Polski
Português
Română
Русский
Саха тыла
Sardu
සිංහල
Simple English
Slovenčina
Slovenščina
Soomaaliga
Српски / srpski
Basa Sunda
Suomi
Svenska
தமிழ்
తెలుగు
ไทย
Türkçe
Удмурт
Українська
Vèneto
Tiếng Việt
ייִדיש
粵語
中文

Edit links

This page was last modified on 6 May 2014 at 00:41.
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.

Privacy policy
About Wikipedia
Disclaimers
Contact Wikipedia
Developers
Mobile view

Wikimedia Foundation
Powered by MediaWiki


Wikipedia:Protection policy
From Wikipedia, the free encyclopedia
Page semi-protected
"WP:PP" redirects here. You may be looking for Wikipedia:Requests for page protection, Wikipedia:Lists of protected pages, Wikipedia:Perennial proposals or WikiProject Parliamentary Procedure.
"WP:PROTECT" redirects here. You may be looking for Wikipedia:Child protection or Wikipedia:WikiProject Protected areas.
Green check.svg This page documents an English Wikipedia policy, a widely accepted standard that all editors must normally follow. Changes made to it should reflect consensus.
Shortcuts:
WP:PP
WP:PROTECT
Enforcement policies

Administrators
Banning policy
Blocking policy
Protection policy

v
t
e

Gold padlock
Fully protected
Pink padlock
Template-protected
Silver padlock
Semi-protected
Blue padlock
Create protected
Green padlock
Move protected
Purple padlock
Upload protected
White padlock
Pending changes protected (level 1)
Orange padlock
Pending changes protected (level 2)
Red padlock
Permanently protected
Black padlock
Protected by Office

Wikipedia is built around 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. However, in particular circumstances, because of a specifically identified likelihood of damage resulting if editing is left open, some individual pages may need to be subject to technical restrictions (often only temporary) on who is permitted to modify them. The placing of such restrictions on pages is called protection.

Protection can be applied to or removed from pages by Wikipedia's administrators, although any user may request these actions. Protection can be indefinite, or expire after a specified time period.

The most commonly encountered types of protection are full protection, which means that a page can be modified only by administrators, and semi-protection, which means that a page can be modified only by users who are logged in and whose accounts have been confirmed (any account is automatically confirmed if it is at least four days old and has made at least ten edits or posts). Other forms of protection are detailed below. Protected pages are normally marked with a small padlock symbol in the top corner; different color padlocks represent different protection types, as shown in the images at the right. Template:Pp-protected is usually used to display the padlock.

Positioning the mouse pointer over the padlock symbol produces an informational tooltip which says "This article is (semi-)protected." If {{Pp-protected}}'s reason parameter is specified, the tooltip also says why the page is protected. If the expiry parameter is specified, the tooltip says for what duration the page is protected.

This policy explains in detail the protection types and procedures for page protection and unprotection, and the reasons for which protection should and should not be applied.

Contents

1 Overview of types of protection
2 Types of protection
2.1 Full protection
2.1.1 Content disputes
2.1.2 Vandalism
2.1.3 "History only" review
2.1.4 Protected generic image names
2.2 Template protection
2.3 Semi-protection
2.3.1 Guidance for administrators
2.4 Creation protection
2.5 Move protection
2.6 Upload protection
2.7 Pending changes protection
2.7.1 When to apply pending changes protection
2.8 Permanent protection
2.9 Office actions
2.10 Cascading protection
2.11 Comparison table
3 Protection by namespace
3.1 Talk pages
3.1.1 User talk pages
3.1.1.1 Blocked users
3.2 User pages
3.2.1 Deceased users
3.3 Protection of templates
3.4 Sandboxes
4 Available templates
5 See also
6 Notes

Overview of types of protection

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

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 that are not confirmed.
Creation protection prevents a page (normally a previously deleted one) from being recreated (also known as "salting").
Move protection protects the page solely from renaming/moving.
Upload protection prevents new versions of a file from being uploaded except by administrators, but it does not prevent editing the file's description page.
Pending-changes protection means edits by unregistered and new contributors are not visible to readers who are not logged in, until the edits are approved by a reviewer or administrator.

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 by an administrator if they are uncontroversial or if there is consensus for them.

Except in the case of office actions (see below) or pages in the MediaWiki namespace (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.
Types of protection

Full protection
Gold padlock
Policy shortcuts:

WP:FPP
WP:FULL
WP:FULL-PRO
WP:GOLDLOCK

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

Content disputes

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.

Policy shortcut:

WP:PREFER

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.
Vandalism
Policy shortcut:

WP:NO-PREEMPT

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.
"History only" review

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.
Protected generic image names

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.

Template protection
Pink padlock
Policy shortcuts:

WP:TEMP-P
WP:TEMP-PRO
WP:TPROT
WP:PINKLOCK

Main page: Wikipedia:Template editor

A template-protected page can be edited only by administrators or users in the Template editors group. This protection level may only be used on high-risk templates and modules, and possibly in rarer cases where pages in other namespaces become transcluded to a very high degree.

This is a new protection level[1] that replaces full protection on pages that are merely protected due to high transclusion rates, rather than content disputes. It should only 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 template editor user right exists – the existence of the right should not result in more templates becoming uneditable for the general editor population.

Semi-protection
Silver padlock
Policy shortcuts:

WP:S-P
WP:SPP
WP:SEMI
WP:SEMI-PRO
WP:SILVERLOCK

See also: Wikipedia:Rough guide to semi-protection

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 at least ten 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.
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, nor should it be used 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) 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. 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, 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 reblocked with talk page editing disallowed. When required, or when reblocking without talk page editing allowed is unsuccessful, protection should be implemented for only a brief period, and not exceeding the duration of the block.

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.

Creation protection
Blue padlock
Policy shortcuts:

WP:SALT
WP:PDP
WP:BLUELOCK

Administrators can prevent the creation of a page through the protection interface. This is useful for articles that have been deleted but repeatedly recreated. 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 (look for one who was previously involved) or use the deletion review process.

There are two levels of creation protection that can be applied to pages. One version is similar to semi-protection which allows autoconfirmed editors to create the page. The other version is similar to full protection which allows only administrators to create the page.

Move protection
Green padlock
Policy shortcuts:

WP:MOVP
WP:MOVE-PRO
WP:GREENLOCK

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 and articles selected as "Today's featured article" on the main page.

Fully protected pages are also move-protected.

As with full protection, protection because of editwarring 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.

Upload protection
Purple padlock
Policy shortcuts:

WP:UPLOAD-P
WP:PURPLELOCK

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.

Pending changes protection
Further information: Wikipedia:Pending changes
Policy shortcuts:

WP:PCPP
WP:WHITELOCK
WP:ORANGELOCK

White padlock Orange padlock

Pending changes protection is a tool used to suppress vandalism and certain other persistent problems, while allowing all users to continue to submit edits. Pending changes protection can be used as an alternative to semi-protection to allow unregistered and new users to edit pages, while keeping the edits hidden to most readers until they are accepted by a 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 reviewer right.

Pending changes are visible in the page history, where they are marked as pending review. The latest accepted revision is displayed to the general public. Logged-in users see the latest revision of the page, with all changes 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.

Both logged-in users and anonymous users who click the "edit this page" tab may edit the latest version as usual. If there are pending changes awaiting review, there will be a dropdown box next to the article title, pointing to the pending changes. For more details, see Help:Pending changes.

Reviewing of pending changes should be resolved within reasonable time limits. Backlog management should be coordinated at a community level.
When to apply pending changes protection

Pending changes may be used to protect articles against:

persistent vandalism
violations of the biographies of living persons policy
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 only be used in cases of severe long-term disruption.

Only what is known as "Pending changes level 1" should be used, which is labeled "Require review for revisions from new and unregistered users". Pending changes level 2, or "Require review for revisions from everyone except Reviewers", should not be used at this time per WP:PC2012/RfC 1.

Removal of pending changes protection can be requested of any administrator, or at requests for unprotection.

The reviewing process is described in detail at reviewing.

Permanent protection
Red padlock
Policy shortcuts:

WP:PPINDEF
WP:PERM-PRO
WP:REDLOCK

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

Office actions
Black padlock
Policy shortcuts:

WP:WMF-P
WP:WMF-PRO
WP:BLACKLOCK

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
Shortcuts:

WP:CASCADE
WP:CASCADING

"WP:CASCADE" redirects here. You may be also looking for Wikipedia:Cascading style sheets.

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 "Protection of templates" section below for alternatives.

Comparison table

The following table compares the effects of protection on Wikipedia users.
Wikipedia users, page protections, and page edits Unregistered, New Autoconfirmed, Confirmed Template editor Reviewer Administrator Appropriate for
No protection can edit;
changes go live* immediately;
no acceptance required The vast majority of pages
Pending changes
level 1 protection can edit;
changes will go live after being accepted by a reviewer can edit;
changes go live immediately (if no previous pending changes remain to be accepted) can edit;
changes go live immediately;**
can accept pending changes Infrequently edited articles that are experiencing high levels of vandalism or BLP violations from unregistered and new users
Semi-protection cannot edit can edit;
changes go live immediately;
no acceptance required Articles experiencing high levels of vandalism or edit warring from unregistered and new users, and for some highly visible templates and modules
Pending changes
level 2 protection can edit;
changes will go live after being accepted by a reviewer can edit;
changes go live immediately;
can accept pending changes No consensus for use on the English Wikipedia per WP:PC2012/RfC 1
Pending changes level 2 with Semi-protection cannot edit can edit;
changes will go live after being accepted by a reviewer can edit;
changes go live immediately;
can accept pending changes No consensus for use on the English Wikipedia per WP:PC2012/RfC 1
Template protection cannot edit can edit;
changes go live immediately;
no acceptance required cannot edit can edit;
changes go live immediately;
no acceptance required High-risk templates and modules
Full protection cannot edit can edit;
changes go live immediately;
no acceptance required Articles experiencing persistent vandalism or edit warring from (auto)confirmed accounts, and for critically important templates and modules
* "Go live" means the edits will be visible to readers who are not logged in. In all cases, edits are always visible to readers logged into Wikipedia.
** When editing articles with un-reviewed pending changes, Administrators and Reviewers are prompted to review the pending changes before saving their edit.
Protection by namespace
Talk pages

Modifications to a 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 protected}} template on the talk page will draw the attention of administrators for implementing uncontroversial changes.

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

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 pages are semi-protected should have an unprotected user talk subpage linked conspicuously from their main talk page to allow good faith comments from non-autoconfirmed users.

A user's request to have his or her own talk page protected is not a sufficient rationale to protect the page.
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 {{unblock}} template, re-blocking the user without talk page access should be preferred over protection. If the user has been indefinitely blocked from editing the talk page, they should be informed of off-wiki ways to appeal their block, such as the UTRS tool interface or ban appeals subcommittee of 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
Policy shortcuts:

WP:UPROT
WP:UPPROT

User pages and subpages can be protected by simple request from the user; this does not apply to the main user talk page. This is common for retired users and talk page archives.
Deceased users
See also: Wikipedia:Deceased Wikipedians/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: Wikipedia:High-risk templates and Wikipedia:Template documentation

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 template-protected based on the degree of visibility, type of use, content, and other factors.

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 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 template editors and account creators).
Sandboxes
See also: Wikipedia:About the Sandbox

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.
Available templates

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

v
t
e

{{pp-meta}} Full Semi Move
Dispute: {{pp-dispute}} {{pp-move-dispute}}
Vandalism: {{pp-vandalism}} {{pp-move-vandalism}}
High visibility templates and modules: {{pp-template}} N/A
User talk of blocked user: {{pp-usertalk}} N/A
Sockpuppetry: {{pp-sock}} N/A
WP:BLP: {{pp-blp}} N/A
Long-term: N/A {{pp-semi-indef}} {{pp-move-indef}}
Generic (other protection): {{pp-protected}} {{pp-move}}
Scrutiny of the Office: {{pp-office}} {{pp-reset}} N/A
Talk page info: {{permanently protected}} {{temporarily protected}} N/A
Create protection: {{pp-create}} N/A
Pending changes protection level 1: {{pp-pc1}} N/A
Pending changes protection level 2: {{pp-pc2}} N/A

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.
See also

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
Category:Wikipedia protected edit requests
Wikipedia:Protection policy/Padlocks

Notes

Created October 2013 as a result of Wikipedia:Requests for comment/Template editor user right‎

[show]

v
t
e

New admin
Categories:

Wikipedia policies
Wikipedia enforcement policies
Wikipedia New admin
Wikipedia vandalism
Wikipedia page protection

Navigation menu

Create account
Log in

Project page
Talk

Read
View source
View history

Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Wikimedia Shop

Interaction

Help
About Wikipedia
Community portal
Recent changes
Contact page

Tools
Print/export
Languages

Afrikaans
Ænglisc
العربية
Aragonés
অসমীয়া
বাংলা
Català
Cebuano
Čeština
Cymraeg
Dansk
Deutsch
ދިވެހިބަސް
Eesti
Ελληνικά
Español
Esperanto
فارسی
Français
Galego
한국어
Հայերեն
Hrvatski
Ilokano
Bahasa Indonesia
Íslenska
Italiano
עברית
Basa Jawa
ქართული
Latina
Lëtzebuergesch
Lietuvių
Magyar
Македонски
Malti
Bahasa Melayu
Монгол
Nederlands
नेपाली
日本語
Norsk bokmål
ଓଡ଼ିଆ
Oʻzbekcha
ភាសាខ្មែរ
Polski
Português
Română
Русский
Саха тыла
Sardu
සිංහල
Simple English
Slovenčina
Slovenščina
Soomaaliga
Српски / srpski
Basa Sunda
Suomi
Svenska
தமிழ்
తెలుగు
ไทย
Türkçe
Удмурт
Українська
Vèneto
Tiếng Việt
ייִדיש
粵語
中文

Edit links

This page was last modified on 6 May 2014 at 00:41.
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.

Privacy policy
About Wikipedia
Disclaimers
Contact Wikipedia
Developers
Mobile view

Wikimedia Foundation
Powered by MediaWiki


Wikipedia:Protection policy
From Wikipedia, the free encyclopedia
Page semi-protected
"WP:PP" redirects here. You may be looking for Wikipedia:Requests for page protection, Wikipedia:Lists of protected pages, Wikipedia:Perennial proposals or WikiProject Parliamentary Procedure.
"WP:PROTECT" redirects here. You may be looking for Wikipedia:Child protection or Wikipedia:WikiProject Protected areas.
Green check.svg This page documents an English Wikipedia policy, a widely accepted standard that all editors must normally follow. Changes made to it should reflect consensus.
Shortcuts:
WP:PP
WP:PROTECT
Enforcement policies

Administrators
Banning policy
Blocking policy
Protection policy

v
t
e

Gold padlock
Fully protected
Pink padlock
Template-protected
Silver padlock
Semi-protected
Blue padlock
Create protected
Green padlock
Move protected
Purple padlock
Upload protected
White padlock
Pending changes protected (level 1)
Orange padlock
Pending changes protected (level 2)
Red padlock
Permanently protected
Black padlock
Protected by Office

Wikipedia is built around 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. However, in particular circumstances, because of a specifically identified likelihood of damage resulting if editing is left open, some individual pages may need to be subject to technical restrictions (often only temporary) on who is permitted to modify them. The placing of such restrictions on pages is called protection.

Protection can be applied to or removed from pages by Wikipedia's administrators, although any user may request these actions. Protection can be indefinite, or expire after a specified time period.

The most commonly encountered types of protection are full protection, which means that a page can be modified only by administrators, and semi-protection, which means that a page can be modified only by users who are logged in and whose accounts have been confirmed (any account is automatically confirmed if it is at least four days old and has made at least ten edits or posts). Other forms of protection are detailed below. Protected pages are normally marked with a small padlock symbol in the top corner; different color padlocks represent different protection types, as shown in the images at the right. Template:Pp-protected is usually used to display the padlock.

Positioning the mouse pointer over the padlock symbol produces an informational tooltip which says "This article is (semi-)protected." If {{Pp-protected}}'s reason parameter is specified, the tooltip also says why the page is protected. If the expiry parameter is specified, the tooltip says for what duration the page is protected.

This policy explains in detail the protection types and procedures for page protection and unprotection, and the reasons for which protection should and should not be applied.

Contents

1 Overview of types of protection
2 Types of protection
2.1 Full protection
2.1.1 Content disputes
2.1.2 Vandalism
2.1.3 "History only" review
2.1.4 Protected generic image names
2.2 Template protection
2.3 Semi-protection
2.3.1 Guidance for administrators
2.4 Creation protection
2.5 Move protection
2.6 Upload protection
2.7 Pending changes protection
2.7.1 When to apply pending changes protection
2.8 Permanent protection
2.9 Office actions
2.10 Cascading protection
2.11 Comparison table
3 Protection by namespace
3.1 Talk pages
3.1.1 User talk pages
3.1.1.1 Blocked users
3.2 User pages
3.2.1 Deceased users
3.3 Protection of templates
3.4 Sandboxes
4 Available templates
5 See also
6 Notes

Overview of types of protection

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

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 that are not confirmed.
Creation protection prevents a page (normally a previously deleted one) from being recreated (also known as "salting").
Move protection protects the page solely from renaming/moving.
Upload protection prevents new versions of a file from being uploaded except by administrators, but it does not prevent editing the file's description page.
Pending-changes protection means edits by unregistered and new contributors are not visible to readers who are not logged in, until the edits are approved by a reviewer or administrator.

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 by an administrator if they are uncontroversial or if there is consensus for them.

Except in the case of office actions (see below) or pages in the MediaWiki namespace (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.
Types of protection

Full protection
Gold padlock
Policy shortcuts:

WP:FPP
WP:FULL
WP:FULL-PRO
WP:GOLDLOCK

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

Content disputes

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.

Policy shortcut:

WP:PREFER

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.
Vandalism
Policy shortcut:

WP:NO-PREEMPT

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.
"History only" review

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.
Protected generic image names

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.

Template protection
Pink padlock
Policy shortcuts:

WP:TEMP-P
WP:TEMP-PRO
WP:TPROT
WP:PINKLOCK

Main page: Wikipedia:Template editor

A template-protected page can be edited only by administrators or users in the Template editors group. This protection level may only be used on high-risk templates and modules, and possibly in rarer cases where pages in other namespaces become transcluded to a very high degree.

This is a new protection level[1] that replaces full protection on pages that are merely protected due to high transclusion rates, rather than content disputes. It should only 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 template editor user right exists – the existence of the right should not result in more templates becoming uneditable for the general editor population.

Semi-protection
Silver padlock
Policy shortcuts:

WP:S-P
WP:SPP
WP:SEMI
WP:SEMI-PRO
WP:SILVERLOCK

See also: Wikipedia:Rough guide to semi-protection

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 at least ten 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.
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, nor should it be used 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) 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. 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, 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 reblocked with talk page editing disallowed. When required, or when reblocking without talk page editing allowed is unsuccessful, protection should be implemented for only a brief period, and not exceeding the duration of the block.

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.

Creation protection
Blue padlock
Policy shortcuts:

WP:SALT
WP:PDP
WP:BLUELOCK

Administrators can prevent the creation of a page through the protection interface. This is useful for articles that have been deleted but repeatedly recreated. 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 (look for one who was previously involved) or use the deletion review process.

There are two levels of creation protection that can be applied to pages. One version is similar to semi-protection which allows autoconfirmed editors to create the page. The other version is similar to full protection which allows only administrators to create the page.

Move protection
Green padlock
Policy shortcuts:

WP:MOVP
WP:MOVE-PRO
WP:GREENLOCK

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 and articles selected as "Today's featured article" on the main page.

Fully protected pages are also move-protected.

As with full protection, protection because of editwarring 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.

Upload protection
Purple padlock
Policy shortcuts:

WP:UPLOAD-P
WP:PURPLELOCK

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.

Pending changes protection
Further information: Wikipedia:Pending changes
Policy shortcuts:

WP:PCPP
WP:WHITELOCK
WP:ORANGELOCK

White padlock Orange padlock

Pending changes protection is a tool used to suppress vandalism and certain other persistent problems, while allowing all users to continue to submit edits. Pending changes protection can be used as an alternative to semi-protection to allow unregistered and new users to edit pages, while keeping the edits hidden to most readers until they are accepted by a 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 reviewer right.

Pending changes are visible in the page history, where they are marked as pending review. The latest accepted revision is displayed to the general public. Logged-in users see the latest revision of the page, with all changes 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.

Both logged-in users and anonymous users who click the "edit this page" tab may edit the latest version as usual. If there are pending changes awaiting review, there will be a dropdown box next to the article title, pointing to the pending changes. For more details, see Help:Pending changes.

Reviewing of pending changes should be resolved within reasonable time limits. Backlog management should be coordinated at a community level.
When to apply pending changes protection

Pending changes may be used to protect articles against:

persistent vandalism
violations of the biographies of living persons policy
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 only be used in cases of severe long-term disruption.

Only what is known as "Pending changes level 1" should be used, which is labeled "Require review for revisions from new and unregistered users". Pending changes level 2, or "Require review for revisions from everyone except Reviewers", should not be used at this time per WP:PC2012/RfC 1.

Removal of pending changes protection can be requested of any administrator, or at requests for unprotection.

The reviewing process is described in detail at reviewing.

Permanent protection
Red padlock
Policy shortcuts:

WP:PPINDEF
WP:PERM-PRO
WP:REDLOCK

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

Office actions
Black padlock
Policy shortcuts:

WP:WMF-P
WP:WMF-PRO
WP:BLACKLOCK

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
Shortcuts:

WP:CASCADE
WP:CASCADING

"WP:CASCADE" redirects here. You may be also looking for Wikipedia:Cascading style sheets.

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 "Protection of templates" section below for alternatives.

Comparison table

The following table compares the effects of protection on Wikipedia users.
Wikipedia users, page protections, and page edits Unregistered, New Autoconfirmed, Confirmed Template editor Reviewer Administrator Appropriate for
No protection can edit;
changes go live* immediately;
no acceptance required The vast majority of pages
Pending changes
level 1 protection can edit;
changes will go live after being accepted by a reviewer can edit;
changes go live immediately (if no previous pending changes remain to be accepted) can edit;
changes go live immediately;**
can accept pending changes Infrequently edited articles that are experiencing high levels of vandalism or BLP violations from unregistered and new users
Semi-protection cannot edit can edit;
changes go live immediately;
no acceptance required Articles experiencing high levels of vandalism or edit warring from unregistered and new users, and for some highly visible templates and modules
Pending changes
level 2 protection can edit;
changes will go live after being accepted by a reviewer can edit;
changes go live immediately;
can accept pending changes No consensus for use on the English Wikipedia per WP:PC2012/RfC 1
Pending changes level 2 with Semi-protection cannot edit can edit;
changes will go live after being accepted by a reviewer can edit;
changes go live immediately;
can accept pending changes No consensus for use on the English Wikipedia per WP:PC2012/RfC 1
Template protection cannot edit can edit;
changes go live immediately;
no acceptance required cannot edit can edit;
changes go live immediately;
no acceptance required High-risk templates and modules
Full protection cannot edit can edit;
changes go live immediately;
no acceptance required Articles experiencing persistent vandalism or edit warring from (auto)confirmed accounts, and for critically important templates and modules
* "Go live" means the edits will be visible to readers who are not logged in. In all cases, edits are always visible to readers logged into Wikipedia.
** When editing articles with un-reviewed pending changes, Administrators and Reviewers are prompted to review the pending changes before saving their edit.
Protection by namespace
Talk pages

Modifications to a 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 protected}} template on the talk page will draw the attention of administrators for implementing uncontroversial changes.

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

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 pages are semi-protected should have an unprotected user talk subpage linked conspicuously from their main talk page to allow good faith comments from non-autoconfirmed users.

A user's request to have his or her own talk page protected is not a sufficient rationale to protect the page.
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 {{unblock}} template, re-blocking the user without talk page access should be preferred over protection. If the user has been indefinitely blocked from editing the talk page, they should be informed of off-wiki ways to appeal their block, such as the UTRS tool interface or ban appeals subcommittee of 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
Policy shortcuts:

WP:UPROT
WP:UPPROT

User pages and subpages can be protected by simple request from the user; this does not apply to the main user talk page. This is common for retired users and talk page archives.
Deceased users
See also: Wikipedia:Deceased Wikipedians/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: Wikipedia:High-risk templates and Wikipedia:Template documentation

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 template-protected based on the degree of visibility, type of use, content, and other factors.

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 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 template editors and account creators).
Sandboxes
See also: Wikipedia:About the Sandbox

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.
Available templates

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

v
t
e

{{pp-meta}} Full Semi Move
Dispute: {{pp-dispute}} {{pp-move-dispute}}
Vandalism: {{pp-vandalism}} {{pp-move-vandalism}}
High visibility templates and modules: {{pp-template}} N/A
User talk of blocked user: {{pp-usertalk}} N/A
Sockpuppetry: {{pp-sock}} N/A
WP:BLP: {{pp-blp}} N/A
Long-term: N/A {{pp-semi-indef}} {{pp-move-indef}}
Generic (other protection): {{pp-protected}} {{pp-move}}
Scrutiny of the Office: {{pp-office}} {{pp-reset}} N/A
Talk page info: {{permanently protected}} {{temporarily protected}} N/A
Create protection: {{pp-create}} N/A
Pending changes protection level 1: {{pp-pc1}} N/A
Pending changes protection level 2: {{pp-pc2}} N/A

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.
See also

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
Category:Wikipedia protected edit requests
Wikipedia:Protection policy/Padlocks

Notes

Created October 2013 as a result of Wikipedia:Requests for comment/Template editor user right‎

[show]

v
t
e

New admin
Categories:

Wikipedia policies
Wikipedia enforcement policies
Wikipedia New admin
Wikipedia vandalism
Wikipedia page protection

Navigation menu

Create account
Log in

Project page
Talk

Read
View source
View history

Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Wikimedia Shop

Interaction

Help
About Wikipedia
Community portal
Recent changes
Contact page

Tools
Print/export
Languages

Afrikaans
Ænglisc
العربية
Aragonés
অসমীয়া
বাংলা
Català
Cebuano
Čeština
Cymraeg
Dansk
Deutsch
ދިވެހިބަސް
Eesti
Ελληνικά
Español
Esperanto
فارسی
Français
Galego
한국어
Հայերեն
Hrvatski
Ilokano
Bahasa Indonesia
Íslenska
Italiano
עברית
Basa Jawa
ქართული
Latina
Lëtzebuergesch
Lietuvių
Magyar
Македонски
Malti
Bahasa Melayu
Монгол
Nederlands
नेपाली
日本語
Norsk bokmål
ଓଡ଼ିଆ
Oʻzbekcha
ភាសាខ្មែរ
Polski
Português
Română
Русский
Саха тыла
Sardu
සිංහල
Simple English
Slovenčina
Slovenščina
Soomaaliga
Српски / srpski
Basa Sunda
Suomi
Svenska
தமிழ்
తెలుగు
ไทย
Türkçe
Удмурт
Українська
Vèneto
Tiếng Việt
ייִדיש
粵語
中文

Edit links

This page was last modified on 6 May 2014 at 00:41.
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.

Privacy policy
About Wikipedia
Disclaimers
Contact Wikipedia
Developers
Mobile view

Wikimedia Foundation
Powered by MediaWiki


Wikipedia:Protection policy
From Wikipedia, the free encyclopedia
Page semi-protected
"WP:PP" redirects here. You may be looking for Wikipedia:Requests for page protection, Wikipedia:Lists of protected pages, Wikipedia:Perennial proposals or WikiProject Parliamentary Procedure.
"WP:PROTECT" redirects here. You may be looking for Wikipedia:Child protection or Wikipedia:WikiProject Protected areas.
Green check.svg This page documents an English Wikipedia policy, a widely accepted standard that all editors must normally follow. Changes made to it should reflect consensus.
Shortcuts:
WP:PP
WP:PROTECT
Enforcement policies

Administrators
Banning policy
Blocking policy
Protection policy

v
t
e

Gold padlock
Fully protected
Pink padlock
Template-protected
Silver padlock
Semi-protected
Blue padlock
Create protected
Green padlock
Move protected
Purple padlock
Upload protected
White padlock
Pending changes protected (level 1)
Orange padlock
Pending changes protected (level 2)
Red padlock
Permanently protected
Black padlock
Protected by Office

Wikipedia is built around 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. However, in particular circumstances, because of a specifically identified likelihood of damage resulting if editing is left open, some individual pages may need to be subject to technical restrictions (often only temporary) on who is permitted to modify them. The placing of such restrictions on pages is called protection.

Protection can be applied to or removed from pages by Wikipedia's administrators, although any user may request these actions. Protection can be indefinite, or expire after a specified time period.

The most commonly encountered types of protection are full protection, which means that a page can be modified only by administrators, and semi-protection, which means that a page can be modified only by users who are logged in and whose accounts have been confirmed (any account is automatically confirmed if it is at least four days old and has made at least ten edits or posts). Other forms of protection are detailed below. Protected pages are normally marked with a small padlock symbol in the top corner; different color padlocks represent different protection types, as shown in the images at the right. Template:Pp-protected is usually used to display the padlock.

Positioning the mouse pointer over the padlock symbol produces an informational tooltip which says "This article is (semi-)protected." If {{Pp-protected}}'s reason parameter is specified, the tooltip also says why the page is protected. If the expiry parameter is specified, the tooltip says for what duration the page is protected.

This policy explains in detail the protection types and procedures for page protection and unprotection, and the reasons for which protection should and should not be applied.

Contents

1 Overview of types of protection
2 Types of protection
2.1 Full protection
2.1.1 Content disputes
2.1.2 Vandalism
2.1.3 "History only" review
2.1.4 Protected generic image names
2.2 Template protection
2.3 Semi-protection
2.3.1 Guidance for administrators
2.4 Creation protection
2.5 Move protection
2.6 Upload protection
2.7 Pending changes protection
2.7.1 When to apply pending changes protection
2.8 Permanent protection
2.9 Office actions
2.10 Cascading protection
2.11 Comparison table
3 Protection by namespace
3.1 Talk pages
3.1.1 User talk pages
3.1.1.1 Blocked users
3.2 User pages
3.2.1 Deceased users
3.3 Protection of templates
3.4 Sandboxes
4 Available templates
5 See also
6 Notes

Overview of types of protection

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

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 that are not confirmed.
Creation protection prevents a page (normally a previously deleted one) from being recreated (also known as "salting").
Move protection protects the page solely from renaming/moving.
Upload protection prevents new versions of a file from being uploaded except by administrators, but it does not prevent editing the file's description page.
Pending-changes protection means edits by unregistered and new contributors are not visible to readers who are not logged in, until the edits are approved by a reviewer or administrator.

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 by an administrator if they are uncontroversial or if there is consensus for them.

Except in the case of office actions (see below) or pages in the MediaWiki namespace (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.
Types of protection

Full protection
Gold padlock
Policy shortcuts:

WP:FPP
WP:FULL
WP:FULL-PRO
WP:GOLDLOCK

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

Content disputes

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.

Policy shortcut:

WP:PREFER

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.
Vandalism
Policy shortcut:

WP:NO-PREEMPT

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.
"History only" review

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.
Protected generic image names

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.

Template protection
Pink padlock
Policy shortcuts:

WP:TEMP-P
WP:TEMP-PRO
WP:TPROT
WP:PINKLOCK

Main page: Wikipedia:Template editor

A template-protected page can be edited only by administrators or users in the Template editors group. This protection level may only be used on high-risk templates and modules, and possibly in rarer cases where pages in other namespaces become transcluded to a very high degree.

This is a new protection level[1] that replaces full protection on pages that are merely protected due to high transclusion rates, rather than content disputes. It should only 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 template editor user right exists – the existence of the right should not result in more templates becoming uneditable for the general editor population.

Semi-protection
Silver padlock
Policy shortcuts:

WP:S-P
WP:SPP
WP:SEMI
WP:SEMI-PRO
WP:SILVERLOCK

See also: Wikipedia:Rough guide to semi-protection

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 at least ten 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.
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, nor should it be used 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) 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. 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, 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 reblocked with talk page editing disallowed. When required, or when reblocking without talk page editing allowed is unsuccessful, protection should be implemented for only a brief period, and not exceeding the duration of the block.

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.

Creation protection
Blue padlock
Policy shortcuts:

WP:SALT
WP:PDP
WP:BLUELOCK

Administrators can prevent the creation of a page through the protection interface. This is useful for articles that have been deleted but repeatedly recreated. 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 (look for one who was previously involved) or use the deletion review process.

There are two levels of creation protection that can be applied to pages. One version is similar to semi-protection which allows autoconfirmed editors to create the page. The other version is similar to full protection which allows only administrators to create the page.

Move protection
Green padlock
Policy shortcuts:

WP:MOVP
WP:MOVE-PRO
WP:GREENLOCK

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 and articles selected as "Today's featured article" on the main page.

Fully protected pages are also move-protected.

As with full protection, protection because of editwarring 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.

Upload protection
Purple padlock
Policy shortcuts:

WP:UPLOAD-P
WP:PURPLELOCK

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.

Pending changes protection
Further information: Wikipedia:Pending changes
Policy shortcuts:

WP:PCPP
WP:WHITELOCK
WP:ORANGELOCK

White padlock Orange padlock

Pending changes protection is a tool used to suppress vandalism and certain other persistent problems, while allowing all users to continue to submit edits. Pending changes protection can be used as an alternative to semi-protection to allow unregistered and new users to edit pages, while keeping the edits hidden to most readers until they are accepted by a 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 reviewer right.

Pending changes are visible in the page history, where they are marked as pending review. The latest accepted revision is displayed to the general public. Logged-in users see the latest revision of the page, with all changes 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.

Both logged-in users and anonymous users who click the "edit this page" tab may edit the latest version as usual. If there are pending changes awaiting review, there will be a dropdown box next to the article title, pointing to the pending changes. For more details, see Help:Pending changes.

Reviewing of pending changes should be resolved within reasonable time limits. Backlog management should be coordinated at a community level.
When to apply pending changes protection

Pending changes may be used to protect articles against:

persistent vandalism
violations of the biographies of living persons policy
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 only be used in cases of severe long-term disruption.

Only what is known as "Pending changes level 1" should be used, which is labeled "Require review for revisions from new and unregistered users". Pending changes level 2, or "Require review for revisions from everyone except Reviewers", should not be used at this time per WP:PC2012/RfC 1.

Removal of pending changes protection can be requested of any administrator, or at requests for unprotection.

The reviewing process is described in detail at reviewing.

Permanent protection
Red padlock
Policy shortcuts:

WP:PPINDEF
WP:PERM-PRO
WP:REDLOCK

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

Office actions
Black padlock
Policy shortcuts:

WP:WMF-P
WP:WMF-PRO
WP:BLACKLOCK

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
Shortcuts:

WP:CASCADE
WP:CASCADING

"WP:CASCADE" redirects here. You may be also looking for Wikipedia:Cascading style sheets.

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 "Protection of templates" section below for alternatives.

Comparison table

The following table compares the effects of protection on Wikipedia users.
Wikipedia users, page protections, and page edits Unregistered, New Autoconfirmed, Confirmed Template editor Reviewer Administrator Appropriate for
No protection can edit;
changes go live* immediately;
no acceptance required The vast majority of pages
Pending changes
level 1 protection can edit;
changes will go live after being accepted by a reviewer can edit;
changes go live immediately (if no previous pending changes remain to be accepted) can edit;
changes go live immediately;**
can accept pending changes Infrequently edited articles that are experiencing high levels of vandalism or BLP violations from unregistered and new users
Semi-protection cannot edit can edit;
changes go live immediately;
no acceptance required Articles experiencing high levels of vandalism or edit warring from unregistered and new users, and for some highly visible templates and modules
Pending changes
level 2 protection can edit;
changes will go live after being accepted by a reviewer can edit;
changes go live immediately;
can accept pending changes No consensus for use on the English Wikipedia per WP:PC2012/RfC 1
Pending changes level 2 with Semi-protection cannot edit can edit;
changes will go live after being accepted by a reviewer can edit;
changes go live immediately;
can accept pending changes No consensus for use on the English Wikipedia per WP:PC2012/RfC 1
Template protection cannot edit can edit;
changes go live immediately;
no acceptance required cannot edit can edit;
changes go live immediately;
no acceptance required High-risk templates and modules
Full protection cannot edit can edit;
changes go live immediately;
no acceptance required Articles experiencing persistent vandalism or edit warring from (auto)confirmed accounts, and for critically important templates and modules
* "Go live" means the edits will be visible to readers who are not logged in. In all cases, edits are always visible to readers logged into Wikipedia.
** When editing articles with un-reviewed pending changes, Administrators and Reviewers are prompted to review the pending changes before saving their edit.
Protection by namespace
Talk pages

Modifications to a 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 protected}} template on the talk page will draw the attention of administrators for implementing uncontroversial changes.

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

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 pages are semi-protected should have an unprotected user talk subpage linked conspicuously from their main talk page to allow good faith comments from non-autoconfirmed users.

A user's request to have his or her own talk page protected is not a sufficient rationale to protect the page.
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 {{unblock}} template, re-blocking the user without talk page access should be preferred over protection. If the user has been indefinitely blocked from editing the talk page, they should be informed of off-wiki ways to appeal their block, such as the UTRS tool interface or ban appeals subcommittee of 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
Policy shortcuts:

WP:UPROT
WP:UPPROT

User pages and subpages can be protected by simple request from the user; this does not apply to the main user talk page. This is common for retired users and talk page archives.
Deceased users
See also: Wikipedia:Deceased Wikipedians/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: Wikipedia:High-risk templates and Wikipedia:Template documentation

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 template-protected based on the degree of visibility, type of use, content, and other factors.

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 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 template editors and account creators).
Sandboxes
See also: Wikipedia:About the Sandbox

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.
Available templates

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

v
t
e

{{pp-meta}} Full Semi Move
Dispute: {{pp-dispute}} {{pp-move-dispute}}
Vandalism: {{pp-vandalism}} {{pp-move-vandalism}}
High visibility templates and modules: {{pp-template}} N/A
User talk of blocked user: {{pp-usertalk}} N/A
Sockpuppetry: {{pp-sock}} N/A
WP:BLP: {{pp-blp}} N/A
Long-term: N/A {{pp-semi-indef}} {{pp-move-indef}}
Generic (other protection): {{pp-protected}} {{pp-move}}
Scrutiny of the Office: {{pp-office}} {{pp-reset}} N/A
Talk page info: {{permanently protected}} {{temporarily protected}} N/A
Create protection: {{pp-create}} N/A
Pending changes protection level 1: {{pp-pc1}} N/A
Pending changes protection level 2: {{pp-pc2}} N/A

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.
See also

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
Category:Wikipedia protected edit requests
Wikipedia:Protection policy/Padlocks

Notes

Created October 2013 as a result of Wikipedia:Requests for comment/Template editor user right‎

[show]

v
t
e

New admin
Categories:

Wikipedia policies
Wikipedia enforcement policies
Wikipedia New admin
Wikipedia vandalism
Wikipedia page protection

Navigation menu

Create account
Log in

Project page
Talk

Read
View source
View history

Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Wikimedia Shop

Interaction

Help
About Wikipedia
Community portal
Recent changes
Contact page

Tools
Print/export
Languages

Afrikaans
Ænglisc
العربية
Aragonés
অসমীয়া
বাংলা
Català
Cebuano
Čeština
Cymraeg
Dansk
Deutsch
ދިވެހިބަސް
Eesti
Ελληνικά
Español
Esperanto
فارسی
Français
Galego
한국어
Հայերեն
Hrvatski
Ilokano
Bahasa Indonesia
Íslenska
Italiano
עברית
Basa Jawa
ქართული
Latina
Lëtzebuergesch
Lietuvių
Magyar
Македонски
Malti
Bahasa Melayu
Монгол
Nederlands
नेपाली
日本語
Norsk bokmål
ଓଡ଼ିଆ
Oʻzbekcha
ភាសាខ្មែរ
Polski
Português
Română
Русский
Саха тыла
Sardu
සිංහල
Simple English
Slovenčina
Slovenščina
Soomaaliga
Српски / srpski
Basa Sunda
Suomi
Svenska
தமிழ்
తెలుగు
ไทย
Türkçe
Удмурт
Українська
Vèneto
Tiếng Việt
ייִדיש
粵語
中文

Edit links

This page was last modified on 6 May 2014 at 00:41.
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.

Privacy policy
About Wikipedia
Disclaimers
Contact Wikipedia
Developers
Mobile view

Wikimedia Foundation
Powered by MediaWiki


Wikipedia:Protection policy
From Wikipedia, the free encyclopedia
Page semi-protected
"WP:PP" redirects here. You may be looking for Wikipedia:Requests for page protection, Wikipedia:Lists of protected pages, Wikipedia:Perennial proposals or WikiProject Parliamentary Procedure.
"WP:PROTECT" redirects here. You may be looking for Wikipedia:Child protection or Wikipedia:WikiProject Protected areas.
Green check.svg This page documents an English Wikipedia policy, a widely accepted standard that all editors must normally follow. Changes made to it should reflect consensus.
Shortcuts:
WP:PP
WP:PROTECT
Enforcement policies

Administrators
Banning policy
Blocking policy
Protection policy

v
t
e

Gold padlock
Fully protected
Pink padlock
Template-protected
Silver padlock
Semi-protected
Blue padlock
Create protected
Green padlock
Move protected
Purple padlock
Upload protected
White padlock
Pending changes protected (level 1)
Orange padlock
Pending changes protected (level 2)
Red padlock
Permanently protected
Black padlock
Protected by Office

Wikipedia is built around 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. However, in particular circumstances, because of a specifically identified likelihood of damage resulting if editing is left open, some individual pages may need to be subject to technical restrictions (often only temporary) on who is permitted to modify them. The placing of such restrictions on pages is called protection.

Protection can be applied to or removed from pages by Wikipedia's administrators, although any user may request these actions. Protection can be indefinite, or expire after a specified time period.

The most commonly encountered types of protection are full protection, which means that a page can be modified only by administrators, and semi-protection, which means that a page can be modified only by users who are logged in and whose accounts have been confirmed (any account is automatically confirmed if it is at least four days old and has made at least ten edits or posts). Other forms of protection are detailed below. Protected pages are normally marked with a small padlock symbol in the top corner; different color padlocks represent different protection types, as shown in the images at the right. Template:Pp-protected is usually used to display the padlock.

Positioning the mouse pointer over the padlock symbol produces an informational tooltip which says "This article is (semi-)protected." If {{Pp-protected}}'s reason parameter is specified, the tooltip also says why the page is protected. If the expiry parameter is specified, the tooltip says for what duration the page is protected.

This policy explains in detail the protection types and procedures for page protection and unprotection, and the reasons for which protection should and should not be applied.

Contents

1 Overview of types of protection
2 Types of protection
2.1 Full protection
2.1.1 Content disputes
2.1.2 Vandalism
2.1.3 "History only" review
2.1.4 Protected generic image names
2.2 Template protection
2.3 Semi-protection
2.3.1 Guidance for administrators
2.4 Creation protection
2.5 Move protection
2.6 Upload protection
2.7 Pending changes protection
2.7.1 When to apply pending changes protection
2.8 Permanent protection
2.9 Office actions
2.10 Cascading protection
2.11 Comparison table
3 Protection by namespace
3.1 Talk pages
3.1.1 User talk pages
3.1.1.1 Blocked users
3.2 User pages
3.2.1 Deceased users
3.3 Protection of templates
3.4 Sandboxes
4 Available templates
5 See also
6 Notes

Overview of types of protection

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

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 that are not confirmed.
Creation protection prevents a page (normally a previously deleted one) from being recreated (also known as "salting").
Move protection protects the page solely from renaming/moving.
Upload protection prevents new versions of a file from being uploaded except by administrators, but it does not prevent editing the file's description page.
Pending-changes protection means edits by unregistered and new contributors are not visible to readers who are not logged in, until the edits are approved by a reviewer or administrator.

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 by an administrator if they are uncontroversial or if there is consensus for them.

Except in the case of office actions (see below) or pages in the MediaWiki namespace (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.
Types of protection

Full protection
Gold padlock
Policy shortcuts:

WP:FPP
WP:FULL
WP:FULL-PRO
WP:GOLDLOCK

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

Content disputes

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.

Policy shortcut:

WP:PREFER

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.
Vandalism
Policy shortcut:

WP:NO-PREEMPT

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.
"History only" review

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.
Protected generic image names

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.

Template protection
Pink padlock
Policy shortcuts:

WP:TEMP-P
WP:TEMP-PRO
WP:TPROT
WP:PINKLOCK

Main page: Wikipedia:Template editor

A template-protected page can be edited only by administrators or users in the Template editors group. This protection level may only be used on high-risk templates and modules, and possibly in rarer cases where pages in other namespaces become transcluded to a very high degree.

This is a new protection level[1] that replaces full protection on pages that are merely protected due to high transclusion rates, rather than content disputes. It should only 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 template editor user right exists – the existence of the right should not result in more templates becoming uneditable for the general editor population.

Semi-protection
Silver padlock
Policy shortcuts:

WP:S-P
WP:SPP
WP:SEMI
WP:SEMI-PRO
WP:SILVERLOCK

See also: Wikipedia:Rough guide to semi-protection

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 at least ten 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.
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, nor should it be used 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) 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. 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, 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 reblocked with talk page editing disallowed. When required, or when reblocking without talk page editing allowed is unsuccessful, protection should be implemented for only a brief period, and not exceeding the duration of the block.

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.

Creation protection
Blue padlock
Policy shortcuts:

WP:SALT
WP:PDP
WP:BLUELOCK

Administrators can prevent the creation of a page through the protection interface. This is useful for articles that have been deleted but repeatedly recreated. 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 (look for one who was previously involved) or use the deletion review process.

There are two levels of creation protection that can be applied to pages. One version is similar to semi-protection which allows autoconfirmed editors to create the page. The other version is similar to full protection which allows only administrators to create the page.

Move protection
Green padlock
Policy shortcuts:

WP:MOVP
WP:MOVE-PRO
WP:GREENLOCK

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 and articles selected as "Today's featured article" on the main page.

Fully protected pages are also move-protected.

As with full protection, protection because of editwarring 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.

Upload protection
Purple padlock
Policy shortcuts:

WP:UPLOAD-P
WP:PURPLELOCK

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.

Pending changes protection
Further information: Wikipedia:Pending changes
Policy shortcuts:

WP:PCPP
WP:WHITELOCK
WP:ORANGELOCK

White padlock Orange padlock

Pending changes protection is a tool used to suppress vandalism and certain other persistent problems, while allowing all users to continue to submit edits. Pending changes protection can be used as an alternative to semi-protection to allow unregistered and new users to edit pages, while keeping the edits hidden to most readers until they are accepted by a 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 reviewer right.

Pending changes are visible in the page history, where they are marked as pending review. The latest accepted revision is displayed to the general public. Logged-in users see the latest revision of the page, with all changes 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.

Both logged-in users and anonymous users who click the "edit this page" tab may edit the latest version as usual. If there are pending changes awaiting review, there will be a dropdown box next to the article title, pointing to the pending changes. For more details, see Help:Pending changes.

Reviewing of pending changes should be resolved within reasonable time limits. Backlog management should be coordinated at a community level.
When to apply pending changes protection

Pending changes may be used to protect articles against:

persistent vandalism
violations of the biographies of living persons policy
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 only be used in cases of severe long-term disruption.

Only what is known as "Pending changes level 1" should be used, which is labeled "Require review for revisions from new and unregistered users". Pending changes level 2, or "Require review for revisions from everyone except Reviewers", should not be used at this time per WP:PC2012/RfC 1.

Removal of pending changes protection can be requested of any administrator, or at requests for unprotection.

The reviewing process is described in detail at reviewing.

Permanent protection
Red padlock
Policy shortcuts:

WP:PPINDEF
WP:PERM-PRO
WP:REDLOCK

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

Office actions
Black padlock
Policy shortcuts:

WP:WMF-P
WP:WMF-PRO
WP:BLACKLOCK

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
Shortcuts:

WP:CASCADE
WP:CASCADING

"WP:CASCADE" redirects here. You may be also looking for Wikipedia:Cascading style sheets.

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 "Protection of templates" section below for alternatives.

Comparison table

The following table compares the effects of protection on Wikipedia users.
Wikipedia users, page protections, and page edits Unregistered, New Autoconfirmed, Confirmed Template editor Reviewer Administrator Appropriate for
No protection can edit;
changes go live* immediately;
no acceptance required The vast majority of pages
Pending changes
level 1 protection can edit;
changes will go live after being accepted by a reviewer can edit;
changes go live immediately (if no previous pending changes remain to be accepted) can edit;
changes go live immediately;**
can accept pending changes Infrequently edited articles that are experiencing high levels of vandalism or BLP violations from unregistered and new users
Semi-protection cannot edit can edit;
changes go live immediately;
no acceptance required Articles experiencing high levels of vandalism or edit warring from unregistered and new users, and for some highly visible templates and modules
Pending changes
level 2 protection can edit;
changes will go live after being accepted by a reviewer can edit;
changes go live immediately;
can accept pending changes No consensus for use on the English Wikipedia per WP:PC2012/RfC 1
Pending changes level 2 with Semi-protection cannot edit can edit;
changes will go live after being accepted by a reviewer can edit;
changes go live immediately;
can accept pending changes No consensus for use on the English Wikipedia per WP:PC2012/RfC 1
Template protection cannot edit can edit;
changes go live immediately;
no acceptance required cannot edit can edit;
changes go live immediately;
no acceptance required High-risk templates and modules
Full protection cannot edit can edit;
changes go live immediately;
no acceptance required Articles experiencing persistent vandalism or edit warring from (auto)confirmed accounts, and for critically important templates and modules
* "Go live" means the edits will be visible to readers who are not logged in. In all cases, edits are always visible to readers logged into Wikipedia.
** When editing articles with un-reviewed pending changes, Administrators and Reviewers are prompted to review the pending changes before saving their edit.
Protection by namespace
Talk pages

Modifications to a 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 protected}} template on the talk page will draw the attention of administrators for implementing uncontroversial changes.

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

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 pages are semi-protected should have an unprotected user talk subpage linked conspicuously from their main talk page to allow good faith comments from non-autoconfirmed users.

A user's request to have his or her own talk page protected is not a sufficient rationale to protect the page.
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 {{unblock}} template, re-blocking the user without talk page access should be preferred over protection. If the user has been indefinitely blocked from editing the talk page, they should be informed of off-wiki ways to appeal their block, such as the UTRS tool interface or ban appeals subcommittee of 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
Policy shortcuts:

WP:UPROT
WP:UPPROT

User pages and subpages can be protected by simple request from the user; this does not apply to the main user talk page. This is common for retired users and talk page archives.
Deceased users
See also: Wikipedia:Deceased Wikipedians/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: Wikipedia:High-risk templates and Wikipedia:Template documentation

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 template-protected based on the degree of visibility, type of use, content, and other factors.

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 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 template editors and account creators).
Sandboxes
See also: Wikipedia:About the Sandbox

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.
Available templates

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

v
t
e

{{pp-meta}} Full Semi Move
Dispute: {{pp-dispute}} {{pp-move-dispute}}
Vandalism: {{pp-vandalism}} {{pp-move-vandalism}}
High visibility templates and modules: {{pp-template}} N/A
User talk of blocked user: {{pp-usertalk}} N/A
Sockpuppetry: {{pp-sock}} N/A
WP:BLP: {{pp-blp}} N/A
Long-term: N/A {{pp-semi-indef}} {{pp-move-indef}}
Generic (other protection): {{pp-protected}} {{pp-move}}
Scrutiny of the Office: {{pp-office}} {{pp-reset}} N/A
Talk page info: {{permanently protected}} {{temporarily protected}} N/A
Create protection: {{pp-create}} N/A
Pending changes protection level 1: {{pp-pc1}} N/A
Pending changes protection level 2: {{pp-pc2}} N/A

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.
See also

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
Category:Wikipedia protected edit requests
Wikipedia:Protection policy/Padlocks

Notes

Created October 2013 as a result of Wikipedia:Requests for comment/Template editor user right‎

[show]

v
t
e

New admin
Categories:

Wikipedia policies
Wikipedia enforcement policies
Wikipedia New admin
Wikipedia vandalism
Wikipedia page protection

Navigation menu

Create account
Log in

Project page
Talk

Read
View source
View history

Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Wikimedia Shop

Interaction

Help
About Wikipedia
Community portal
Recent changes
Contact page

Tools
Print/export
Languages

Afrikaans
Ænglisc
العربية
Aragonés
অসমীয়া
বাংলা
Català
Cebuano
Čeština
Cymraeg
Dansk
Deutsch
ދިވެހިބަސް
Eesti
Ελληνικά
Español
Esperanto
فارسی
Français
Galego
한국어
Հայերեն
Hrvatski
Ilokano
Bahasa Indonesia
Íslenska
Italiano
עברית
Basa Jawa
ქართული
Latina
Lëtzebuergesch
Lietuvių
Magyar
Македонски
Malti
Bahasa Melayu
Монгол
Nederlands
नेपाली
日本語
Norsk bokmål
ଓଡ଼ିଆ
Oʻzbekcha
ភាសាខ្មែរ
Polski
Português
Română
Русский
Саха тыла
Sardu
සිංහල
Simple English
Slovenčina
Slovenščina
Soomaaliga
Српски / srpski
Basa Sunda
Suomi
Svenska
தமிழ்
తెలుగు
ไทย
Türkçe
Удмурт
Українська
Vèneto
Tiếng Việt
ייִדיש
粵語
中文

Edit links

This page was last modified on 6 May 2014 at 00:41.
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.

Privacy policy
About Wikipedia
Disclaimers
Contact Wikipedia
Developers
Mobile view

Wikimedia Foundation
Powered by MediaWiki


Wikipedia:Protection policy
From Wikipedia, the free encyclopedia
Page semi-protected
"WP:PP" redirects here. You may be looking for Wikipedia:Requests for page protection, Wikipedia:Lists of protected pages, Wikipedia:Perennial proposals or WikiProject Parliamentary Procedure.
"WP:PROTECT" redirects here. You may be looking for Wikipedia:Child protection or Wikipedia:WikiProject Protected areas.
Green check.svg This page documents an English Wikipedia policy, a widely accepted standard that all editors must normally follow. Changes made to it should reflect consensus.
Shortcuts:
WP:PP
WP:PROTECT
Enforcement policies

Administrators
Banning policy
Blocking policy
Protection policy

v
t
e

Gold padlock
Fully protected
Pink padlock
Template-protected
Silver padlock
Semi-protected
Blue padlock
Create protected
Green padlock
Move protected
Purple padlock
Upload protected
White padlock
Pending changes protected (level 1)
Orange padlock
Pending changes protected (level 2)
Red padlock
Permanently protected
Black padlock
Protected by Office

Wikipedia is built around 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. However, in particular circumstances, because of a specifically identified likelihood of damage resulting if editing is left open, some individual pages may need to be subject to technical restrictions (often only temporary) on who is permitted to modify them. The placing of such restrictions on pages is called protection.

Protection can be applied to or removed from pages by Wikipedia's administrators, although any user may request these actions. Protection can be indefinite, or expire after a specified time period.

The most commonly encountered types of protection are full protection, which means that a page can be modified only by administrators, and semi-protection, which means that a page can be modified only by users who are logged in and whose accounts have been confirmed (any account is automatically confirmed if it is at least four days old and has made at least ten edits or posts). Other forms of protection are detailed below. Protected pages are normally marked with a small padlock symbol in the top corner; different color padlocks represent different protection types, as shown in the images at the right. Template:Pp-protected is usually used to display the padlock.

Positioning the mouse pointer over the padlock symbol produces an informational tooltip which says "This article is (semi-)protected." If {{Pp-protected}}'s reason parameter is specified, the tooltip also says why the page is protected. If the expiry parameter is specified, the tooltip says for what duration the page is protected.

This policy explains in detail the protection types and procedures for page protection and unprotection, and the reasons for which protection should and should not be applied.

Contents

1 Overview of types of protection
2 Types of protection
2.1 Full protection
2.1.1 Content disputes
2.1.2 Vandalism
2.1.3 "History only" review
2.1.4 Protected generic image names
2.2 Template protection
2.3 Semi-protection
2.3.1 Guidance for administrators
2.4 Creation protection
2.5 Move protection
2.6 Upload protection
2.7 Pending changes protection
2.7.1 When to apply pending changes protection
2.8 Permanent protection
2.9 Office actions
2.10 Cascading protection
2.11 Comparison table
3 Protection by namespace
3.1 Talk pages
3.1.1 User talk pages
3.1.1.1 Blocked users
3.2 User pages
3.2.1 Deceased users
3.3 Protection of templates
3.4 Sandboxes
4 Available templates
5 See also
6 Notes

Overview of types of protection

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

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 that are not confirmed.
Creation protection prevents a page (normally a previously deleted one) from being recreated (also known as "salting").
Move protection protects the page solely from renaming/moving.
Upload protection prevents new versions of a file from being uploaded except by administrators, but it does not prevent editing the file's description page.
Pending-changes protection means edits by unregistered and new contributors are not visible to readers who are not logged in, until the edits are approved by a reviewer or administrator.

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 by an administrator if they are uncontroversial or if there is consensus for them.

Except in the case of office actions (see below) or pages in the MediaWiki namespace (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.
Types of protection

Full protection
Gold padlock
Policy shortcuts:

WP:FPP
WP:FULL
WP:FULL-PRO
WP:GOLDLOCK

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

Content disputes

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.

Policy shortcut:

WP:PREFER

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.
Vandalism
Policy shortcut:

WP:NO-PREEMPT

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.
"History only" review

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.
Protected generic image names

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.

Template protection
Pink padlock
Policy shortcuts:

WP:TEMP-P
WP:TEMP-PRO
WP:TPROT
WP:PINKLOCK

Main page: Wikipedia:Template editor

A template-protected page can be edited only by administrators or users in the Template editors group. This protection level may only be used on high-risk templates and modules, and possibly in rarer cases where pages in other namespaces become transcluded to a very high degree.

This is a new protection level[1] that replaces full protection on pages that are merely protected due to high transclusion rates, rather than content disputes. It should only 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 template editor user right exists – the existence of the right should not result in more templates becoming uneditable for the general editor population.

Semi-protection
Silver padlock
Policy shortcuts:

WP:S-P
WP:SPP
WP:SEMI
WP:SEMI-PRO
WP:SILVERLOCK

See also: Wikipedia:Rough guide to semi-protection

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 at least ten 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.
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, nor should it be used 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) 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. 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, 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 reblocked with talk page editing disallowed. When required, or when reblocking without talk page editing allowed is unsuccessful, protection should be implemented for only a brief period, and not exceeding the duration of the block.

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.

Creation protection
Blue padlock
Policy shortcuts:

WP:SALT
WP:PDP
WP:BLUELOCK

Administrators can prevent the creation of a page through the protection interface. This is useful for articles that have been deleted but repeatedly recreated. 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 (look for one who was previously involved) or use the deletion review process.

There are two levels of creation protection that can be applied to pages. One version is similar to semi-protection which allows autoconfirmed editors to create the page. The other version is similar to full protection which allows only administrators to create the page.

Move protection
Green padlock
Policy shortcuts:

WP:MOVP
WP:MOVE-PRO
WP:GREENLOCK

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 and articles selected as "Today's featured article" on the main page.

Fully protected pages are also move-protected.

As with full protection, protection because of editwarring 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.

Upload protection
Purple padlock
Policy shortcuts:

WP:UPLOAD-P
WP:PURPLELOCK

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.

Pending changes protection
Further information: Wikipedia:Pending changes
Policy shortcuts:

WP:PCPP
WP:WHITELOCK
WP:ORANGELOCK

White padlock Orange padlock

Pending changes protection is a tool used to suppress vandalism and certain other persistent problems, while allowing all users to continue to submit edits. Pending changes protection can be used as an alternative to semi-protection to allow unregistered and new users to edit pages, while keeping the edits hidden to most readers until they are accepted by a 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 reviewer right.

Pending changes are visible in the page history, where they are marked as pending review. The latest accepted revision is displayed to the general public. Logged-in users see the latest revision of the page, with all changes 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.

Both logged-in users and anonymous users who click the "edit this page" tab may edit the latest version as usual. If there are pending changes awaiting review, there will be a dropdown box next to the article title, pointing to the pending changes. For more details, see Help:Pending changes.

Reviewing of pending changes should be resolved within reasonable time limits. Backlog management should be coordinated at a community level.
When to apply pending changes protection

Pending changes may be used to protect articles against:

persistent vandalism
violations of the biographies of living persons policy
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 only be used in cases of severe long-term disruption.

Only what is known as "Pending changes level 1" should be used, which is labeled "Require review for revisions from new and unregistered users". Pending changes level 2, or "Require review for revisions from everyone except Reviewers", should not be used at this time per WP:PC2012/RfC 1.

Removal of pending changes protection can be requested of any administrator, or at requests for unprotection.

The reviewing process is described in detail at reviewing.

Permanent protection
Red padlock
Policy shortcuts:

WP:PPINDEF
WP:PERM-PRO
WP:REDLOCK

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

Office actions
Black padlock
Policy shortcuts:

WP:WMF-P
WP:WMF-PRO
WP:BLACKLOCK

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
Shortcuts:

WP:CASCADE
WP:CASCADING

"WP:CASCADE" redirects here. You may be also looking for Wikipedia:Cascading style sheets.

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 "Protection of templates" section below for alternatives.

Comparison table

The following table compares the effects of protection on Wikipedia users.
Wikipedia users, page protections, and page edits Unregistered, New Autoconfirmed, Confirmed Template editor Reviewer Administrator Appropriate for
No protection can edit;
changes go live* immediately;
no acceptance required The vast majority of pages
Pending changes
level 1 protection can edit;
changes will go live after being accepted by a reviewer can edit;
changes go live immediately (if no previous pending changes remain to be accepted) can edit;
changes go live immediately;**
can accept pending changes Infrequently edited articles that are experiencing high levels of vandalism or BLP violations from unregistered and new users
Semi-protection cannot edit can edit;
changes go live immediately;
no acceptance required Articles experiencing high levels of vandalism or edit warring from unregistered and new users, and for some highly visible templates and modules
Pending changes
level 2 protection can edit;
changes will go live after being accepted by a reviewer can edit;
changes go live immediately;
can accept pending changes No consensus for use on the English Wikipedia per WP:PC2012/RfC 1
Pending changes level 2 with Semi-protection cannot edit can edit;
changes will go live after being accepted by a reviewer can edit;
changes go live immediately;
can accept pending changes No consensus for use on the English Wikipedia per WP:PC2012/RfC 1
Template protection cannot edit can edit;
changes go live immediately;
no acceptance required cannot edit can edit;
changes go live immediately;
no acceptance required High-risk templates and modules
Full protection cannot edit can edit;
changes go live immediately;
no acceptance required Articles experiencing persistent vandalism or edit warring from (auto)confirmed accounts, and for critically important templates and modules
* "Go live" means the edits will be visible to readers who are not logged in. In all cases, edits are always visible to readers logged into Wikipedia.
** When editing articles with un-reviewed pending changes, Administrators and Reviewers are prompted to review the pending changes before saving their edit.
Protection by namespace
Talk pages

Modifications to a 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 protected}} template on the talk page will draw the attention of administrators for implementing uncontroversial changes.

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

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 pages are semi-protected should have an unprotected user talk subpage linked conspicuously from their main talk page to allow good faith comments from non-autoconfirmed users.

A user's request to have his or her own talk page protected is not a sufficient rationale to protect the page.
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 {{unblock}} template, re-blocking the user without talk page access should be preferred over protection. If the user has been indefinitely blocked from editing the talk page, they should be informed of off-wiki ways to appeal their block, such as the UTRS tool interface or ban appeals subcommittee of 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
Policy shortcuts:

WP:UPROT
WP:UPPROT

User pages and subpages can be protected by simple request from the user; this does not apply to the main user talk page. This is common for retired users and talk page archives.
Deceased users
See also: Wikipedia:Deceased Wikipedians/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: Wikipedia:High-risk templates and Wikipedia:Template documentation

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 template-protected based on the degree of visibility, type of use, content, and other factors.

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 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 template editors and account creators).
Sandboxes
See also: Wikipedia:About the Sandbox

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.
Available templates

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

v
t
e

{{pp-meta}} Full Semi Move
Dispute: {{pp-dispute}} {{pp-move-dispute}}
Vandalism: {{pp-vandalism}} {{pp-move-vandalism}}
High visibility templates and modules: {{pp-template}} N/A
User talk of blocked user: {{pp-usertalk}} N/A
Sockpuppetry: {{pp-sock}} N/A
WP:BLP: {{pp-blp}} N/A
Long-term: N/A {{pp-semi-indef}} {{pp-move-indef}}
Generic (other protection): {{pp-protected}} {{pp-move}}
Scrutiny of the Office: {{pp-office}} {{pp-reset}} N/A
Talk page info: {{permanently protected}} {{temporarily protected}} N/A
Create protection: {{pp-create}} N/A
Pending changes protection level 1: {{pp-pc1}} N/A
Pending changes protection level 2: {{pp-pc2}} N/A

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.
See also

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
Category:Wikipedia protected edit requests
Wikipedia:Protection policy/Padlocks

Notes

Created October 2013 as a result of Wikipedia:Requests for comment/Template editor user right‎

[show]

v
t
e

New admin
Categories:

Wikipedia policies
Wikipedia enforcement policies
Wikipedia New admin
Wikipedia vandalism
Wikipedia page protection

Navigation menu

Create account
Log in

Project page
Talk

Read
View source
View history

Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Wikimedia Shop

Interaction

Help
About Wikipedia
Community portal
Recent changes
Contact page

Tools
Print/export
Languages

Afrikaans
Ænglisc
العربية
Aragonés
অসমীয়া
বাংলা
Català
Cebuano
Čeština
Cymraeg
Dansk
Deutsch
ދިވެހިބަސް
Eesti
Ελληνικά
Español
Esperanto
فارسی
Français
Galego
한국어
Հայերեն
Hrvatski
Ilokano
Bahasa Indonesia
Íslenska
Italiano
עברית
Basa Jawa
ქართული
Latina
Lëtzebuergesch
Lietuvių
Magyar
Македонски
Malti
Bahasa Melayu
Монгол
Nederlands
नेपाली
日本語
Norsk bokmål
ଓଡ଼ିଆ
Oʻzbekcha
ភាសាខ្មែរ
Polski
Português
Română
Русский
Саха тыла
Sardu
සිංහල
Simple English
Slovenčina
Slovenščina
Soomaaliga
Српски / srpski
Basa Sunda
Suomi
Svenska
தமிழ்
తెలుగు
ไทย
Türkçe
Удмурт
Українська
Vèneto
Tiếng Việt
ייִדיש
粵語
中文

Edit links

This page was last modified on 6 May 2014 at 00:41.
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.

Privacy policy
About Wikipedia
Disclaimers
Contact Wikipedia
Developers
Mobile view

Wikimedia Foundation
Powered by MediaWiki


Wikipedia:Protection policy
From Wikipedia, the free encyclopedia
Page semi-protected
"WP:PP" redirects here. You may be looking for Wikipedia:Requests for page protection, Wikipedia:Lists of protected pages, Wikipedia:Perennial proposals or WikiProject Parliamentary Procedure.
"WP:PROTECT" redirects here. You may be looking for Wikipedia:Child protection or Wikipedia:WikiProject Protected areas.
Green check.svg This page documents an English Wikipedia policy, a widely accepted standard that all editors must normally follow. Changes made to it should reflect consensus.
Shortcuts:
WP:PP
WP:PROTECT
Enforcement policies

Administrators
Banning policy
Blocking policy
Protection policy

v
t
e

Gold padlock
Fully protected
Pink padlock
Template-protected
Silver padlock
Semi-protected
Blue padlock
Create protected
Green padlock
Move protected
Purple padlock
Upload protected
White padlock
Pending changes protected (level 1)
Orange padlock
Pending changes protected (level 2)
Red padlock
Permanently protected
Black padlock
Protected by Office

Wikipedia is built around 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. However, in particular circumstances, because of a specifically identified likelihood of damage resulting if editing is left open, some individual pages may need to be subject to technical restrictions (often only temporary) on who is permitted to modify them. The placing of such restrictions on pages is called protection.

Protection can be applied to or removed from pages by Wikipedia's administrators, although any user may request these actions. Protection can be indefinite, or expire after a specified time period.

The most commonly encountered types of protection are full protection, which means that a page can be modified only by administrators, and semi-protection, which means that a page can be modified only by users who are logged in and whose accounts have been confirmed (any account is automatically confirmed if it is at least four days old and has made at least ten edits or posts). Other forms of protection are detailed below. Protected pages are normally marked with a small padlock symbol in the top corner; different color padlocks represent different protection types, as shown in the images at the right. Template:Pp-protected is usually used to display the padlock.

Positioning the mouse pointer over the padlock symbol produces an informational tooltip which says "This article is (semi-)protected." If {{Pp-protected}}'s reason parameter is specified, the tooltip also says why the page is protected. If the expiry parameter is specified, the tooltip says for what duration the page is protected.

This policy explains in detail the protection types and procedures for page protection and unprotection, and the reasons for which protection should and should not be applied.

Contents

1 Overview of types of protection
2 Types of protection
2.1 Full protection
2.1.1 Content disputes
2.1.2 Vandalism
2.1.3 "History only" review
2.1.4 Protected generic image names
2.2 Template protection
2.3 Semi-protection
2.3.1 Guidance for administrators
2.4 Creation protection
2.5 Move protection
2.6 Upload protection
2.7 Pending changes protection
2.7.1 When to apply pending changes protection
2.8 Permanent protection
2.9 Office actions
2.10 Cascading protection
2.11 Comparison table
3 Protection by namespace
3.1 Talk pages
3.1.1 User talk pages
3.1.1.1 Blocked users
3.2 User pages
3.2.1 Deceased users
3.3 Protection of templates
3.4 Sandboxes
4 Available templates
5 See also
6 Notes

Overview of types of protection

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

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 that are not confirmed.
Creation protection prevents a page (normally a previously deleted one) from being recreated (also known as "salting").
Move protection protects the page solely from renaming/moving.
Upload protection prevents new versions of a file from being uploaded except by administrators, but it does not prevent editing the file's description page.
Pending-changes protection means edits by unregistered and new contributors are not visible to readers who are not logged in, until the edits are approved by a reviewer or administrator.

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 by an administrator if they are uncontroversial or if there is consensus for them.

Except in the case of office actions (see below) or pages in the MediaWiki namespace (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.
Types of protection

Full protection
Gold padlock
Policy shortcuts:

WP:FPP
WP:FULL
WP:FULL-PRO
WP:GOLDLOCK

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

Content disputes

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.

Policy shortcut:

WP:PREFER

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.
Vandalism
Policy shortcut:

WP:NO-PREEMPT

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.
"History only" review

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.
Protected generic image names

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.

Template protection
Pink padlock
Policy shortcuts:

WP:TEMP-P
WP:TEMP-PRO
WP:TPROT
WP:PINKLOCK

Main page: Wikipedia:Template editor

A template-protected page can be edited only by administrators or users in the Template editors group. This protection level may only be used on high-risk templates and modules, and possibly in rarer cases where pages in other namespaces become transcluded to a very high degree.

This is a new protection level[1] that replaces full protection on pages that are merely protected due to high transclusion rates, rather than content disputes. It should only 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 template editor user right exists – the existence of the right should not result in more templates becoming uneditable for the general editor population.

Semi-protection
Silver padlock
Policy shortcuts:

WP:S-P
WP:SPP
WP:SEMI
WP:SEMI-PRO
WP:SILVERLOCK

See also: Wikipedia:Rough guide to semi-protection

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 at least ten 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.
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, nor should it be used 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) 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. 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, 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 reblocked with talk page editing disallowed. When required, or when reblocking without talk page editing allowed is unsuccessful, protection should be implemented for only a brief period, and not exceeding the duration of the block.

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.

Creation protection
Blue padlock
Policy shortcuts:

WP:SALT
WP:PDP
WP:BLUELOCK

Administrators can prevent the creation of a page through the protection interface. This is useful for articles that have been deleted but repeatedly recreated. 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 (look for one who was previously involved) or use the deletion review process.

There are two levels of creation protection that can be applied to pages. One version is similar to semi-protection which allows autoconfirmed editors to create the page. The other version is similar to full protection which allows only administrators to create the page.

Move protection
Green padlock
Policy shortcuts:

WP:MOVP
WP:MOVE-PRO
WP:GREENLOCK

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 and articles selected as "Today's featured article" on the main page.

Fully protected pages are also move-protected.

As with full protection, protection because of editwarring 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.

Upload protection
Purple padlock
Policy shortcuts:

WP:UPLOAD-P
WP:PURPLELOCK

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.

Pending changes protection
Further information: Wikipedia:Pending changes
Policy shortcuts:

WP:PCPP
WP:WHITELOCK
WP:ORANGELOCK

White padlock Orange padlock

Pending changes protection is a tool used to suppress vandalism and certain other persistent problems, while allowing all users to continue to submit edits. Pending changes protection can be used as an alternative to semi-protection to allow unregistered and new users to edit pages, while keeping the edits hidden to most readers until they are accepted by a 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 reviewer right.

Pending changes are visible in the page history, where they are marked as pending review. The latest accepted revision is displayed to the general public. Logged-in users see the latest revision of the page, with all changes 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.

Both logged-in users and anonymous users who click the "edit this page" tab may edit the latest version as usual. If there are pending changes awaiting review, there will be a dropdown box next to the article title, pointing to the pending changes. For more details, see Help:Pending changes.

Reviewing of pending changes should be resolved within reasonable time limits. Backlog management should be coordinated at a community level.
When to apply pending changes protection

Pending changes may be used to protect articles against:

persistent vandalism
violations of the biographies of living persons policy
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 only be used in cases of severe long-term disruption.

Only what is known as "Pending changes level 1" should be used, which is labeled "Require review for revisions from new and unregistered users". Pending changes level 2, or "Require review for revisions from everyone except Reviewers", should not be used at this time per WP:PC2012/RfC 1.

Removal of pending changes protection can be requested of any administrator, or at requests for unprotection.

The reviewing process is described in detail at reviewing.

Permanent protection
Red padlock
Policy shortcuts:

WP:PPINDEF
WP:PERM-PRO
WP:REDLOCK

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

Office actions
Black padlock
Policy shortcuts:

WP:WMF-P
WP:WMF-PRO
WP:BLACKLOCK

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
Shortcuts:

WP:CASCADE
WP:CASCADING

"WP:CASCADE" redirects here. You may be also looking for Wikipedia:Cascading style sheets.

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 "Protection of templates" section below for alternatives.

Comparison table

The following table compares the effects of protection on Wikipedia users.
Wikipedia users, page protections, and page edits Unregistered, New Autoconfirmed, Confirmed Template editor Reviewer Administrator Appropriate for
No protection can edit;
changes go live* immediately;
no acceptance required The vast majority of pages
Pending changes
level 1 protection can edit;
changes will go live after being accepted by a reviewer can edit;
changes go live immediately (if no previous pending changes remain to be accepted) can edit;
changes go live immediately;**
can accept pending changes Infrequently edited articles that are experiencing high levels of vandalism or BLP violations from unregistered and new users
Semi-protection cannot edit can edit;
changes go live immediately;
no acceptance required Articles experiencing high levels of vandalism or edit warring from unregistered and new users, and for some highly visible templates and modules
Pending changes
level 2 protection can edit;
changes will go live after being accepted by a reviewer can edit;
changes go live immediately;
can accept pending changes No consensus for use on the English Wikipedia per WP:PC2012/RfC 1
Pending changes level 2 with Semi-protection cannot edit can edit;
changes will go live after being accepted by a reviewer can edit;
changes go live immediately;
can accept pending changes No consensus for use on the English Wikipedia per WP:PC2012/RfC 1
Template protection cannot edit can edit;
changes go live immediately;
no acceptance required cannot edit can edit;
changes go live immediately;
no acceptance required High-risk templates and modules
Full protection cannot edit can edit;
changes go live immediately;
no acceptance required Articles experiencing persistent vandalism or edit warring from (auto)confirmed accounts, and for critically important templates and modules
* "Go live" means the edits will be visible to readers who are not logged in. In all cases, edits are always visible to readers logged into Wikipedia.
** When editing articles with un-reviewed pending changes, Administrators and Reviewers are prompted to review the pending changes before saving their edit.
Protection by namespace
Talk pages

Modifications to a 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 protected}} template on the talk page will draw the attention of administrators for implementing uncontroversial changes.

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

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 pages are semi-protected should have an unprotected user talk subpage linked conspicuously from their main talk page to allow good faith comments from non-autoconfirmed users.

A user's request to have his or her own talk page protected is not a sufficient rationale to protect the page.
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 {{unblock}} template, re-blocking the user without talk page access should be preferred over protection. If the user has been indefinitely blocked from editing the talk page, they should be informed of off-wiki ways to appeal their block, such as the UTRS tool interface or ban appeals subcommittee of 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
Policy shortcuts:

WP:UPROT
WP:UPPROT

User pages and subpages can be protected by simple request from the user; this does not apply to the main user talk page. This is common for retired users and talk page archives.
Deceased users
See also: Wikipedia:Deceased Wikipedians/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: Wikipedia:High-risk templates and Wikipedia:Template documentation

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 template-protected based on the degree of visibility, type of use, content, and other factors.

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 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 template editors and account creators).
Sandboxes
See also: Wikipedia:About the Sandbox

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.
Available templates

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

v
t
e

{{pp-meta}} Full Semi Move
Dispute: {{pp-dispute}} {{pp-move-dispute}}
Vandalism: {{pp-vandalism}} {{pp-move-vandalism}}
High visibility templates and modules: {{pp-template}} N/A
User talk of blocked user: {{pp-usertalk}} N/A
Sockpuppetry: {{pp-sock}} N/A
WP:BLP: {{pp-blp}} N/A
Long-term: N/A {{pp-semi-indef}} {{pp-move-indef}}
Generic (other protection): {{pp-protected}} {{pp-move}}
Scrutiny of the Office: {{pp-office}} {{pp-reset}} N/A
Talk page info: {{permanently protected}} {{temporarily protected}} N/A
Create protection: {{pp-create}} N/A
Pending changes protection level 1: {{pp-pc1}} N/A
Pending changes protection level 2: {{pp-pc2}} N/A

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.
See also

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
Category:Wikipedia protected edit requests
Wikipedia:Protection policy/Padlocks

Notes

Created October 2013 as a result of Wikipedia:Requests for comment/Template editor user right‎

[show]

v
t
e

New admin
Categories:

Wikipedia policies
Wikipedia enforcement policies
Wikipedia New admin
Wikipedia vandalism
Wikipedia page protection

Navigation menu

Create account
Log in

Project page
Talk

Read
View source
View history

Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Wikimedia Shop

Interaction

Help
About Wikipedia
Community portal
Recent changes
Contact page

Tools
Print/export
Languages

Afrikaans
Ænglisc
العربية
Aragonés
অসমীয়া
বাংলা
Català
Cebuano
Čeština
Cymraeg
Dansk
Deutsch
ދިވެހިބަސް
Eesti
Ελληνικά
Español
Esperanto
فارسی
Français
Galego
한국어
Հայերեն
Hrvatski
Ilokano
Bahasa Indonesia
Íslenska
Italiano
עברית
Basa Jawa
ქართული
Latina
Lëtzebuergesch
Lietuvių
Magyar
Македонски
Malti
Bahasa Melayu
Монгол
Nederlands
नेपाली
日本語
Norsk bokmål
ଓଡ଼ିଆ
Oʻzbekcha
ភាសាខ្មែរ
Polski
Português
Română
Русский
Саха тыла
Sardu
සිංහල
Simple English
Slovenčina
Slovenščina
Soomaaliga
Српски / srpski
Basa Sunda
Suomi
Svenska
தமிழ்
తెలుగు
ไทย
Türkçe
Удмурт
Українська
Vèneto
Tiếng Việt
ייִדיש
粵語
中文

Edit links

This page was last modified on 6 May 2014 at 00:41.
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.

Privacy policy
About Wikipedia
Disclaimers
Contact Wikipedia
Developers
Mobile view

Wikimedia Foundation
Powered by MediaWiki


Wikipedia:Protection policy
From Wikipedia, the free encyclopedia
Page semi-protected
"WP:PP" redirects here. You may be looking for Wikipedia:Requests for page protection, Wikipedia:Lists of protected pages, Wikipedia:Perennial proposals or WikiProject Parliamentary Procedure.
"WP:PROTECT" redirects here. You may be looking for Wikipedia:Child protection or Wikipedia:WikiProject Protected areas.
Green check.svg This page documents an English Wikipedia policy, a widely accepted standard that all editors must normally follow. Changes made to it should reflect consensus.
Shortcuts:
WP:PP
WP:PROTECT
Enforcement policies

Administrators
Banning policy
Blocking policy
Protection policy

v
t
e

Gold padlock
Fully protected
Pink padlock
Template-protected
Silver padlock
Semi-protected
Blue padlock
Create protected
Green padlock
Move protected
Purple padlock
Upload protected
White padlock
Pending changes protected (level 1)
Orange padlock
Pending changes protected (level 2)
Red padlock
Permanently protected
Black padlock
Protected by Office

Wikipedia is built around 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. However, in particular circumstances, because of a specifically identified likelihood of damage resulting if editing is left open, some individual pages may need to be subject to technical restrictions (often only temporary) on who is permitted to modify them. The placing of such restrictions on pages is called protection.

Protection can be applied to or removed from pages by Wikipedia's administrators, although any user may request these actions. Protection can be indefinite, or expire after a specified time period.

The most commonly encountered types of protection are full protection, which means that a page can be modified only by administrators, and semi-protection, which means that a page can be modified only by users who are logged in and whose accounts have been confirmed (any account is automatically confirmed if it is at least four days old and has made at least ten edits or posts). Other forms of protection are detailed below. Protected pages are normally marked with a small padlock symbol in the top corner; different color padlocks represent different protection types, as shown in the images at the right. Template:Pp-protected is usually used to display the padlock.

Positioning the mouse pointer over the padlock symbol produces an informational tooltip which says "This article is (semi-)protected." If {{Pp-protected}}'s reason parameter is specified, the tooltip also says why the page is protected. If the expiry parameter is specified, the tooltip says for what duration the page is protected.

This policy explains in detail the protection types and procedures for page protection and unprotection, and the reasons for which protection should and should not be applied.

Contents

1 Overview of types of protection
2 Types of protection
2.1 Full protection
2.1.1 Content disputes
2.1.2 Vandalism
2.1.3 "History only" review
2.1.4 Protected generic image names
2.2 Template protection
2.3 Semi-protection
2.3.1 Guidance for administrators
2.4 Creation protection
2.5 Move protection
2.6 Upload protection
2.7 Pending changes protection
2.7.1 When to apply pending changes protection
2.8 Permanent protection
2.9 Office actions
2.10 Cascading protection
2.11 Comparison table
3 Protection by namespace
3.1 Talk pages
3.1.1 User talk pages
3.1.1.1 Blocked users
3.2 User pages
3.2.1 Deceased users
3.3 Protection of templates
3.4 Sandboxes
4 Available templates
5 See also
6 Notes

Overview of types of protection

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

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 that are not confirmed.
Creation protection prevents a page (normally a previously deleted one) from being recreated (also known as "salting").
Move protection protects the page solely from renaming/moving.
Upload protection prevents new versions of a file from being uploaded except by administrators, but it does not prevent editing the file's description page.
Pending-changes protection means edits by unregistered and new contributors are not visible to readers who are not logged in, until the edits are approved by a reviewer or administrator.

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 by an administrator if they are uncontroversial or if there is consensus for them.

Except in the case of office actions (see below) or pages in the MediaWiki namespace (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.
Types of protection

Full protection
Gold padlock
Policy shortcuts:

WP:FPP
WP:FULL
WP:FULL-PRO
WP:GOLDLOCK

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

Content disputes

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.

Policy shortcut:

WP:PREFER

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.
Vandalism
Policy shortcut:

WP:NO-PREEMPT

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.
"History only" review

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.
Protected generic image names

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.

Template protection
Pink padlock
Policy shortcuts:

WP:TEMP-P
WP:TEMP-PRO
WP:TPROT
WP:PINKLOCK

Main page: Wikipedia:Template editor

A template-protected page can be edited only by administrators or users in the Template editors group. This protection level may only be used on high-risk templates and modules, and possibly in rarer cases where pages in other namespaces become transcluded to a very high degree.

This is a new protection level[1] that replaces full protection on pages that are merely protected due to high transclusion rates, rather than content disputes. It should only 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 template editor user right exists – the existence of the right should not result in more templates becoming uneditable for the general editor population.

Semi-protection
Silver padlock
Policy shortcuts:

WP:S-P
WP:SPP
WP:SEMI
WP:SEMI-PRO
WP:SILVERLOCK

See also: Wikipedia:Rough guide to semi-protection

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 at least ten 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.
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, nor should it be used 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) 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. 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, 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 reblocked with talk page editing disallowed. When required, or when reblocking without talk page editing allowed is unsuccessful, protection should be implemented for only a brief period, and not exceeding the duration of the block.

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.

Creation protection
Blue padlock
Policy shortcuts:

WP:SALT
WP:PDP
WP:BLUELOCK

Administrators can prevent the creation of a page through the protection interface. This is useful for articles that have been deleted but repeatedly recreated. 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 (look for one who was previously involved) or use the deletion review process.

There are two levels of creation protection that can be applied to pages. One version is similar to semi-protection which allows autoconfirmed editors to create the page. The other version is similar to full protection which allows only administrators to create the page.

Move protection
Green padlock
Policy shortcuts:

WP:MOVP
WP:MOVE-PRO
WP:GREENLOCK

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 and articles selected as "Today's featured article" on the main page.

Fully protected pages are also move-protected.

As with full protection, protection because of editwarring 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.

Upload protection
Purple padlock
Policy shortcuts:

WP:UPLOAD-P
WP:PURPLELOCK

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.

Pending changes protection
Further information: Wikipedia:Pending changes
Policy shortcuts:

WP:PCPP
WP:WHITELOCK
WP:ORANGELOCK

White padlock Orange padlock

Pending changes protection is a tool used to suppress vandalism and certain other persistent problems, while allowing all users to continue to submit edits. Pending changes protection can be used as an alternative to semi-protection to allow unregistered and new users to edit pages, while keeping the edits hidden to most readers until they are accepted by a 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 reviewer right.

Pending changes are visible in the page history, where they are marked as pending review. The latest accepted revision is displayed to the general public. Logged-in users see the latest revision of the page, with all changes 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.

Both logged-in users and anonymous users who click the "edit this page" tab may edit the latest version as usual. If there are pending changes awaiting review, there will be a dropdown box next to the article title, pointing to the pending changes. For more details, see Help:Pending changes.

Reviewing of pending changes should be resolved within reasonable time limits. Backlog management should be coordinated at a community level.
When to apply pending changes protection

Pending changes may be used to protect articles against:

persistent vandalism
violations of the biographies of living persons policy
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 only be used in cases of severe long-term disruption.

Only what is known as "Pending changes level 1" should be used, which is labeled "Require review for revisions from new and unregistered users". Pending changes level 2, or "Require review for revisions from everyone except Reviewers", should not be used at this time per WP:PC2012/RfC 1.

Removal of pending changes protection can be requested of any administrator, or at requests for unprotection.

The reviewing process is described in detail at reviewing.

Permanent protection
Red padlock
Policy shortcuts:

WP:PPINDEF
WP:PERM-PRO
WP:REDLOCK

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

Office actions
Black padlock
Policy shortcuts:

WP:WMF-P
WP:WMF-PRO
WP:BLACKLOCK

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
Shortcuts:

WP:CASCADE
WP:CASCADING

"WP:CASCADE" redirects here. You may be also looking for Wikipedia:Cascading style sheets.

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 "Protection of templates" section below for alternatives.

Comparison table

The following table compares the effects of protection on Wikipedia users.
Wikipedia users, page protections, and page edits Unregistered, New Autoconfirmed, Confirmed Template editor Reviewer Administrator Appropriate for
No protection can edit;
changes go live* immediately;
no acceptance required The vast majority of pages
Pending changes
level 1 protection can edit;
changes will go live after being accepted by a reviewer can edit;
changes go live immediately (if no previous pending changes remain to be accepted) can edit;
changes go live immediately;**
can accept pending changes Infrequently edited articles that are experiencing high levels of vandalism or BLP violations from unregistered and new users
Semi-protection cannot edit can edit;
changes go live immediately;
no acceptance required Articles experiencing high levels of vandalism or edit warring from unregistered and new users, and for some highly visible templates and modules
Pending changes
level 2 protection can edit;
changes will go live after being accepted by a reviewer can edit;
changes go live immediately;
can accept pending changes No consensus for use on the English Wikipedia per WP:PC2012/RfC 1
Pending changes level 2 with Semi-protection cannot edit can edit;
changes will go live after being accepted by a reviewer can edit;
changes go live immediately;
can accept pending changes No consensus for use on the English Wikipedia per WP:PC2012/RfC 1
Template protection cannot edit can edit;
changes go live immediately;
no acceptance required cannot edit can edit;
changes go live immediately;
no acceptance required High-risk templates and modules
Full protection cannot edit can edit;
changes go live immediately;
no acceptance required Articles experiencing persistent vandalism or edit warring from (auto)confirmed accounts, and for critically important templates and modules
* "Go live" means the edits will be visible to readers who are not logged in. In all cases, edits are always visible to readers logged into Wikipedia.
** When editing articles with un-reviewed pending changes, Administrators and Reviewers are prompted to review the pending changes before saving their edit.
Protection by namespace
Talk pages

Modifications to a 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 protected}} template on the talk page will draw the attention of administrators for implementing uncontroversial changes.

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

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 pages are semi-protected should have an unprotected user talk subpage linked conspicuously from their main talk page to allow good faith comments from non-autoconfirmed users.

A user's request to have his or her own talk page protected is not a sufficient rationale to protect the page.
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 {{unblock}} template, re-blocking the user without talk page access should be preferred over protection. If the user has been indefinitely blocked from editing the talk page, they should be informed of off-wiki ways to appeal their block, such as the UTRS tool interface or ban appeals subcommittee of 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
Policy shortcuts:

WP:UPROT
WP:UPPROT

User pages and subpages can be protected by simple request from the user; this does not apply to the main user talk page. This is common for retired users and talk page archives.
Deceased users
See also: Wikipedia:Deceased Wikipedians/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: Wikipedia:High-risk templates and Wikipedia:Template documentation

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 template-protected based on the degree of visibility, type of use, content, and other factors.

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 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 template editors and account creators).
Sandboxes
See also: Wikipedia:About the Sandbox

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.
Available templates

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

v
t
e

{{pp-meta}} Full Semi Move
Dispute: {{pp-dispute}} {{pp-move-dispute}}
Vandalism: {{pp-vandalism}} {{pp-move-vandalism}}
High visibility templates and modules: {{pp-template}} N/A
User talk of blocked user: {{pp-usertalk}} N/A
Sockpuppetry: {{pp-sock}} N/A
WP:BLP: {{pp-blp}} N/A
Long-term: N/A {{pp-semi-indef}} {{pp-move-indef}}
Generic (other protection): {{pp-protected}} {{pp-move}}
Scrutiny of the Office: {{pp-office}} {{pp-reset}} N/A
Talk page info: {{permanently protected}} {{temporarily protected}} N/A
Create protection: {{pp-create}} N/A
Pending changes protection level 1: {{pp-pc1}} N/A
Pending changes protection level 2: {{pp-pc2}} N/A

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.
See also

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
Category:Wikipedia protected edit requests
Wikipedia:Protection policy/Padlocks

Notes

Created October 2013 as a result of Wikipedia:Requests for comment/Template editor user right‎

[show]

v
t
e

New admin
Categories:

Wikipedia policies
Wikipedia enforcement policies
Wikipedia New admin
Wikipedia vandalism
Wikipedia page protection

Navigation menu

Create account
Log in

Project page
Talk

Read
View source
View history

Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Wikimedia Shop

Interaction

Help
About Wikipedia
Community portal
Recent changes
Contact page

Tools
Print/export
Languages

Afrikaans
Ænglisc
العربية
Aragonés
অসমীয়া
বাংলা
Català
Cebuano
Čeština
Cymraeg
Dansk
Deutsch
ދިވެހިބަސް
Eesti
Ελληνικά
Español
Esperanto
فارسی
Français
Galego
한국어
Հայերեն
Hrvatski
Ilokano
Bahasa Indonesia
Íslenska
Italiano
עברית
Basa Jawa
ქართული
Latina
Lëtzebuergesch
Lietuvių
Magyar
Македонски
Malti
Bahasa Melayu
Монгол
Nederlands
नेपाली
日本語
Norsk bokmål
ଓଡ଼ିଆ
Oʻzbekcha
ភាសាខ្មែរ
Polski
Português
Română
Русский
Саха тыла
Sardu
සිංහල
Simple English
Slovenčina
Slovenščina
Soomaaliga
Српски / srpski
Basa Sunda
Suomi
Svenska
தமிழ்
తెలుగు
ไทย
Türkçe
Удмурт
Українська
Vèneto
Tiếng Việt
ייִדיש
粵語
中文

Edit links

This page was last modified on 6 May 2014 at 00:41.
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.

Privacy policy
About Wikipedia
Disclaimers
Contact Wikipedia
Developers
Mobile view

Wikimedia Foundation
Powered by MediaWiki

المراجعة الحالية بتاريخ 08:10، 7 مارس 2024

يا ويلك و سواد ليلك ان كانت هذه امك

الوظيفة اعادة تأهيلك من جنين سابق الى مواطن زعطوط
دوره في الوحدة العربية كل الشعوب العربية تنادي بأسمه من المحيط الى الخليج
درجة الإهانة شديدة اللهجة و ما تبشر بخير
استعمالات اخرى حرث لمنجل أبيك يأتيه من أين يشاء
موارد طبيعية دم, مخاط, نفط , حضرة جنابك

كس امك لأسباب غير مفهومة تحتل عبارة كس أمك موقع الشتيمة الأكثر استفزازا و إهانة من المخيط الى الخليع , لذا فقد تفاجأ عندما تكتشف ان كس امك هو المكان الذي خرجت منه انت و كل هذه الرجال الغليظة الثخينة أيضا قد خرجت من أكساس امهاتها الذليلة , و يعبر عن هذه الدهشة الفسيولوجية بالمثل العراقي :"شايف مشايف شاف كس امه و اخترع" في دلاله على هول المصيبة باكتشاف ان لأمك كس يمكن ان يدنس رجولتك في أي لحظة . خرجتم من كس امهاتكم عراة حفاة الى هذه الدنيا الواسعة فأين العيب إذا ؟ بعد مضي بضعة سنين تستكشف فيها الحياة الدنيا قررت انك لا تحب البقاء هنا و اعتذرت من امك في الرجوع مرة اخرى الى اللجوء الى الداخل حيث ان ارتباط حبل المشيمة الدافئ اهون من الخوازيق التي تستهدفك في كل مكان , رفض طلبك و منذ ذلك اليوم اقمت الدنيا و لم تقعدها على هذا العضو المسكين في سعيك المتواصل لإيجاد ما يربطك بحبل المشيمة مرة أخرى .

يطلق على المهبل باللغة الشوارعية الإنجليزية كلمة Cunt التي تستعمل كشتيمة للمرأة العنيدة المزعجة من وجهة نظر الرجل ولكن ولسخرية القدر فإن كلمة Cunt مشابهة لكلمات قديمة جدا في قمة المعرفة والروحانيات والاستنارة . فالعضو التناسلي الأنثوي يدعى في اللغة السومرية kunta وتم رسم تلك الإشارات على ألواح الطين حوالي 3100 ق.م حيث تم اختراع اللغة التي سميت باللغة المسمارية وهي تدعى بالإنكليزية Cuneiform وهذه التسمية تعني الشكل المهبلي . في لغات الشرق الأدنى و إفريقيا قديما كان يستخدم لفظ Quna للإشارة إلى المرأة أو مهبلها أو طاقة الحياة. حتى كلمة Whore الإنجليزية التي تعني العاهرة أصلها من الفارسية القديمة houri أي حورية كانت تصور أنها مقيمة في السماء السابعة بانتظار الرجل البطل أو القديس . عند العرب قديما كانت تدار عبادات الآلهة الأم بشكل واسع فكلمة اللات تم تذكيرها إلى الله ، وكلمة العزى تم تذكيرها لتصبح العزيز .

ولفرج المرأة كذلك تسميات تراثية: التبنة ، الطبون ، الحر ، الفرج ، أبو طرطور ، الشق ، الزرزور ، العص ، الغلمون ،الثقيل ،الدكاك السكوتي، ، القنفود ، أبو خشيم ، النفاخ ، الحسن ، الطلاب ، البشيع ، الفشفاش، المقعور ، أبو بلعوم ، العريض ، الواسع ، أبو جبة ، المؤدي ، الهزاز ، الغربال ، أبو عنكرة ، أبو شفرين ، المقابل ، الملقي ، المسبول ،المغيب ، المعبن ،العضاض، المغمور ، المصفح ، الناوي ، الصبار .

دوره كشتيمة[عدل | عدل المصدر]

كس أمك عبارة لا تقول شيئا . مبتدأ بلا خبر . فاعل ، أو مفعول ، بلا فعل ولا مفعول ، أو فاعل . كس أمك ، هي اقتحام للرجل ، أي رجل ، لأنه على حد علمي ، لم يولد رجل حتى الآن بلا أم ، وعلى حد علمي أيضا ، لم توجد امرأة حتى الآن بلا كس ، وإن وجدت ، في خارقة طبيعية ، فهي لم تلد ، أي أنها لم تصبح أما ، أي أنه لم يوجد لها رجل طويل عريض يمكن أن يقال له كس امك . حتى المسيح عليه السلام كان بلا اب ولكنه لا يستطيع الهرب من هذه الشتيمة الغبية . قد تكون اختصار لجملة (عير بكس أمك) ، هنا سنكون أمام جملة اسمية مكونة من مبتدأ هو (عير) وخبره شبه جملة مكونة من حرف الجر (ب) وإسم مجرور بحرف الجر (كس) أما (أمك) فهي مضافة الى الاسم المجرور (كس) ، واختصاراً لطول الجملة حُذِفَ المبتدأ وحُذِف حرف الجر فأصبحت العبارة (كس أمك).

أن يقول رجل لرجل كس أمك فهذا يعني تمزيقا عنيفا لرجولته ، تذكيره بأن أمه هي ست في الأول وفي الآخر وهي عار يمكن ان يقتحم في أي لحظة . الاقتحام تنبع قوته من كونه ليس معلوماتيا ، أنت لا تقول أمك شرموطة فيكذب هذه المعلومة ، ولا تصفه بابن الوسخة فيقول لك أنت اللي ابن ستين وسخة . إنها شتيمة بلا منفذ ، مقفولة على نفسها ، غير مفهومة . وإذا كنا نعيش في مجتمع من العقلاء ، فالرد الوحيد على كلمة كس امك هو سؤال مندهش : ماله ؟ مشخور مثل كس أمك يا روح أمك ؟.

ذكورة كل من الجاني والضحية تتحالف لخلق الشتيمة ، بالأصح لخلق كونها شتيمة . المشتوم يشعر بالإهانة فورما يتذكر أن أمه هي امرأة ذات فرج ، وأن هذا الفرج ، علامة ضعفها الأزلي ، هو السبب في وجوده ، أن وجوده ملوث بالعار ، ملوث بالكس ، والشاتم يعرف كيفية النفاذ إلى المشتوم بتذكيره بهذا العار الذي لا يمحى . في هذا تتحالف كس امك مع يا ابن المتناكة ، ولأن كلنا كائنات بشرية طبيعية فكلنا أولاد متناكة بلا شك ، أو بالأصح ، كلنا أولاد متناكات ، كلنا ملوث بخطيئة وجودنا من صلب كائن يأخذ فيها. غالبا ترتبط كس امك بلفظ اخر مسئ للرجل مثل كس امك يا خول او كس امك يا معرص وهناك تعبير اخر مثل هطلع كس امك بس محدش عارف هيطلعه منين من الكلوت ولا هيطلعه منين بالظبط وهناك ايضا هنيك كس امك

تاريخيا[عدل | عدل المصدر]

كس أمك كغيرها من العبارات النابية في الثقافات الأخرى كفك يو بالإنكليزية و أرش لوخ بالامانية كلمة لا معنى لها لغويا , يعتقد البعض ان الجملة قد تم اختصارها من مصطلحات لغوية أكثر طولا لسهولة اللفظ و كثرة الطلب , قد تذهل عندما تعرف ان العرب القدماء لم يكونوا يتحرجون من الشتيمة كثيرا فهذا العالم الجليل السيوطي الذي أفنى عمره كله ما بين القرآن و الفقه و الأيمان و التقوى يتفرغ لتأليف كتاب مشهور أسمه نواضر الأيك في معرفة النيك, تخيل ان الشعراوي رحمه الله يكتب كتابا عنوانه : "جلي الغمة عمن جهل قدر كس أمه" لتفهم ان تخلف الأمة تخلف جماعي حتى في الشتيمة , من الجمل التي قد تكون أصلا لعبارة كس أمك هي يا عاض بظر أمك و يبدو انها الشتيمة (الغير مفهومة أيضا) الأكثر استخداما في عصر الصحابة المحجلين رضوان الله عليهم كما قال سيدنا ذو النورين رضي الله عنه لسيدنا عمار بن ياسر : يا عاض أير أبيك[1], مع الأخذ بنظر الإعتبار حياء سيدنا عثمان فلا يمكننا ان نتخيل ما سيقوله رجل مهذار مثل عمرو بن العاص مثلا .

كما كان الصحابي ابو بكر الصديق بارعا في استعمال هذه العبارة كما جاء في كتاب السيرة الحلبية في فصل غزوة الحديبية حيث قال لعروة بن مسعود الثقفي : اعضض بظر اللات. والبظر. قطعة تبقى في فرج المرأة بعد الختان، وقيل التي تقطعها الخاتنة علما ان اللات ربما لم يتم ختانها لانها اصلا صنم روماني لفينوس العارية منحوت من المرمر واستوردها العرب من الشام خلال رحلة الصيف وكان العرب يسجدون لها في الجاهلية ومنهم الصحابي ابو بكر الصديق فأنطبع منظر بظرها في مخيلتهم وجرى على لسانهم.

استعمالاتها[عدل | عدل المصدر]

بالزنجباري[عدل | عدل المصدر]

من مشاهير مستخدميها[عدل | عدل المصدر]

  • ناتالي بورتمان. (ما هي سبتك المفضلة؟) [1]

المصادر[عدل | عدل المصدر]

جسم الإنسان

البروستات - بنكرياس – القضيب الذكري - عين - بظر – الجهاز الهضمي – عصب – طيز – مبيض - ثدي - قناة فالوب - سائل منوي - غشاء البكارة - الدماغ - حنجرة

مجلوبة من «https://beidipedia.com/wiki/كس_أمك?oldid=70026»