Staff:Override Guide

Revision as of 22:32, 6 November 2008

In This Guide:

1 READ FIRST!

2 Acceptable Overrides

3 Unacceptable Overrides

3.1 Topic Changes

3.2 Userlist Changes

3.3 Banlist Changes

READ FIRST!

Any time you are helping in #Support, or as a Network Helper with security-overide (god-mode) enabled, you possess the ability to override channel security in certain channels. This access is NOT granted for you to become all-powerful and start circumventing channel security. All overrides must be related to official support business, and must follow certain guidelines, as detailed in the guide below.

Acceptable Overrides

The following are acceptable uses of security-override (god-mode):

Any staff commands (on official Support duty only) which require override to be enabled.

PEEK

This may be used to monitor channels on your watch list.

SET

This may be used to view channel settings when helping the channel's owner. NEVER use this override to change any settings. There is only one exception to this rule, which is detailed below.
The only setting that you may change via override is ENFTOPIC. This is done ONLY in the case of channels registered to the *DareNET account where the owner (499) requests assistance in setting the TOPICMASK. DO NOT set the TOPICMASK for them, only adjust the ENFTOPIC level to allow them to set the TOPICMASK as they wish.

GIVEOWNERSHIP

This command may be used when all users with higher access than the requesting users have been gone for four (4) weeks or more, and the owner is not marked as on vacation.

NOTE: If the user is not on the userlist, you may NOT override to add the user to the userlist prior to a .giveownership command. Instead, you should use the form: .giveownership <channel> <user> FORCE, which will automatically add the user to the userlist.

SUSPEND

When there has been a suspected takeover of a channel, you may .suspend the offending user(s), NOT the channel itself. You should then immediately seek a support operator to sort things out. This is very rare, so think twice before doing it.

Unacceptable Overrides

The following overrides are unacceptable at any time. Override access is constantly monitored, so please use extreme caution any time ou have "god-mode" enabled, and always think twice about what you are about to do, before you do it. Should you accedentially perform and override that you know will cause suspicion, contact the Abuse Team and reverse the change (or find someone of higher rank who can do so for you) immediately.

Topic Changes

If a topic violates the AUP or Registration Guidelines, contact a support operator. They will investigate the matter, and take action if necessary. Also, please do not use .topic <channel> to view a channel's topic, as it will force the topic to revert to its DefaultTopic setting should the current topic not be the default topic. To view a channel's topic, use .peek <channel> (see above) or /topic <channel>.

Userlist Changes

You are NEVER to add, remove or change access for any user in any channel which you do not have the appropriate access to do so yourself without override. We cannot stress this enough. Doing so will cause you to lose access to "god-mode."

The only exception to this, is in the case where a channel is registered to the *DareNET account. In such cases, you must add the requesting user at level 499.

You may not add a user to the userlist (at any level) before a .giveownership command if the user is not already on the userlist. Instead, follow the method described above under acceptable overrides.

If a situation similar to the one described below in Banlist Changes arises, which involves a user who is currently on the channel's userlist, follow the instructions provided below, and/or (as appropriate) those descrived in the SUSPEND section above, under acceptable overrides. Under no circumstances will you be justified in deleting a user from the userlist of a channel.

Banlist Changes

DO NOT .addban (including timed bans) any user from a channel in which you do not have appropriate access without security-override. Likewise, do not remove any bans from the channel's ban list if you do not have access to do so.

You should always attempt to contact a support operator for cases that you feel might require a staff member to intervene and remove a user from a channel (e.g. no channel operators are available). If (and only if) you have made a reasonable attempt to contact a support operator and none have responded, and the issue at hand is a matter of channel security or an AUP violation, a network helper (+H) may use the .kickban command to temporarily remove the user from the channel, so long as the ban is not added to the channel's lamers list.

In all such cases, you should leave the channel owner a memo explaining the reason for the override, and let them know they can contact you if they have any further questions. These kinds of situations should not occur often, and as such, all cases will be throughly investigated, so please, please, do not do it if you do not have to.

@@ Line 1: / Line 1: @@
-Any time you are helping in #support, or as a Network Helper with "god-mode" enabled, you possess the ability to override channel security in certain channels. This access is not granted for you to become all-powerful and start circumventing channel security. All overrides must be related to official Support business, and must follow certain guidelines, as detailed below.
+{{Headerbox_blue
+| text = '''<h3>READ FIRST!</h3>'''
+Any time you are helping in #Support, or as a Network Helper with security-overide (god-mode) enabled, you possess the ability to override channel security in certain channels. This access is NOT granted for you to become all-powerful and start circumventing channel security. '''All overrides must be related to official support business''', and must follow certain guidelines, as detailed in the guide below.
+}}
 == Acceptable Overrides ==
-* Any staff commands (on official Support duty) which require override to be enabled.
+The following are acceptable uses of security-override (god-mode):
+* Any staff commands (on official Support duty only) which require override to be enabled.
 '''PEEK'''
@@ Line 9: / Line 15: @@
 '''SET'''
-*This may be used to view channel settings when helping the channel's owner. Do not use this override to change settings.
+* This may be used to view channel settings when helping the channel's owner. NEVER use this override to change any settings. There is only one exception to this rule, which is detailed below.
-*The only setting that you may change via override is ENFTOPIC. This is done only in the case of channels registered to *DareNET where the owner (499) requests assistance in setting the topicmask. Do not set the topicmask for them, only adjust the enftopic level to allow them to set the topicmask as they wish.
+* The only setting that you may change via override is ENFTOPIC. This is done ONLY in the case of channels registered to the '''<code>*DareNET</code>''' account where the owner (499) requests assistance in setting the TOPICMASK. DO NOT set the TOPICMASK for them, only adjust the ENFTOPIC level to allow them to set the TOPICMASK as they wish.
 '''GIVEOWNERSHIP'''
-*This command may be used when all users with higher access than the requesting user are gone 4 weeks or more, and the owner is not on vacation.
+* This command may be used when all users with higher access than the requesting users have been gone for four (4) weeks or more, and the owner is not marked as on vacation.
-*Alternatively, if a user can prove that they are the leader of the organization the channel is for (not just sharing the same name - it must be the SAME organization) you may transfer ownership to the user. If they do not have access in the channel, make sure to make that known in staff note.
-*Note that if the user is not on the userlist, you may NOT override to add the user to the userlist prior to a !giveownership command. You should use the form: !giveownership <#channel> <user> FORCE, which will automatically add the user to the userlist.
+NOTE: If the user is not on the userlist, you may NOT override to add the user to the userlist prior to a <code>.giveownership</code> command. Instead, you should use the form: <code>.giveownership <channel> <user> FORCE</code>, which will automatically add the user to the userlist.
 '''SUSPEND'''
-*Where there is a suspected channel takeover, you may !suspend the offending user(s) (NOT the channel) and immediately seek a support operator to sort things out. This is very rare. Think twice before doing it.
+* When there has been a suspected takeover of a channel, you may <code>.suspend</code> the offending user(s), NOT the channel itself. You should then immediately seek a support operator to sort things out. This is very rare, so think twice before doing it.
 == Unacceptable Overrides ==
-The following overrides are unacceptable at any time, and will be thoroughly investigated. Override access is constantly monitored, so please always use extreme caution any time you have god-mode enabled, and always think twice about what you are about to do, before you do it. If you accidentally perform an override that you know will cause suspicion, you should contact the Abuse Team and reverse the change (or find someone of higher rank to do so for you) immediately.
+The following overrides are unacceptable at any time. Override access is constantly monitored, so please use extreme caution any time ou have "god-mode" enabled, and always think twice about what you are about to do, before you do it. Should you accedentially perform and override that you know will cause suspicion, contact the Abuse Team and reverse the change (or find someone of higher rank who can do so for you) immediately.
+=== Topic Changes ===
+If a topic violates the AUP or Registration Guidelines, contact a support operator. They will investigate the matter, and take action if necessary. Also, please do not use <code>.topic <channel></code> to view a channel's topic, as it will force the topic to revert to its DefaultTopic setting should the current topic not be the default topic. To view a channel's topic, use <code>.peek <channel></code> (see above) or <code>/topic <channel></code>.
+=== Userlist Changes ===
+You are NEVER to add, remove or change access for any user in any channel which you do not have the appropriate access to do so yourself without override. We cannot stress this enough. Doing so will cause you to lose access to "god-mode."
+The only exception to this, is in the case where a channel is registered to the *DareNET account. In such cases, you must add the requesting user at level 499.
+You may not add a user to the userlist (at any level) before a <code>.giveownership</code> command if the user is not already on the userlist. Instead, follow the method described above under acceptable overrides.
+If a situation similar to the one described below in ''Banlist Changes'' arises, which involves a user who is currently on the channel's userlist, follow the instructions provided below, and/or (as appropriate) those descrived in the ''SUSPEND'' section above, under acceptable overrides. Under no circumstances will you be justified in deleting a user from the userlist of a channel.
+=== Banlist Changes ===
-'''Topic changes'''
+DO NOT <code>.addban</code> (including timed bans) any user from a channel in which you do not have appropriate access without security-override. Likewise, do not remove any bans from the channel's ban list if you do not have access to do so.
-*Seek a support operator, even if the topic violates the AUP, TOS, or Registration Guidelines. Note, this includes using !topic <#channel> to view the current topic! Using !topic <#channel> will force the topic to revert to its DefaultTopic setting, in the event that the current topic is not the default, which WILL be considered an unacceptable override. To view the channel's topic, you should use peek instead (see above).
-'''Userlist changes'''
+You should always attempt to contact a support operator for cases that you feel might require a staff member to intervene and remove a user from a channel (e.g. no channel operators are available). If (and only if) you have made a reasonable attempt to contact a support operator and none have responded, and the issue at hand is a matter of channel security or an AUP violation, a network helper (+H) may use the <code>.kickban</code> command to temporarily remove the user from the channel, so long as the ban is not added to the channel's lamers list.
-*You are NOT to add, remove, or change access for any user in any channel in which you do not have the appropriate access to do so. The only exception to this, is in the case where a channel is registered to *DareNET, and you must add the requesting user at level 499. You may NOT add a user to the userlist (at any level) before a !giveownership command if the user is not already on the userlist (see above for an explanation of how to handle this situation).
-*If a situation similar to one described below in the Banlist changes section arises, which involves a user who is currently on the channel's userlist, follow the guidelines described below and/or (as appropriate) those described in the !suspend section above. Under no circumstances will you be justified in deleting the user from the userlist.
-'''Banlist changes'''
+In all such cases, you should leave the channel owner a memo explaining the reason for the override, and let them know they can contact you if they have any further questions. These kinds of situations should not occur often, and as such, all cases will be throughly investigated, so please, please, do not do it if you do not have to.
-*Do not addban (including timed bans) any user from a channel in which you do not have appropriate access. Likewise, do not remove any bans from the channel's ban list if you do not have access to do so. You should always attempt to contact a Support Operator for cases that you feel might require a staff member to intervene and remove a user from a channel (such as, if no channel ops are available). If (and only if) you have made a reasonable attempt to contact an oper and none has responded, and if the issue at hand is a matter of channel security or an AUP violation, a network helper (+H) may use the KICKBAN command to temporarily remove the user from the channel, so long as the ban does not get added to the channel's ban list (that is, ADDBAN or ADDTIMEDBAN/!tb). A reasonable attempt should be made to contact the channel owner and explain the reason for the override. This kind of situation should not occur often, and as such, all cases will be thoroughly investigated, so please, please, do not do it if you don't have to!
 [[Category:Staff Documentation]]