Scratchpad:Protection policy

Administrators can protect and unprotect pages, including ones that do not exist. Protection of a page or image usually means that a non-sysop cannot modify it.

The majority of pages on all wikis should remain publicly editable, and not protected. Pages may, however, be temporarily or permanently protected for legal reasons, in cases of extreme vandalism, edit warring, and/or abusive re-creation.

Uses

 * Protecting highly vandalised pages, such as the Main Page on large wikis.
 * Maintaining the integrity of the site’s logo and favicon.
 * Maintaining the integrity of key copyright and licence pages.
 * Preventing repeatedly created vandal or spam pages from creation. See Special:ProtectedTitles
 * Protecting the interface and system messages in the MediaWiki namespace (these are protected automatically)

A temporary protection is used for:
 * Enforcing a “cool down” period to stop an “edit war”, upon request.
 * Protecting a page or image that has been a recent target of persistent vandalism or persistent edits by a banned/blocked user.

There is no need to protect personal  and   pages such as follows: Only the accounts associated with these pages (and admins) are able to edit them. (For more information on using these pages, see Help:User style)
 * global.css
 * global.js
 * common.css
 * common.js
 * wikia.css
 * wikia.js
 * monobook.css
 * monobook.js

Usage
Most pages and images are unprotected by default. Only the site logo, favicons, and the entirety of the MediaWiki namespace, are automatically protected.

You can protect editing, moving, or both by checking/unchecking the appropriate boxes, and making the appropriate selection from the pulldown menus.


 * Allow all users
 * unprotected &rarr; any user — whether logged-in or anonymous — can edit or move the page.
 * Block new and unregistered users
 * semi-protected &rarr; anonymous users, and new accounts less than four days old and/or with less than 10 edits, cannot edit and/or move pages.


 * Block all non-admin users
 * fully-protected &rarr; only Administrators may edit and/or move the page.

Cascade protection
Pages can also be cascade protected, this will cause all images, pages, or templates transcluded onto the page to be fully protected, even if the main article is only semi-protected.

At, pages are never cascade protected due to the unforeseen and unintended consequences that so often flow from cascade protection.

Move protection
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 Noticeboard and the main page.

Fully protected pages are also move-protected.

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

Rules for Administrators

 * 1) Do not make the common mistake of protecting pages unnecessarily. For example, do not protect a page simply because it is the Main Page.
 * 2) Do not edit a temporarily protected page except to add a notice explaining the page is protected.
 * 3) Do not protect a page you are involved in an edit dispute over. Administrative powers are not editor privileges — sysops should only act as servants to the user community at large.
 * 4) Avoid favoring one version of the article over another, unless one version is vandalism.
 * 5) Temporarily protected pages should not be left protected for very long.
 * 6) User pages and subpages can be protected by simple request from the user.
 * 7) Talk pages and user talk pages are not protected except in extreme circumstances.
 * 8) * Blocked users only have their user talk pages blocked to them if and only if they abuse the privilege of editing their own user talk page while blocked (e.g., abusively using the template while blocked).
 * 9) The protection of a page on any particular version is not meant to express support for that version and requests should therefore not be made that the protected version be reverted to a different one.