CheckUser policy: Difference between revisions

(3 intermediate revisions by the same user not shown)

Line 1:

{{ombox|text=Use of the CheckUser tool must also comply with the [[Policy:Privacy Policy|Privacy Policy]]. In case of conflict between this policy and the Privacy Policy, the Privacy Policy takes precedence.}}

'''CheckUser''' is a tool available to [[Stewards]] and to [[#~~Access to the CheckUser tool~~|certain local administrators]] (called "checkusers"). The tool may be used to reveal the IP addresses associated with a registered account, as well as other technical data about accounts and IP addresses.

'''CheckUser''' is a tool available to [[Stewards]] and to [[#Local checkusers|certain local administrators]] (called "checkusers"). The tool may be used to reveal the IP addresses associated with a registered account, as well as other technical data about accounts and IP addresses.

== Use of the tool ==

Line 24:

When in doubt, checkusers should provide as little information as possible. Explicit statements such as "User A is connecting from IP address 127.0.0.1" are rarely necessary and should be avoided.

== ~~Access to the~~ CheckUser ~~tool~~ ==

== CheckUser access ==

=== Stewards ===

[[Stewards]] are the primary users with access to the CheckUser tool. Stewards are granted CheckUser access on the WickedGov [https://login.wickedgov.org/w Login Wiki]. This allows them to view CheckUser data for log-in and logout actions across all projects.

Line 42:

=== Local checkusers ===

~~The local checkuser group~~ may be ~~granted and removed by Stewards only. Temporary CheckUser access will not be granted~~, ~~except for Stewards.~~

Sometimes, checkusers may be appointed on individual wikis, subject to the following rules:

According to local policies, local checkusers may be appointed ~~based on~~ either local consensus or a local Arbitration Committee or similar body.

* The local checkuser flag may be granted and removed by Stewards only.

* Temporary CheckUser access will not be granted,<ref>This applies to the technical flag only. Notwithstanding this policy, local communities may create periodic review and confirmation processes for checkusers.</ref> except for Stewards.

* According to local policies, local checkusers may be appointed either by local consensus or by a local Arbitration Committee or similar body.

* All users applying for local CheckUser access must either be (a) a local administrator or (b) a member of a local Arbitration Committee or similar body.

* All checkusers must have [[Help:2FA|two-factor authentication]] enabled.

* On any wiki, there must be at least two users with CheckUser access, or none at all. This is so that they can mutually control and confirm their actions. In the case where only one checkuser is left on a wiki (when the only other one retires or is removed), the community must appoint a new checkuser immediately (so that the number of checkusers is at least two). If the community does not do so, the remaining checkuser shall also have access removed.

* The wiki must be large enough to require local checkusers. Stewards will make the final determination of this point based on criteria including the size of the community and the frequency of checks being necessary.

* There must be broad consensus for the appointment with numerous users participating. In cases of appointments by arbitration committees, the election of arbitrators must have been well-attended.

~~All users applying for local CheckUser access must either be (a) a local administrator or (b) a member of a local Arbitration Committee or similar body.~~

== Notes ==

On any wiki, there must be at least two users with CheckUser access, or none at all. This is so that they can mutually control and confirm their actions. In the case where only one checkuser is left on a wiki (when the only other one retires or is removed), the community must appoint a new checkuser immediately (so that the number of checkusers is at least two). If the community does not do so, the remaining checkuser shall also have access removed.

@@ Line 1: / Line 1: @@
 {{global policy}}
 {{ombox|text=Use of the CheckUser tool must also comply with the [[Policy:Privacy Policy|Privacy Policy]]. In case of conflict between this policy and the Privacy Policy, the Privacy Policy takes precedence.}}
-'''CheckUser''' is a tool available to [[Stewards]] and to [[#Access to the CheckUser tool|certain local administrators]] (called "checkusers"). The tool may be used to reveal the IP addresses associated with a registered account, as well as other technical data about accounts and IP addresses.
+'''CheckUser''' is a tool available to [[Stewards]] and to [[#Local checkusers|certain local administrators]] (called "checkusers"). The tool may be used to reveal the IP addresses associated with a registered account, as well as other technical data about accounts and IP addresses.
 == Use of the tool ==
@@ Line 24: / Line 24: @@
 When in doubt, checkusers should provide as little information as possible. Explicit statements such as "User A is connecting from IP address 127.0.0.1" are rarely necessary and should be avoided.
-== Access to the CheckUser tool ==
+== CheckUser access ==
 === Stewards ===
 [[Stewards]] are the primary users with access to the CheckUser tool. Stewards are granted CheckUser access on the WickedGov [https://login.wickedgov.org/w Login Wiki]. This allows them to view CheckUser data for log-in and logout actions across all projects.
@@ Line 42: / Line 42: @@
 === Local checkusers ===
-The local checkuser group may be granted and removed by Stewards only. Temporary CheckUser access will not be granted, except for Stewards.
+Sometimes, checkusers may be appointed on individual wikis, subject to the following rules:
-According to local policies, local checkusers may be appointed based on either local consensus or a local Arbitration Committee or similar body.
+* The local checkuser flag may be granted and removed by Stewards only.
+* Temporary CheckUser access will not be granted,<ref>This applies to the technical flag only. Notwithstanding this policy, local communities may create periodic review and confirmation processes for checkusers.</ref>  except for Stewards.
+* According to local policies, local checkusers may be appointed  either by local consensus or by a local Arbitration Committee or similar body.
+* All users applying for local CheckUser access must either be (a) a local administrator or (b) a member of a local Arbitration Committee or similar body.
+* All checkusers must have [[Help:2FA|two-factor authentication]] enabled.
+* On any wiki, there must be at least two users with CheckUser access, or none at all. This is so that they can mutually control and confirm their actions. In the case where only one checkuser is left on a wiki (when the only other one retires or is removed), the community must appoint a new checkuser immediately (so that the number of checkusers is at least two). If the community does not do so, the remaining checkuser shall also have access removed.
+* The wiki must be large enough to require local checkusers. Stewards will make the final determination of this point based on criteria including the size of the community and the frequency of checks being necessary.
+* There must be broad consensus for the appointment with numerous users participating. In cases of appointments by arbitration committees, the election of arbitrators must have been well-attended.
-All users applying for local CheckUser access must either be (a) a local administrator or (b) a member of a local Arbitration Committee or similar body.
+== Notes ==
+<references/>
-On any wiki, there must be at least two users with CheckUser access, or none at all. This is so that they can mutually control and confirm their actions. In the case where only one checkuser is left on a wiki (when the only other one retires or is removed), the community must appoint a new checkuser immediately (so that the number of checkusers is at least two). If the community does not do so, the remaining checkuser shall also have access removed.