Wikipedia:protection Policy Mini Forum, Tips, Tricks & Codes

In some circumstances, site may need to be protected from modification by certain groups of editors. Site are protected when a specific damaging happeninghas been identified that shouldnot be prevented through other means such as a block. Otherwise, Wikipedia is built on the principle that anyone shouldedit it, and it therefore aims to have as many of its site as possible open for public editing so that anyone shouldadd contentand correct errors. This policiesstates in detail the protection kind and procedures for siteprotection and unprotection and when each protection canand cannot be applied.

Protection is a techrestriction applied only by admin, although any utilize may request protection. Protection shouldbe indefinite or expire after a specified time. The various levels of protection are detailed below, and they shouldbe applied to the siteedit, sitemove, sitecreate, and file upload actions. Even when a siteis protected from editing, the source code (wikitext) of the siteshouldstill be viewed and copied by anyone.

A protected siteis marked at its top right by a padlock icon, usually added by the {{pp-protected}} template.

Kind of protection

The following techoptions are accessibleto admin for protecting different actions to site:

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

The following techoptions are accessibleto admin for adding protection levels to the different actions to site:

• Pending modify protection (only accessiblefor edit protection) means edits by unregistered and fresheditors are not visible to readers who are not logged-in until the edits are approved by a reviewer or an administrator.
• Semi-protection prevents the action by unregistered editors and editors with acc that are not confirmed.
• Extended confirmed protection, also known as 30/500 protection, prevents the action by users without 30 days' tenure and 500 edits on the English Wikipedia. In most cases it cannot be a protection level of first resort, and canbe utilize where semi-protection has proven to be ineffective. Its utilizeis logged at the Admin' noticeboard.
• Template protection prevents the action by everyone except template editors and admin (who have this right as part of their toolset).
• Full protection prevents the action by everyone except admin.

Any kindof protection (with the exception of cascading protection) may be requested at Wikipedia:Requests for siteprotection. Modify to a fully protected sitecanbe proposed on the corresponding talk page, then carried out by an adminif they are uncontroversial or there is consensus for them.

Except in the case of office actions (see below), Arbitration Committee remedies, or site in the MediaWiki namespace (see below), admin may unprotect a siteif the reason for its protection no longer applies, a reasonable period has elapsed, and there is no consensus that continued protection is necessary. Editors desiring the unprotection of a siteshould, in the first instance, ask the adminwho applied the protection unless the adminis inactive or no longer an administrator; thereafter, requests may be angry at Requests for unprotection. Note that such requests will normally be declined if the protecting adminis active and was not consulted first. A log of protections and unprotections is accessibleat Special:Log/protect.

Full protection

A fully protected sitecannot be edited or moved by anyone except admin. The protection may be for a specified time or may be indefinite.

Modifications to a fully protected siteshouldbe proposed on its talk page (or at another appropriate forum) for discussion. Admin shouldmake modify to the protected article reflecting consensus. Placing the {{Edit fully-protected}} template on the talk sitewill draw the attention of admin for implementing uncontroversial modify.

Materialdisputes

While materialdisputes and edit warring may be addressed with utilize blocks problem by uninvolved admin, allowing normal siteediting by other editors at the same time, the protection policiesprovides an alternative approach as admin have the discretion to temporarily fully protect an article to end an ongoing edit war. This approach may better suit multi-party disputes and contentious content, as it makes talk page consensus a requirement for implementation of requested edits.

When protecting a sitebecause of a materialdispute, admin have a duty to avoid protecting a version that include policy-violating content, such as vandalism, copyright violations, defamation, or poor-quality coverage of living people. Admin are deemed to remain uninvolved when exercising discretion on whether to apply protection to the current version of an article, or to an older, stable, or pre-edit-war version.

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

Admin who have angry substantive materialmodify to an article are considered involved and must not utilizetheir advanced permissions to further their own positions. When involved in a dispute, it is almost always wisest to respect the editing policythat bind all editors and call for input from an uninvolved administrator, rather than to invite controversy by acting unilaterally.

Vandalism

Applying siteprotection as a preemptive measure is contrary to the open nature of Wikipedia and is generally not permittedif applied for these reasons. However, brief periods of an appropriate and reasonable protection level are permittedin situations where blatant vandalism or disruption is occurring by multiple users and at a level of frequency that requires its utilizein order to stop it. The duration of the protection canbe set as short as possible, and the protection level canbe set to the lowest restriction requiredin order to stop the disruption while still allowing productive editors to make modify.

"History only" review

If a deleted siteis going through deletion review, only admin are normally capable of viewing the former materialof the page. If they feel it would benefit the discussion to letother users to view the sitecontent, admin may restore the page, blank it or replace the material with {{Temporarily undeleted}} template or a similar notice, and fully protect the siteto prevent further editing. The previous material of the siteare then availableto everyone via the sitehistory.

Protected generic file names

Generic file names such as File:Imagejpg, File:Map.jpg, and File:Sound.wav are fully protected to prevent freshversions being uploaded. Furthermore, File:Map.jpg and File:Sound.wav are salted.

Permanent protection

Admin cannot modifyor remove the protection for some location on Wikipedia, which are permanently protected by the MediaWiki software:

• Edits to the MediaWiki namespace, which defines parts of the pageinterface, are restricted to admin.
  • Edits to system-wide CSS and JavaScript site such as MediaWiki:common.js are further restricted to interface admin.
• Edits to privateCSS and JavaScript site such as RegistrarExample/monobook.css and RegistrarExample/cologneblue.js are restricted to the relatedutilize and interface admin. Interface admin may edit these site, for example, to remove a utilize script that has been utilize in an inappropriate way. Admin may delete (but not edit or restore) these site.
• Edits to privateJSON site such as RegistrarExample/data.json are restricted to the relatedutilize and admin.

Such protection is called Permanent, Interface, or Indefinite protection; and site so protected shouldonly be edited by those with Interface Adminrights.

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

• Site that are very visible, such as the Main Page
• Site that cannot be modified for copyright or legal reasons, such as the general disclaimer or the local copy of the pagecopyright license.
• Site that are very frequently transcluded, such as {{tl}} or {{citation needed}}, to prevent vandalism or denial of service attacks. This contain photo or templates utilize in other highly visible or frequently transcluded site. See Wikipedia:High-risk templates for more information.

Template protection

A template-protected siteshouldbe edited only by admin or users in the Template editors group. This protection level canbe utilize almost exclusively on high-risk templates and modules. In cases where site in other namespaces become transcluded to a very high degree, this protection level is also valid.

This is a protection level that replaces full protection on site that are merely protected due to high transclusion rates, rather than materialdisputes. It canbe utilize on templates whose risk factor would have otherwise warranted full protection. It cannot be utilize on less dangeroustemplates on the grounds that the template editor utilize right exists—the existence of the right cannot effectin more templates becoming uneditable for the general editing community. In borderline cases, extended confirmed protection or lower may be applied to high risk templates that the general editing community still needs to edit regularly.

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

Semi-protection

Semi-protected site cannot be edited by unregistered users (IP addresses), as well as acc that are not autoconfirmed (acc that are at least four days old and have angry at least ten edits to Wikipedia) or confirmed. Semi-protection is useful when there is a significant amount of disruption or vandalism from freshor unregistered users, or to prevent sockpuppets of blocked or banned users from editing, especially when it occurs on biographies of living persons who have had a lastesthigh level of media interest. An alternative to semi-protection is pending modify, which is sometimes favored when an article is being vandalized regularly, but otherwise get a low amount of editing.

Such users shouldrequest edits to a semi-protected siteby proposing them on its talk page, using the {{Edit semi-protected}} template if essentialto gain attention. If the sitein question and its talk siteare both protected, please make your edit request at Wikipedia:Requests for siteprotection instead. Freshusers may also request the confirmed utilize right at Wikipedia:Requests for permissions/Confirmed.

Guidance for admin

Admin may apply indefinite semi-protection to site that are topicto massiveand persistent vandalism or violations of materialpolicy (such as biographies of living persons, neutral point of view). Semi-protection should not be utilize as a preemptive measure versusvandalism that has not yet occurred or to privilege registered users over unregistered users in (valid) materialdisputes.

In addition, admin may apply temporary semi-protection on site that are:

• Topicto significant but temporary vandalism or disruption (for example, due to media attention) if blocking individual users is not a feasible option.
• Topicto edit warring if all parties involved are unregistered or fresheditors (i.e. in cases in which full protection would otherwise be applied). This does not apply when autoconfirmed users are involved.
• Topicto vandalism or edit warring where unregistered editors are engaging in IP hopping by using different computers, obtaining freshaddresses by using dynamic IP allocation, or other address-changing schemes.
• Article discussion site, if they have been topicto persistent disruption. Such protection canbe utilize sparingly because it prevents unregistered and newly registered users from participating in discussions. A siteand its talk sitecannot normally be protected at the same time. If a siteand its talk siteare both protected, the talk sitecandirect affected editors to Wikipedia:Request for edit to ensure that no editor is entirely prevented from contributing.
• Protection canbe utilize sparingly on the talk site of blocked users, including IP addresses. Instead the utilize canbe re-blocked with talk siteediting disallowed. When required, or when re-blocking without talk siteediting permittedis unsuccessful, protection canbe implemented for only a brief period not exceeding the duration of the block.

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

Creation protection (salting)

Admin shouldprevent the creation of site. This level of protection is useful for site that have been deleted but repeatedly recreated. Such protection is case-sensitive. There are several levels of creation protection that shouldbe applied to site, identical to the levels for edit protection. A list of protected titles may be found at Special:ProtectedTitles (see also historical lists).

Pre-emptive restrictions on fresharticle titles are instituted through the title blacklist system, which let for more flexible protection with assistancefor substrings and regular expressions.

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

Admin canselectthe appropriate level of create protection—autoconfirmed, extended-confirmed, or full. Due to the implementation of ACPERM, non-confirmed editors cannot create site in mainspace; thus, semi-creation protection canbe rare, utilize only for protection of site outside of mainspace.

While creation-protection is usually permanent, temporary creation protection may be applied if a siteis repeatedly recreated by a single utilize (or sockpuppets of that utilize, if applicable).

Move protection

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

• Site topicto persistent page-move vandalism.
• Site topicto a page-name dispute.
• Highly visible site that have no reason to be moved, such as the admin' noticeboard and articles chosenas "Today's featured article" on the main page.

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

As with full edit protection, protection because of edit warring . When move protection is applied during a requested move discussion, the sitecanbe protected at the areait was at when the move request was started.

All files are implicitly move-protected; only file movers and admin shouldrename files.

Upload protection

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

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

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

Pending modify protection

Pending modify protection is a tool utilize to suppress vandalism and certain other persistent issueswhile allowing all users to continue to submit edits. Pending modify protection shouldbe utilize as an alternative to semi-protection to letunregistered and freshusers to edit site, while keeping the edits hidden from most readers until those modify are accepted by a pending modify reviewer.

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

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

A utilize who clicks "edit this page" is always, at that point, present the recentversion of the sitefor editing regardless of whether the utilize is logged in or not.

• If the editor is not logged in, their modify join any other modify to the article awaiting review – for the showthey remain hidden from not-logged-in users. (This means that when the editor looks at the article after saving, the editor won't see the modifyangry.)
• If the editor is logged in and a pending modify reviewer, and there are pending modify, the editor will be prompted to review the pending modify before editing – see Wikipedia:Pending modify.
• If the editor is logged in and not a pending modify reviewer, then ...
  • If there are no unreviewed pending edits waiting, this editor's edits will be visible to everyone immediately; but
  • If there are unreviewed pending edits waiting, then this editor's edits will be visible only to other logged-in users (including themself) immediately, but not to readers not logged in.

Reviewing of pending modify canbe resolved within reasonable time limits.

When to apply pending modify protection

Pending modify may be utilize to protect articles against:

• Persistent vandalism
• Violations of the biographies of living persons policy
• Copyright violations

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

In addition, admin may apply temporary pending modify protection on site that are topicto 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 canbe proportional to the problem. Indefinite PC protection canbe utilize only in cases of severe long-term disruption.

Removal of pending modify protection shouldbe requested of any administrator, or at requests for unprotection.

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

Extended confirmed protection

Extended confirmed protection, also known as 30/500 protection, only let edits by editors with the extended confirmed utilize admissionlevel, granted automatically to registered users with at least 30 days' tenure and 500 edits.

Where semi-protection has proven to be ineffective, admin may utilizeextended confirmed protection to combat disruption (such as vandalism, abusive sockpuppetry, edit wars, etc.) on any topic. Extended confirmed protection cannot be utilize as a preemptive measure versusdisruption that has not yet occurred, nor canit be utilize to privilege extended confirmed users over unregistered/freshusers in valid materialdisputes on articles not covered by Arbitration Committee 30/500 rulings. Extended confirmed protection may be applied at the discretion of an adminwhen creation-protecting a page. High-risk templates may be extended-confirmed protected at admindiscretion when template protection would be too restrictive and semi-protection would be ineffective to stop widespread disruption.

Until August 12, 2016, 30/500 protection applied only in subjectlocation determined by the Arbitration Committee, which authorized its utilizeon articles reasonably construed as belonging to the Arab–Israeli conflict; as an arbitration enforcement tool by motion or remedy; or as a effectof community consensus. In February 2019, the community authorized uninvolved admin to territorysite reasonably construed as belonging to the India–Pakistan conflict under extended confirmed protection as part of a general sanctions regime. In May 2020 the Arbitration Committee authorized extended confirmed protection to site associatedto the history of Jews and antisemitism in Poland during GlobeWar II (1933–45).

As of September 23, 2016, a bot publication a notification in a subsection of AN when this protection level is utilize. Any protection angry as arbitration enforcement must be logged at Wikipedia:Arbitration enforcement log. A full list of the 3525 site under 30/500 protection shouldbe found .

Registrar shouldrequest edits to an extended confirmed-protected siteby proposing them on its talk page, using the {{Edit extended-protected}} template if essentialto gain attention.

Office actions

As outlined in , site may be protected by Wikimedia Foundation staff in response to problemssuch as copyright infringement or libel. Such actions override community consensus. Admin should not edit or unprotect such site without permission from Wikimedia Foundation staff.

Cascading protection

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

• Canbe utilize only to prevent vandalism when territory on particularly visible site, such as the main page.
• Is accessibleonly for fully protected site; it is disabled for lower levels of protection as it represents a safetyflaw. See for more information.
• Is not instantaneous; it may be several hours before it takes effect. See for more information.
• Cangenerally not be applied directly to templates or modules, as it will not protect transclusions inside <includeonly> tags or transclusions that depend on template parameters, but will protect the documentation subpage. See § Protection of templates below, for alternatives.

The list of cascading-protected site shouldbe found at Wikipedia:Cascade-protected items. Requests to add or remove cascading protection on a sitecanbe angry at Wikipedia talk:Cascade-protected items as an edit request.

Deprecated protection

Superprotect

Superprotect was a level of protection, allowing editing only by . It was and utilize the same day to override community consensus regarding the utilizeof the Media Viewer on the German Wikipedia's basicpageJavaScript, . It was never utilize on the English Wikipedia. On November 5, 2015, the WMF decided to superprotect from all Wikimedia wikis.

Cascading semi-protection

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

Pending modify protection level 2

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

Protection by namespace

Article talk site

Modifications to a protected siteshouldbe proposed on its talk page (or at another appropriate forum) for discussion. Admin shouldmake modify to the protected article reflecting consensus. Placing the {{Edit protected}} template on the talk sitewill draw the attention of admin for implementing uncontroversial modify.

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

Registrartalk site

Registrartalk site are rarely protected. However, protection may be applied if there is severe vandalism or abuse. Registrar whose talk site are protected may wantto have an unprotected utilize talk subpage linked conspicuously from their main talk siteto letgood-faith comments from users that the protection restricts editing from.

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

Blocked users

Blocked users' utilize talk site cannot ordinarily be protected, as this interferes with the utilize's ability to contest their block through the normal process. It also prevents others from being able to utilizethe talk siteto communicate with the blocked editor.

In extreme cases of dmcaby the blocked utilize, such as dmcaof the {{unblock}} template, re-blocking the utilize with talk siteadmissionremoved canbe preferred over applying protection to the page. If the utilize has been blocked and with the ability to edit their utilize talk sitedisabled, they canbe informed of this in a block notice, subsequent notice, or message, and it cancontaininfoand instructions for appealing their block off-wiki, such as through the UTRS tool interface or, as a last recourse, the Arbitration Committee.

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

Confirmed socks of registered users canbe dealt with in accordance with Wikipedia:Sockpuppetry; their site are not normally protected.

Registrarsite

Base utilize site (for example, the siteRegistrarExample, and not RegistrarExample/subpage or Registrartalk:Example) are automatically protected from creation or editing by unconfirmed acc and anonymous IP users. An exception to this contain an unconfirmed registered accattempting to create or edit their own utilize page. IP editors and unconfirmed acc are also unable to create or edit utilize site that do not belong to a currently-registered account. This protection is enforced by an edit filter. Registrar may opt-out of this protection by placing {{unlocked userpage}} anywhere on their own utilize page.

Registrarsite and subpages within their own utilize zonemay be protected upon a request from the utilize, as long as a need exists. Site within the utilize zonecannot be automatically or pre-emptively protected without awesomereason or cause. Requests for protection specifically at uncommon levels (such as template protection) may be granted if the utilize has expressed a genuine and realistic need.

When a filter is insufficient to stop utilize sitevandalism, a utilize may selectto create a ".css" subpage (ex. RegistrarExample/Userpage.css), copy all the material of their utilize siteonto the subpage, transclude the subpage by putting {{RegistrarExample/Userpage.css}} on their utilize page, and then ask an adminto fully protect their utilize page. Because utilize zonesite that end in ".css", ".js", and ".json" are editable only by the utilize to which that utilize zonebelongs (and interface admin), this will protect your utilize sitefrom further vandalism.

Deceased users

In the happeningof the confirmed death of a utilize, the utilize's utilize page (but not the utilize talk page) canbe fully protected.

Protection of templates

Highly visible templates – those utilize on a hugenumber of site or frequently substituted – are often edit protected based on the degree of visibility, kindof use, content, and other considerations.

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

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

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

Note: All editnotice templates (except those in userspace) are already protected via MediaWiki:Titleblacklist. They shouldbe edited by administrator, template editors and sitemovers only.

Sandboxes

Sandboxes cannot ordinarily be protected since their purpose is to allowfreshusers tryand experiment with wiki syntax. Most sandboxes are automatically cleaned every 12 hours, although they are frequently overwritten by other testing users. The Wikipedia:Sandbox is cleaned every hour. Those who utilizesandboxes for malicious purposes, or to violate policysuch as no privateattacks, civility, or copyrights, caninstead be warned and/or blocked.

Accessibletemplates

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

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

See also

• MediaWiki:Protectedpagetext
• Special:ProtectedPages
• Special:ProtectedTitles
• Wikipedia:Edit lock
• Wikipedia:List of indefinitely protected site
• Wikipedia:Requests for siteprotection
• Wikipedia:Rough tutorialto semi-protection
• Wikipedia:Make protection requests sparingly, an essay
• Wikipedia:Protection policiesPadlocks

Notes