Help:Permissions: Difference between revisions

(8 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.

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 ==

A '''bureaucrat''' can ~~review~~ IP addresses ~~used~~ to ~~access~~ wiki accounts ~~(reserved for investigating a user account being compromised)~~, delete material on the wiki in such a manner to where even administrators cannot see it ~~(reserved for ''personally identifiable'' information)~~, and can grant and revoke any permission listed on this page.

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.

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>

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>.

{{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 [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>

Line 67:

Line 69:

* 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'''.

** 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 '''<nowiki>{{</nowiki>[[Template:Account verified|Account verified]]<nowiki>}}</nowiki>''' to be sure.

** 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.

** 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 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.

** 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.
+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 ==
-A '''bureaucrat''' can review IP addresses used to access wiki accounts (reserved for investigating a user account being compromised), delete material on the wiki in such a manner to where even administrators cannot see it (reserved for ''personally identifiable'' information), and can grant and revoke any permission listed on this page.
+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.
@@ Line 50: / 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>
-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>.
+{{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 [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>
@@ Line 67: / Line 69: @@
 * 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'''.
-** 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 '''<nowiki>{{</nowiki>[[Template:Account verified|Account verified]]<nowiki>}}</nowiki>''' to be sure.
+** 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.
 ** 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 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.
+** 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 ==