Help:Permissions: Difference between revisions

(12 intermediate revisions by the same user not shown)

Line 1:

{{Ambox|image=[[File:~~Tux~~.~~svg~~|40px|link=]]|text=~~Anyone with super user privileges on~~ the ~~Endurance Coalition VPS is entitled~~ to ~~all permissions upon request. They are not granted by default as a practical matter~~.}}

{{Ambox|image=[[File:Authenticator.jpg|40px|link=]]|text=[[wikipedia:Multi-factor authentication|'''Multi-factor authentication''']] is required by the software to make use of any permission listed on this page.}}

This wiki has different account permissions to assist in it's administration. Any ~~editor~~ may ~~ask a bureaucrat for~~ any permission. Granting ~~and revoking~~ is at a bureaucrat's discretion.

This wiki has different account permissions to assist in it's administration. Any person with an account may request any permission. Granting of permissions is at EDC leadership and bureaucrat discretion.

== Bureaucrat ==

~~The only people able to adjust permissions are~~ '''~~bureaucrats~~'''~~. They may do so at their discretion. They~~ can ~~also~~ delete ~~revisions~~ in a manner ~~that hides them from~~ even ~~administrators, reserved for getting rid of~~ ''~~personally identifiable~~'' ~~information that is mistakenly published~~.

A '''bureaucrat''' can tie IP addresses to wiki accounts and vice versa, delete material on the wiki in such a manner to where even ''administrators'' cannot see it, and can grant and revoke any permission listed on this page.

The following individuals in the Endurance Coalition are bureaucrats~~. This permission is the most strictly controlled. Anyone with an account may still request it, just odds are higher than normal that it'll be denied~~.

The following individuals in the Endurance Coalition are bureaucrats.

* '''[[User:Sirdog|Sirdog]]''' (sirdog3355)

Line 19:

Usage of the above tools are at administrator discretion (with an expectation of working nicely with others). The actual use of the tools are explained at [[mw:Manual:Administrators|Manual:Administrators]].<ref>The linked page makes assumptions about the permissions administrators have. Some permissions may not be available on this wiki for a variety of reasons.</ref> Administrators should be aware that deletion is not permanent. All pages and files<ref>In the interest of keeping the wiki's overall file size low, sometimes deleted images are pruned on the backend and thus cannot be recovered, so technically not ''all'' images are ''always'' recoverable. But '''pages''' ''are'' always recoverable.</ref> can be [[mw:Help:Deletion and undeletion|undeleted]]. To delete specific revisions, see [[mediawikiwiki:Help:RevisionDelete|Help:RevisionDelete]].

=== ~~Usage~~ guidelines ===

=== Blocking guidelines ===

~~Administrators~~ should ~~never~~ block to ~~punish~~, ~~but to stop an~~ account ~~from disrupting~~ the ~~wiki~~. The account holder may be drunk, having an emotional episode, lashing out in response to some kind of falling out, or the account may be compromised. ~~These are~~ the ~~situations where blocking is appropriate~~. ~~Blocking~~ is ~~performed~~ at ~~[[Special:Block]]~~.

An administrator is ''not'' a moderator; they do not exist to punish. A ''punitive'' block is prohibited unless asked of by EDC leadership (which should be clearly documented in the block reason). Usage of administrator tools are purely to protect and enrich the wiki. In this regard, blocking a wiki account should be because without the block the account will continually be disruptive. The account holder may be drunk, having an emotional episode, lashing out in response to some kind of falling out, or the account may be compromised. In such situations, EDC leadership should be notified and the account blocked. Block length is at the administrator's discretion, though doing so indefinitely until hearing back from EDC leadership is always an option.

When blocking, as best practice, please ensure the following.

* Blocks should always be marked as <code>Sitewide</code>.

* The box <code>Editing their own talk page</code> should always be ticked.

* Blocks should always be given a legible reason.

* Expiration is at administrator discretion. Generally speaking, most of the examples above would warrant an indefinite block (a drunk editor perhaps a day or two, someone emotional perhaps a week; these are recommendations, not rules).

== Interface administrator ==

Line 33:

Line 34:

== Edit filter manager ==

: ''List of edit filter managers available [[Special:ListUsers/edit-filter-manager|here]]''.

An '''edit filter manager''' is able to create and edit filters at [[Special:AbuseFilter]]. They can also view and edit the private filters. The abuse filter is a set of [[wikipedia:Regular expression|regular expression]] patterns that perform certain actions when triggered. This wiki uses filters to prevent certain behaviors which may cause harm. Filters are marked private by edit filter managers at their discretion.

An '''edit filter manager''' is able to create and edit filters at [[Special:AbuseFilter]]. They can also view and edit the private filters. The abuse filter is a set of [[wikipedia:Regular expression|regular expression]] (sometimes called "regex) patterns that perform certain actions when triggered. This wiki uses filters to prevent certain behaviors which may cause harm. Filters are marked private by edit filter managers at their discretion. This permission is not bundled into another permission due to the technical knowledge needed to create, edit, and interpret regex.

== Account specialist ==

Line 49:

Line 50:

At the '''top''' of the page, copy and paste the following:

<pre>

</pre>

~~After <code>name=</code> but before the pipe (<code>|</code>), just write the name they commonly go by. If creating an account for Fleff, you'd just write <code>Fleff</code>.~~ After <code>id=</code> but before the curly brackets (<code>}}</code>), you'll write in their Discord ID.<ref>~~Why do we use~~ Discord IDs~~? Simple. Usernames can be changed. IDs cannot~~.</ref>

After <code>id=</code> but before the curly brackets (<code>}}</code>), you'll write in their Discord ID.<ref>While usernames are unique to the user, they are changeable. Discord IDs are not.</ref>

{{Note|If you want to double check that what you have copied is a Discord ID, you can put it into a website such as [https://discord.id/ Discord Lookup] and see if it gives you the user in question.|type=reminder}}

To get a Discord ID, you need to enable developer mode on Discord (Settings > Advanced > Developer mode), right click the account's name on any message they've sent, and click the button <code>Copy User ID</code>. You will paste this after <code>id=</code>. It should ~~just~~ be a long number. For example, Sirdog's Discord ID is <code>281589411962028034</code>.

To get a Discord ID, you need to [https://discord.com/developers/docs/activities/building-an-activity#step-0-enable-developer-mode enable developer mode] on Discord (Settings > Advanced > Developer mode), right click the account's ''name'' on any message they've sent, and click the button <code>Copy User ID</code>. You will paste this after <code>id=</code>. It should be a long number. For example, Sirdog's Discord ID is <code>281589411962028034</code>.

The following is an example of a properly filled out template.

<pre>

</pre>

After you've done this, save the page. Double check the template doesn't look wonky, then, you are done. Thank you!<ref>Curious minds may wonder why this is enough if anyone can edit user pages. An edit filter stops editors without the bureaucrat or account specialist permissions from messing with the template.</ref>

=== ~~Usage guidelines~~ ===

=== Guidelines ===

* Accounts should only be made for people currently in the Endurance Coalition Discord. ~~If they~~ aren't~~, the person must be redirected to a bureaucrat for an answer~~.

* Accounts should only be made for people currently in the Endurance Coalition Discord. Those who aren't are ineligible.

* Never click <code>Close account</code> in the [[Special:EditAccount]] interface.<ref>~~Nothing ''actually bad'' happens if you do this. It~~ just scrambles the person's password and ~~blanks their~~ email ~~field (which is~~ '~~'already'' blank)~~. ~~But this just creates more work~~ if ~~the user ever wants to, ya know, login and edit. If~~ a user needs to not ~~be allowed~~ to ~~edit ever again~~, ~~then that falls to~~ an administrator (~~using~~ [[Special:Block]]) ~~to enact~~, '''not''' an account specialist~~. A properly setup block will perform essentially the same function~~.</ref>

* Never click <code>Close account</code> in the [[Special:EditAccount]] interface.<ref>This just scrambles the person's password and email. It doesn't do anything crazy or irreversible. However, if a user needs to not edit the wiki due to disruption, an administrator needs to handle it (via [[Special:Block]]), ''not'' an account specialist.</ref>

* To help recover an account, simply use [[Special:EditAccount]] to change the person's password to something random and give it to them. '''Instruct them to change it immediately'''.

** If the person is not in a position to immediately change their password (e.g at work, asleep, etc), and the account specialist ''knows'' this, it is advised the account specialist hold off on changing the password until they can. But this is not a requirement.

** Most of the time, account verification is simple since the Discord account for most users are well known. But if there is even a ''sliver'' of doubt, use '''<nowiki>{{</nowiki>[[Template:Account verified|Account verified]]<nowiki>}}</nowiki>''' to be sure.

** Most of the time, account verification is simple ~~sense~~ the Discord account for most users are well known. But if there is even a ''sliver'' of doubt, use ~~the~~ '''<nowiki>{{</nowiki>[[Template:Account verified|Account verified]]<nowiki>}}</nowiki>''' to be sure.

** If there is even a ''sliver'' of doubt that a '''Discord account''' requesting recovery is compromised, forward the matter to EDC leadership, and do not do anything to the relevant wiki account.

** If there is even a ''sliver'' of doubt that a '''Discord account''' requesting recovery is compromised, forward the matter to an ~~administrator~~.

** If part of account recovery is that the individual has lost access to their 2FA and their recovery codes an EDC <code>@SYS:OP</code> will need to assist them.<ref>This is because a backend maintenance script has to be run to remove someone's 2FA.</ref>

== Footnotes ==

@@ Line 1: / Line 1: @@
-{{Ambox|image=[[File:Tux.svg|40px|link=]]|text=Anyone with super user privileges on the Endurance Coalition VPS is entitled to all permissions upon request. They are not granted by default as a practical matter.}}
+{{Ambox|image=[[File:Authenticator.jpg|40px|link=]]|text=[[wikipedia:Multi-factor authentication|'''Multi-factor authentication''']] is required by the software to make use of any permission listed on this page.}}
-This wiki has different account permissions to assist in it's administration. Any editor may ask a bureaucrat for any permission. Granting and revoking is at a bureaucrat's discretion.
+This wiki has different account permissions to assist in it's administration. Any person with an account may request any permission. Granting of permissions is at EDC leadership and bureaucrat discretion.
 == Bureaucrat ==
-The only people able to adjust permissions are '''bureaucrats'''. They may do so at their discretion. They can also delete revisions in a manner that hides them from even administrators, reserved for getting rid of ''personally identifiable'' information that is mistakenly published.
+A '''bureaucrat''' can tie IP addresses to wiki accounts and vice versa, delete material on the wiki in such a manner to where even ''administrators'' cannot see it, and can grant and revoke any permission listed on this page.
-The following individuals in the Endurance Coalition are bureaucrats. This permission is the most strictly controlled. Anyone with an account may still request it, just odds are higher than normal that it'll be denied.
+The following individuals in the Endurance Coalition are bureaucrats.
 * '''[[User:Sirdog|Sirdog]]''' (sirdog3355)
@@ Line 19: / Line 19: @@
 Usage of the above tools are at administrator discretion (with an expectation of working nicely with others). The actual use of the tools are explained at [[mw:Manual:Administrators|Manual:Administrators]].<ref>The linked page makes assumptions about the permissions administrators have. Some permissions may not be available on this wiki for a variety of reasons.</ref> Administrators should be aware that deletion is not permanent. All pages and files<ref>In the interest of keeping the wiki's overall file size low, sometimes deleted images are pruned on the backend and thus cannot be recovered, so technically not ''all'' images are ''always'' recoverable. But '''pages''' ''are'' always recoverable.</ref> can be [[mw:Help:Deletion and undeletion|undeleted]]. To delete specific revisions, see [[mediawikiwiki:Help:RevisionDelete|Help:RevisionDelete]].
-=== Usage guidelines ===
+=== Blocking guidelines ===
-Administrators should never block to punish, but to stop an account from disrupting the wiki. The account holder may be drunk, having an emotional episode, lashing out in response to some kind of falling out, or the account may be compromised. These are the situations where blocking is appropriate. Blocking is performed at [[Special:Block]].
+An administrator is ''not'' a moderator; they do not exist to punish. A ''punitive'' block is prohibited unless asked of by EDC leadership (which should be clearly documented in the block reason). Usage of administrator tools are purely to protect and enrich the wiki. In this regard, blocking a wiki account should be because without the block the account will continually be disruptive. The account holder may be drunk, having an emotional episode, lashing out in response to some kind of falling out, or the account may be compromised. In such situations, EDC leadership should be notified and the account blocked. Block length is at the administrator's discretion, though doing so indefinitely until hearing back from EDC leadership is always an option.
+When blocking, as best practice, please ensure the following.
 * Blocks should always be marked as <code>Sitewide</code>.
 * The box <code>Editing their own talk page</code> should always be ticked.
 * Blocks should always be given a legible reason.
-* Expiration is at administrator discretion. Generally speaking, most of the examples above would warrant an indefinite block (a drunk editor perhaps a day or two, someone emotional perhaps a week; these are recommendations, not rules).
 == Interface administrator ==
@@ Line 33: / Line 34: @@
 == Edit filter manager ==
 : ''List of edit filter managers available [[Special:ListUsers/edit-filter-manager|here]]''.
-An '''edit filter manager''' is able to create and edit filters at [[Special:AbuseFilter]]. They can also view and edit the private filters. The abuse filter is a set of [[wikipedia:Regular expression|regular expression]] patterns that perform certain actions when triggered. This wiki uses filters to prevent certain behaviors which may cause harm. Filters are marked private by edit filter managers at their discretion.
+An '''edit filter manager''' is able to create and edit filters at [[Special:AbuseFilter]]. They can also view and edit the private filters. The abuse filter is a set of [[wikipedia:Regular expression|regular expression]] (sometimes called "regex) patterns that perform certain actions when triggered. This wiki uses filters to prevent certain behaviors which may cause harm. Filters are marked private by edit filter managers at their discretion. This permission is not bundled into another permission due to the technical knowledge needed to create, edit, and interpret regex.
 == Account specialist ==
@@ Line 49: / Line 50: @@
 At the '''top''' of the page, copy and paste the following:
 <pre>
-{{Account verified|name=|id=}}
+{{Account verified|id=}}
 </pre>
-After <code>name=</code> but before the pipe (<code>|</code>), just write the name they commonly go by. If creating an account for Fleff, you'd just write <code>Fleff</code>. After <code>id=</code> but before the curly brackets (<code>}}</code>), you'll write in their Discord ID.<ref>Why do we use Discord IDs? Simple. Usernames can be changed. IDs cannot.</ref>
+After <code>id=</code> but before the curly brackets (<code>}}</code>), you'll write in their Discord ID.<ref>While usernames are unique to the user, they are changeable. Discord IDs are not.</ref>
+{{Note|If you want to double check that what you have copied is a Discord ID, you can put it into a website such as [https://discord.id/ Discord Lookup] and see if it gives you the user in question.|type=reminder}}
-To get a Discord ID, you need to enable developer mode on Discord (Settings > Advanced > Developer mode), right click the account's name on any message they've sent, and click the button <code>Copy User ID</code>. You will paste this after <code>id=</code>. It should just be a long number. For example, Sirdog's Discord ID is <code>281589411962028034</code>.
+To get a Discord ID, you need to [https://discord.com/developers/docs/activities/building-an-activity#step-0-enable-developer-mode enable developer mode] on Discord (Settings > Advanced > Developer mode), right click the account's ''name'' on any message they've sent, and click the button <code>Copy User ID</code>. You will paste this after <code>id=</code>. It should be a long number. For example, Sirdog's Discord ID is <code>281589411962028034</code>.
 The following is an example of a properly filled out template.
 <pre>
-{{Account verified|name=Sirdog|id=281589411962028034}}
+{{Account verified|id=281589411962028034}}
 </pre>
 After you've done this, save the page. Double check the template doesn't look wonky, then, you are done. Thank you!<ref>Curious minds may wonder why this is enough if anyone can edit user pages. An edit filter stops editors without the bureaucrat or account specialist permissions from messing with the template.</ref>
-=== Usage guidelines ===
+=== Guidelines ===
-* Accounts should only be made for people currently in the Endurance Coalition Discord. If they aren't, the person must be redirected to a bureaucrat for an answer.
+* Accounts should only be made for people currently in the Endurance Coalition Discord. Those who aren't are ineligible.
-* Never click <code>Close account</code> in the [[Special:EditAccount]] interface.<ref>Nothing ''actually bad'' happens if you do this. It just scrambles the person's password and blanks their email field (which is ''already'' blank). But this just creates more work if the user ever wants to, ya know, login and edit. If a user needs to not be allowed to edit ever again, then that falls to an administrator (using [[Special:Block]]) to enact, '''not''' an account specialist. A properly setup block will perform essentially the same function.</ref>
+* Never click <code>Close account</code> in the [[Special:EditAccount]] interface.<ref>This just scrambles the person's password and email. It doesn't do anything crazy or irreversible. However, if a user needs to not edit the wiki due to disruption, an administrator needs to handle it (via [[Special:Block]]), ''not'' an account specialist.</ref>
 * To help recover an account, simply use [[Special:EditAccount]] to change the person's password to something random and give it to them. '''Instruct them to change it immediately'''.
-** If the person is not in a position to immediately change their password (e.g at work, asleep, etc), and the account specialist ''knows'' this, it is advised the account specialist hold off on changing the password until they can. But this is not a requirement.
+** Most of the time, account verification is simple since the Discord account for most users are well known. But if there is even a ''sliver'' of doubt, use '''<nowiki>{{</nowiki>[[Template:Account verified|Account verified]]<nowiki>}}</nowiki>''' to be sure.
-** Most of the time, account verification is simple sense the Discord account for most users are well known. But if there is even a ''sliver'' of doubt, use the '''<nowiki>{{</nowiki>[[Template:Account verified|Account verified]]<nowiki>}}</nowiki>''' to be sure.
+** If there is even a ''sliver'' of doubt that a '''Discord account''' requesting recovery is compromised, forward the matter to EDC leadership, and do not do anything to the relevant wiki account.
-** If there is even a ''sliver'' of doubt that a '''Discord account''' requesting recovery is compromised, forward the matter to an administrator.
+** If part of account recovery is that the individual has lost access to their 2FA and their recovery codes an EDC <code>@SYS:OP</code> will need to assist them.<ref>This is because a backend maintenance script has to be run to remove someone's 2FA.</ref>
 == Footnotes ==