Can edit Changes are visible only to logged-in users until reviewed by a pending changes reviewer or administrator.[γ]
Can edit Changes are visible to everyone if there aren't any unreviewed pending changes. Otherwise, they are visible only to logged-in users until reviewed by a pending changes reviewer or administrator.[γ]
Can edit If there are any unreviewed pending changes, they can only edit the page after reviewing them.[γ]
Infrequently edited pages with high levels of vandalism, BLP violations, edit-warring, or other disruption from unregistered and new users.
↑This table assumes that template editors are also extended confirmed, which is almost always the case for non-bot accounts.
123However, if any unregistered or registered editor reverts all unreviewed pending changes back to the latest accepted version, that revision is automatically accepted and pending changes reviewers and administrators aren't prompted or notified.
↑Only noncontroversial changes or requested changes following an achieved consensus should be performed.
↑Cascade protection extends to all pages that are transcluded onto the protected page, unless the transcluded page is at the same protection level or higher. Cascade protection can only be applied to pages that are fully or office-protected because otherwise it creates a workflow flaw.
↑The interface protection level is automatically set by the MediaWiki software to a specific set of pages, such as pages in the MediaWiki namespace, system-wide CSS and JavaScript pages, and personal CSS and JavaScript pages of other users. It is not a protection level that an administrator can manually apply to any page, nor is it a protection level that can be modified on pages currently under interface protection. Because of this, administrators also cannot cascade-protect pages that are Interface-protected.
↑This form of protection is often also called "salting".
↑Under the default no protection, unregistered and newly registered users can still create talk pages in all namespaces and draft articles in the Draft namespace. For these namespaces, it would therefore be possible for the create protection to only apply to unregistered and newly registered users.
Can edit Changes are only visible to logged-in users until reviewed by a pending changes reviewer or administrator.[γ]
Can edit Changes are visible to everyone if there aren't any unreviewed pending changes. Otherwise, they are only visible to logged-in users until reviewed by a pending changes reviewer or administrator.[γ]
Can edit If there are any unreviewed pending changes, they can only edit the page after reviewing them.[γ]
Infrequently edited pages with high levels of vandalism, BLP violations, edit-warring, or other disruption from unregistered and new users.
↑This table assumes that template editors are also extended confirmed, which is almost always the case for non-bot accounts.
123However, if any unregistered or registered editor reverts all unreviewed pending changes back to the latest accepted version, that revision is automatically accepted and pending changes reviewers and administrators aren't prompted or notified.
↑Only noncontroversial changes or requested changes following an achieved consensus should be performed.
↑Cascade protection extends to all pages that are transcluded onto the protected page, unless the transcluded page is at the same protection level or higher. Cascade protection can only be applied to pages that are fully or office-protected because otherwise it creates a workflow flaw.
↑The interface protection level is automatically set by the MediaWiki software to a specific set of pages, such as pages in the MediaWiki namespace, system-wide CSS and JavaScript pages, and personal CSS and JavaScript pages of other users. It is not a protection level that an administrator can manually apply to any page, nor is it a protection level that can be modified on pages currently under interface protection. Because of this, administrators also cannot cascade-protect pages that are Interface-protected.
↑This form of protection is often also called "salting".
↑Under the default no protection, unregistered and newly registered users can still create talk pages in all namespaces and draft articles in the Draft namespace. For these namespaces, it would therefore be possible for the create protection to only apply to unregistered and newly registered users.
Can edit Changes are visible only to logged-in users until reviewed by a pending changes reviewer or administrator.[γ]
Can edit Changes are visible to everyone if there aren't any unreviewed pending changes. Otherwise, they are visible only to logged-in users until reviewed by a pending changes reviewer or administrator.[γ]
Can edit If there are any unreviewed pending changes, they can only edit the page after reviewing them.[γ]
Infrequently edited pages with high levels of vandalism, BLP violations, edit-warring, or other disruption from unregistered and new users.
Can edit Changes are only visible to logged-in users until reviewed by a pending changes reviewer or administrator.[γ]
Can edit Changes are visible to everyone if there aren't any unreviewed pending changes. Otherwise, they are only visible to logged-in users until reviewed by a pending changes reviewer or administrator.[γ]
Can edit If there are any unreviewed pending changes, they can only edit the page after reviewing them.[γ]
Infrequently edited pages with high levels of vandalism, BLP violations, edit-warring, or other disruption from unregistered and new users.
↑This table assumes that template editors are also extended confirmed, which is almost always the case for non-bot accounts.
123456However, if any unregistered or registered editor reverts all unreviewed pending changes back to the latest accepted version, that revision is automatically accepted and pending changes reviewers and administrators aren't prompted or notified.
↑Only noncontroversial changes or requested changes following an achieved consensus should be performed.
↑Cascade protection extends to all pages that are transcluded onto the protected page, unless the transcluded page is at the same protection level or higher. Cascade protection can only be applied to pages that are fully or office-protected because otherwise it creates a workflow flaw.
12The interface protection level is automatically set by the MediaWiki software to a specific set of pages, such as pages in the MediaWiki namespace, system-wide CSS and JavaScript pages, and personal CSS and JavaScript pages of other users. It is not a protection level that an administrator can manually apply to any page, nor is it a protection level that can be modified on pages currently under interface protection. Because of this, administrators also cannot cascade-protect pages that are Interface-protected.
↑This form of protection is often also called "salting".
12Under the default no protection, unregistered and newly registered users can still create talk pages in all namespaces and draft articles in the Draft namespace. For these namespaces, it would therefore be possible for the create protection to only apply to unregistered and newly registered users.
↑Cascade protection extends to all pages that are transcluded onto the protected page, unless the transcluded page is at the same protection level or higher. Cascade protection can only be applied to pages that are fully or office-protected because otherwise it creates a workflow flaw.