Starfleet Logistics:Protection policy

"SF:PP" redirects here. You may be looking for Starfleet Logistics:Requests for page protection, Starfleet Logistics:Lists of protected pages, Starfleet Logistics:Perennial proposals, WikiProject Parliamentary Procedure or Starfleet Logistics:Party and person.

"SF:PROTECT" redirects here. You may be looking for Starfleet Logistics:Child protection or Starfleet Logistics:WikiProject Protected areas.

Enforcement policies
Administrators Banning policy Blocking policy Protection policy

Template:Padlock list Starfleet Logistics is built around/with 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 some 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 but sometimes indefinitely) 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 only by Starfleet Logistics's administrators, although any user may request protection. Protection can be indefinite or expire after a specified time period.

The most commonly used 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 has existed for at least four days and has made at least ten edits). Other types of protection are detailed below. Protected pages are normally marked with a small padlock icon in the top right corner of the article page; different color padlocks represent different protection types, as shown in the images at the right. The template {{pp-protected}} is usually placed on protected pages to display the padlock. Even when protected, the source code (text) of the page can still be viewed and copied by any user.

Placing the mouse pointer over a padlock icon produces an informational tooltip saying "This article is protected." If the padlock template'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.

Overview of 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 (also known as "salting").
• 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 contributors and contributors with accounts that are not confirmed.
• Pending-changes protection (only available for edit 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.
• Extended confirmed protection, also known as 30/500 protection, prevents the action by users without 30 days tenure and 500 edits on the English Starfleet Logistics. It is applied to combat any form of disruption where semi-protection has proven to be ineffective. It should not be applied as a protection level of first resort. Its use is logged at the Administrators' noticeboard.
• Template protection prevents the action by everyone except template editors and administrators (who have this right as part of their toolset).
• Full protection prevents the action by everyone except administrators.

Any type of protection (with the exception of cascading protection) may be requested at Starfleet Logistics: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), Arbitration Committee remedies, 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. Editors desiring the unprotection of a page should, in the first instance, ask the administrator who applied the protection unless the administrator is inactive or no longer an administrator; thereafter, requests may be made at Requests for unprotection. Note that such requests will normally be declined if the protecting administrator is active and was not consulted first. A log of protections and unprotections is available at Special:Log/protect.

Template:Protection table

Types of protection

Full protection

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

Content disputes

See also: Starfleet Logistics:Stable version

Content disputes and edit warring may be addressed with blocks issued by uninvolved administrators while allowing normal page editing by other editors. Under the protection policy, an alternative approach is available as administrators have the discretion to temporarily fully protect an article to end an ongoing edit war. This approach may be better suited to multi-party disputes and contentious content as talk page consensus becomes a requirement for implementation of requested edits.

When protecting a page because of a content dispute, administrators have a duty to avoid protecting a version that contains policy-violating content, such as vandalism, copyright violations, defamation, or poor-quality coverage of living people. Administrators remain uninvolved when exercising their discretion, subject to this proviso, to decide whether to apply protection to the most current version of an article, or to an older, stable, or pre-edit-war version.

Protected pages may not be edited except to make changes that are uncontroversial or for which there is clear consensus. Editors convinced that the protected version of an article contains 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 should consider how independent editors might view the suggestion and recognize that continuing an edit war is grounds for being blocked.

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

Vandalism

Applying page protection as a preemptive measure is contrary to the open nature of Starfleet Logistics and is generally not allowed if applied for these reasons. However, brief periods of an appropriate and reasonable protection level are allowed in situations where blatant vandalism or disruption is occurring and at a level of frequency that requires its use in order to stop it. The duration of the protection should be set as short as possible, and the protection level should be set to the lowest restriction needed in order to stop the disruption while still allowing productive editors to make changes.

"History only" review

If a deleted page is going through 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 everyone via the page history.

Protected generic file names

Generic file names such as File:Map.jpg, File:Photo.jpg, and File:Sound.wav are fully protected to prevent new versions being uploaded.

Permanent protection

Administrators cannot change or remove the protection for some areas on Starfleet Logistics which are permanently protected by the MediaWiki software:

• Edits to the MediaWiki namespace, which defines parts of the site interface, are restricted to administrators.
  • Edits to system-wide CSS and JavaScript pages such as MediaWiki:common.js are further restricted to interface administrators.
• Edits to personal CSS and JavaScript pages such as User:Example/monobook.css and User:Example/cologneblue.js are restricted to the associated user and interface administrators. Interface administrators may edit these pages, for example, to remove a user script that has been used in an inappropriate way. Administrators may delete (but not edit) these pages.
• Edits to personal JSON pages such as User:Example/data.json are restricted to the associated user and administrators.

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 Starfleet Logistics:High-risk templates for more information.

Template protection

Main page: Starfleet Logistics:Template editor

A template-protected page can be edited only by administrators or users in the ⧼group-templateeditor⧽ group. This protection level should be used almost exclusively on high-risk templates and modules. In cases where pages 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 pages that are merely protected due to high transclusion rates, rather than content disputes. It should 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 editing community.

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

Semi-protection

See also: Starfleet Logistics: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 made at least ten edits to Starfleet Logistics) or confirmed. This level of protection is useful when there is a significant amount of disruption or vandalism from new or 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 recent high level of media interest. An alternative to semi-protection is pending changes, which is sometimes favored when an article is being vandalized regularly, but otherwise receives a low amount of editing.

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 Starfleet Logistics: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 Starfleet Logistics: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 re-blocked with talk page editing disallowed. When required, or when re-blocking 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 that 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 Starfleet Logistics:Main Page featured article protection.

Creation protection (salting)

Administrators can prevent the creation of a page through the protection interface. This is useful for bad articles 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 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 appropriate content should either contact an administrator (preferably the protecting administrator), file a request at Starfleet Logistics:Requests for page protection, or use the deletion review process. To make a convincing case for re-creation, it is helpful to show a draft version of the intended article when filing a request.

Administrators should choose the appropriate level of create protection—autoconfirmed, extended-confirmed, or full. Due to the implementation of ACPERM, non-confirmed editors cannot create pages in mainspace; thus, semi-creation protection should be rare, used only for protection of pages outside of mainspace.

Move protection

Move protected pages, or more technically, fully 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 edit-protected pages are also implicitly move-protected.

As with full edit 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.

All files are implicitly move-protected; only file movers and administrators can move files.

Upload protection

Upload protected files, or more technically, fully 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.
• Files with common or generic names.

As with full edit 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: Starfleet Logistics:Pending changes

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 from the view of most readers until those changes 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 Starfleet Logistics readers, until it is reviewed and accepted by an editor with the pending changes reviewer right. When a page under pending changes protection is edited by an autoconfirmed user, the edit will be immediately visible to Starfleet Logistics readers.

Pending changes are visible in the page history, where they are marked as pending review. Readers not logged in (the vast majority of readers) are shown the latest accepted version of the page; logged-in users see the latest version of the page, with all changes (reviewed or not) 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.

A user who clicks "edit this page" is always, at that point, shown the latest version of the page for editing regardless of whether the user is logged in or not.

• If the editor is not logged in, his or her changes join any other changes to the article awaiting review – for the present they remain hidden from not-logged-in users. (This means that when the editor looks at the article after saving, he won't see the change he just made.)
• If the editor is logged in and a pending changes reviewer, and there are pending changes, the editor will be prompted to review the pending changes before editing – see Starfleet Logistics:Pending changes.
• If the editor is logged in and not a pending changes 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 himself) immediately, but not to readers not logged in.

Reviewing of pending changes should be resolved within reasonable time limits.

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 be used only in cases of severe long-term disruption.

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

The reviewing process is described in detail at Starfleet Logistics:Reviewing pending changes.

Extended confirmed protection

See also: Starfleet Logistics:Rough guide to extended confirmed protection

Extended confirmed protection, also known as 30/500 protection, allows edits only by editors with the extended confirmed user access level, granted automatically to registered users with at least 30 days tenure and 500 edits.

Where semi-protection has proven to be ineffective, administrators may use extended confirmed protection to combat disruption (such as vandalism, abusive sockpuppetry, edit wars, etc.) on any topic. Extended confirmed protection should not be used as a preemptive measure against disruption that has not yet occurred, nor should it be used to privilege extended confirmed users over unregistered users in valid content disputes on articles not covered by Arbitration Committee 30/500 rulings. Extended confirmed protection may be applied by an administrator at their discretion when creation-protecting a page.

Until August 12, 2016, 30/500 protection applied only in topic areas determined by the Arbitration Committee, which authorized its use on articles reasonably construed as belonging to the Arab–Israeli conflict; as an arbitration enforcement tool by motion or remedy; or as a result of community consensus. In February 2019, the community authorized uninvolved administrators to place pages reasonably construed as belonging to the India–Pakistan conflict under extended confirmed protection as part of a general sanctions regime. As of September 23, 2016, a bot posts a notification in a subsection of AN when this protection level is used. A full list of the User:MusikBot/ECPMonitor/Total pages under 30/500 protection can be found here.

Users can request edits to an extended confirmed-protected page by proposing them on its talk page, using the {{Edit extended-protected}} template if necessary to gain attention.

Office actions

As outlined in Meta:Office actions#Use of advanced rights by Foundation staff, pages may be protected by Wikimedia Foundation staff in response to issues such as copyright infringement or libel. Such actions override community consensus. Administrators should not edit or unprotect such pages without permission from Wikimedia Foundation staff.

Cascading protection

"SF:CASCADE" redirects here. You may be also looking for Starfleet Logistics: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 the English Starfleet Logistics. Files stored on Commons are not protected by any other wiki's cascading protection and must be temporarily uploaded to the English Starfleet Logistics or protected at Commons, either manually or through cascading protection there. When operational, KrinkleBot cascade-protects Commons files transcluded at Starfleet Logistics:Main Page/Tomorrow, Starfleet Logistics:Main Page/Commons 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 news, for which upcoming images are not queued at Starfleet Logistics:Main Page/Tomorrow.) 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 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 the "Protection of templates" section below for alternatives.

The list of cascading-protected pages can be found at Starfleet Logistics:Cascade-protected items. Requests to add or remove cascading protection on a page should be made at Starfleet Logistics talk:Cascade-protected items as an edit request.

Deprecated protection

Superprotect

Superprotect was a level of protection, allowing editing only by Wikimedia Foundation employees who are in the Staff global group. It was implemented on August 10, 2014 and used the same day to override community consensus regarding the use of the Media Viewer on the German Starfleet Logistics's primary site JavaScript, common.js. It was never used on the English Starfleet Logistics. On November 5, 2015, the WMF decided to remove superprotect from all Wikimedia wikis.

Cascading semi-protection

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

Pending changes protection level 2

Originally, two levels of pending changes protection existed, where level 2 required edits by all users who are not pending changes reviewers to be reviewed. Following a community discussion, level 2 was retired from the English Starfleet Logistics in January 2017. It was suggested then that "Pending changes level 1" be referred to in the future as simply "Pending changes".

Protection by namespace

Article 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 semi-protected only 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 by itself to protect the page, although requests may be considered if a reason is provided.

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 as a last recourse, 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 Starfleet Logistics:Sockpuppetry; their pages are not normally protected.

User pages

Base user pages (for example, the page User:Example, and not User:Example/subpage or User talk:Example) are automatically protected from creation or editing by unconfirmed and IP users. An exception to this includes an unconfirmed registered user attempting to edit their own user page. IP and unconfirmed editors are also unable to create or edit user pages that do not belong to a registered user. This protection is enforced by a filter. Users may opt-out of this protection by placing {{unlocked userpage}} anywhere on their own page.

User pages and subpages may be protected upon a request from the user, as long as a need exists—pages in user space should not be automatically or pre-emptively protected. Requests for protection specifically at uncommon levels (such as template protection) may be granted if the user has expressed a genuine and realistic need.

When a filter is insufficient to stop user page vandalism, a user may choose to create a ".css" subpage (ex. User:Example/Userpage.css), copy all the contents of their user page onto the subpage, transclude the subpage by putting {{User:Example/Userpage.css}} on their user page, and then ask an administrator to fully protect their user page. Because user space pages that end in ".css", ".js", and ".json" are editable only by the user to which that user space belongs (and interface administrators), this will protect your user page from further vandalism.

Deceased users

See also: Starfleet Logistics:Deceased Starfleet Logisticians/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

See also: Starfleet Logistics:High-risk templates and Starfleet Logistics:Template documentation

Highly visible templates, which are used on an extremely large number of pages or substituted with great frequency, are often semi- or template-protected based on the degree of visibility, type of use, content, etc.

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 protected. Only manually add {{pp-template}} to protected templates that don't use {{documentation}} (mostly the 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. They can be edited by admins, template editors and page movers only.

Sandboxes

See also: Starfleet Logistics:About the Sandbox

Sandboxes should not ordinarily be protected since their purpose is to let new users test and experiment with wiki syntax. Most sandboxes are automatically cleaned every 12 hours, although they are frequently overwritten by other testing users. The Starfleet Logistics:Sandbox is cleaned every hour. Those who use sandboxes for malicious purposes, or to violate policies such as no personal attacks, civility, or 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:

On redirect pages, use the {{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
• Starfleet Logistics:Edit lock
• Starfleet Logistics:List of indefinitely protected pages
• Starfleet Logistics:Requests for page protection
• Starfleet Logistics:Rough guide to semi-protection
• Starfleet Logistics:Make protection requests sparingly, an essay
• m:Protected pages considered harmful
• m:The Wrong Version
• Starfleet Logistics:Protection policy/Padlocks