Page protected

MicroWiki:Protection policy

From MicroWiki, the free micronational encyclopædia
Jump to navigation Jump to search

White padlock Pending changes protected
Whitelock
Silver padlock Semi-protected
Silverlock
Dark blue padlock Extended confirmed protected
Bluelock
Pink padlock Template-protected
Pinklock
Gold padlock Fully-protected
Goldlock
Brown padlock Interface protected
Redlock
Green padlock Move protected
Greenlock
Blue padlock Create protected
Skybluelock
Purple padlock Upload protected
Purplelock
Turquoise padlock Cascade protected
Turquoiselock
Black padlock Protected by Office
Blacklock

Protection of a page is a type of action taken by an administrator that prevents certain or all user groups from editing or creating a specified page. This is usually done in response to vandalism or a threat of vandalism, or in some instances of high traffic pages and templates. Protection is usually done at the discretion of an individual administrator. Users may request protection of their pages by contacting individual administrators. Proposed changes to any protected page should be requested on the talk page of the affected page, and admins should ideally be notified.

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

Types of protection

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

  • Edit protection protects the page from being edited.
  • Move protection protects the page from being moved or renamed.
  • Creation protection prevents a page (normally a previously deleted one) from being created.
  • Upload protection prevents new versions 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 technical options are available to administrators for adding protection levels to the different actions to pages:

  • Semi-protection prevents the action by unregistered users and users with accounts that are not confirmed.
  • Full protection prevents the action by everyone except administrators.

Interaction of MicroWiki user groups and page protection levels
  Unregistered or newly registered Confirmed or autoconfirmed Extended confirmed Template editor Admin Interface admin Appropriate for
No protection normal editing The vast majority of pages. This is the default protection level.
Semi cannot edit normal editing Pages that have been persistently vandalized by anonymous and registered users. Some highly visible templates and modules.
Extended confirmed cannot edit normal editing* Pages where semi-protection has failed, or high-risk templates where template protection would be too restrictive.
Template cannot edit normal editing High-risk or very-frequently used templates and modules. Some high-risk pages outside of template space.
Full cannot edit normal editing Pages with persistent disruption from extended confirmed accounts. Critical templates and modules.
Interface cannot edit normal editing Scripts, stylesheets, and similar objects central to operation of the site or that are in other editors' user spaces.
* In order to edit through extended confirmed protection, a template editor must also be extended confirmed, but in practice this is almost always the case.
Other modes of protection:

Creation protection (salting)

Blue padlock

Administrators can prevent the creation of pages. This type of protection is useful for pages that have been deleted but repeatedly recreated. Such protection is case-sensitive. There are several levels of creation protection that can be applied to pages, identical to the levels for edit protection. A list of protected titles can be found at Special:ProtectedTitles.

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". Editors wishing to re-create a salted title with appropriate content should contact an administrator (preferably the protecting administrator). To make a convincing case for re-creation, it is helpful to show a draft version of the intended article when filing a request.