Difference between revisions of "Levels"

From Chat4AllFAQ
Jump to: navigation, search
m (Protected "Levels": Protected against vandalism [edit=sysop:move=sysop])
(Fixed some errors, reworded some sections and reworked the SECURE section.)
Line 1: Line 1:
 
== Levels ==
 
== Levels ==
  
−
The Levels system is an alternative to the [[xOP]] channel access system. This method allows for finer control of various channel features and user rights as opposed to the predefined SOP/AOP/HOP/VOP used in the xOPs system. Read on for the details.
+
The Levels system is an alternative to the [[xOP]] channel access system. This method allows for finer control of various channel features and user rights as opposed to the predefined VOP/HOP/AOP/SOP/ used in the xOPs system. Read on for the details.
  
 
== Syntax and Enabling ==
 
== Syntax and Enabling ==
  
−
First things first, you will have to enable the Levels system on your channel:
+
First things first, you will have to disabled the xOP system to be able to use the Levels system on your channel:
−
   /cs SET #channel XOP off  
+
   /CHANSERV SET #channel XOP off  
−
Your current user access list will be converted into the Levels system automatically. From here on, you will not be able to use the old /cs [sop|aop|hop|vop] #channel add nick to maintain user accesses, unless you switch back to the xOP system (which typically isn't recommended to do).
+
Your current xOP user access list will be converted into the Levels system automatically, following this conversion table:
 +
  xOP -> LEVEL
 +
  -----------
 +
  VOP ->  3
 +
  HOP ->  4
 +
  AOP ->  5
 +
  SOP -> 10
  
−
Now for some basic management commands.
+
From here on, you will not be able to use the old xOP edit commands to maintain user accesses, unless you switch back to the xOP system (which typically isn't recommended to do). So, the following does NOT work anymore:
 +
  /CHANSERV [VOP|HOP|AOP|SOP] #channel ADD nick
 +
Instead you will have to assign an access level instead, using the following command syntax:
 +
  /CHANSERV ACCESS #channel ADD nickname level
 +
For instance, to grant ''aRandomUser'' the equivalent rights of HOP on your channel #testingIsFun, you have to issue the following command:
 +
  /CHANSERV ACCESS #testingIsFun ADD aRandomUser 4
 +
 
 +
=== Basic commands overview ===
 +
Now for some basic access list management commands:
  
 
Viewing the access list:
 
Viewing the access list:
−
   /cs ACCESS #channel list
+
   /CHANSERV ACCESS #channel LIST
  
−
Assigning the nick Person to a specific user level (in this case, the eqivilent to AOP):
+
Adding a '''''registered'''''user to the access list:
 +
  /CHANSERV ACCESS #channel ADD nickname level
 +
For instance, assigning level 5 (the equivalent of AOP) to the user ''DennisOpper'' on channel ''#filmfreaks'':
 +
  /CHANSERV ACCESS #filmfreaks ADD DennisOpper 5
  
−
   /cs ACCESS #channel ADD Person 5
+
See the complete list of possible LEVELS descriptions:
 +
   /CHANSERV HELP LEVELS DESC
  
−
See a rather large list of configurable channel options:
+
See a rather large list of all configurable channel options and their current minimum required levels:
 +
  /CHANSERV LEVELS #channel LIST
 +
This will for instance show:
 +
  KICKME      5
 +
which means you'll need at least level 5 before you can kick yourself. Or you'll see:
 +
  AUTOPROTECT  10
 +
which means that you need at least level 10 before you will automatically get channel-usermode +a (admin/PROTECT).
  
−
  /cs LEVELS #channel LIST
+
A complete list of options is in the [#ChannelOptions Channel Options section].
  
−
Set the user level required for automatic +v on join to 0 (The default user level)
+
==== AutoVoice everyone ====
−
A complete list of options is in the next section.
+
If you want to auto-voice everyone who enters your channel, you can lower the minimum required level for AUTOVOICE to 0 (the default user level)
−
 
+
   /CHANSERV LEVELS #channel SET autovoice 0  
−
   /cs LEVELS #channel SET autovoice 0  
 
  
 
== Channel Options ==
 
== Channel Options ==
−
With the Levels system comes the ability to set what level of user can use a given function or gain a specific channel status. This is the complete list as extracted from '''/cs help levels desc'''
+
With the Levels system comes the ability to set what level of user can use a given function or gain a specific channel status. This is the complete list as extracted from '''/CHANSERV help levels desc'''
 
<p>Notes:<br />
 
<p>Notes:<br />
 
#Casing was added to the option names for readability
 
#Casing was added to the option names for readability
Line 38: Line 61:
 
!scope="col"| Option
 
!scope="col"| Option
 
!scope="col"| Description
 
!scope="col"| Description
−
!scope="col"| Default Level
+
!scope="col"| Default Min.Level
 
|-
 
|-
 
| AutoDeOp
 
| AutoDeOp
−
| Disallow a user operator access, even if someone manually ops with /mode
+
| Disallow a user operator access, even if someone manually ops with /mode #channel +o nickname
 
| -1
 
| -1
 
|-
 
|-
 
| AutoHalfop
 
| AutoHalfop
−
| Automatic halfop (+h) on join (Same effect as /cs hop in xOP)
+
| Automatic halfop (+h) on join (Same effect as /CHANSERV HOP in xOP)
 
| 4
 
| 4
 
|-
 
|-
 
| AutoOp
 
| AutoOp
−
| Automatic op (+o) on join. (Same as /cs aop in xOP)
+
| Automatic op (+o) on join. (Same as /CHANSERV AOP in xOP)
 
| 5
 
| 5
 
|-
 
|-
 
| AutoProtect
 
| AutoProtect
−
| Automatic admin/protected op (+a) on join. (Same as /cs sop in xOP)
+
| Automatic admin/protected op (+a) on join. (Same as /CHANSERV SOP in xOP)
 
| 10
 
| 10
 
|-
 
|-
 
| AutoVoice
 
| AutoVoice
−
| Automatic voice (+v) on join. (Same as /cs vop in xOP)
+
| Automatic voice (+v) on join. (Same as /CHANSERV VOP in xOP)
 
| 3
 
| 3
 
|-
 
|-
Line 65: Line 88:
 
|-
 
|-
 
| SignKick
 
| SignKick
−
| Kick messages done through [[ChanServ]] or a [[Bot|Services Bot]] will not be signed above this number. (This doesn't seem to affect anything for me; further research required)
+
| Kick messages done through [[ChanServ]] or a [[Bot|Services Bot]] will not be signed when the level is equal or above this number if /CHANSERV SET #channel SIGNKICK LEVEL is set.<br /> However, this seems to be broken currently in the Anope services, since it will always sign regardless of level.
 
| Disabled
 
| Disabled
 
|-
 
|-
 
| Acc-List
 
| Acc-List
−
| Permit the viewing of the access list via /cs access #channel list (useful if you want to let people see who your channel staff is)
+
| Permit the viewing of the access list via /CHANSERV access #channel list (useful if you want to let people see who your channel staff is)
 
| 1
 
| 1
 
|-
 
|-
Line 81: Line 104:
 
|-
 
|-
 
| Set
 
| Set
−
| Permit the use of /cs set, except for the FOUNDER and PASSWORD options which remain restricted to the channel founder.
+
| Permit the use of /CHANSERV SET, except for the FOUNDER and PASSWORD options which remain restricted to the channel founder.
 
| Disabled
 
| Disabled
 
|-
 
|-
 
| Ban
 
| Ban
−
| Permit the banning of users via ChanServ's /cs BAN
+
| Permit the banning of users via ChanServ's /CHANSERV BAN
 
| 5
 
| 5
 
|-
 
|-
 
| BanMe
 
| BanMe
−
| Permits you to...ban yourself!
+
| Permits you to...ban yourself! (through /CHANSERV BAN)
 
| 5
 
| 5
 
|-
 
|-
 
| Clear
 
| Clear
−
| Permit the use of the Clear command (/cs clear)
+
| Permit the use of the Clear command (/CHANSERV CLEAR)
 
| Disabled
 
| Disabled
 
|-
 
|-
 
| GetKey
 
| GetKey
−
| Permit a user to get the channel key of a +k channel with /cs GETKEY
+
| Permit a user to get the channel key of a +k channel with /CHANSERV GETKEY
 
| 5
 
| 5
 
|-
 
|-
−
| Halfop
+
| HalfOp
−
| Permit the use of the /cs (de)halfop commands.
+
| Permit the use of the /CHANSERV HALFOP and /CHANSERV DEHALFOP commands on others.
 
| 5
 
| 5
 
|-
 
|-
−
| HalfopMe
+
| HalfOpMe
−
| Permit self-(de)halfop.
+
| Permit the use of /CHANSERV HALFOP and /CHANSERV DEHALFOP on yourself.
 
| 4
 
| 4
 
|-
 
|-
 
| Info
 
| Info
−
| Permit the viewing of the output of all info (/cs info #channel all) instead of basic info only.
+
| Permit the viewing of the output of all info (/CHANSERV INFO #channel ALL) instead of basic info only.
 
| Disabled
 
| Disabled
 
|-
 
|-
 
| Kick
 
| Kick
−
| Permits use of /cs KICK
+
| Permits use of /CHANSERV KICK on others
 
| 5
 
| 5
 
|-
 
|-
 
| KickMe
 
| KickMe
−
| Permits self-kicking
+
| Permits use of /CHANSERV KICK on yourself
 
| 5
 
| 5
 
|-
 
|-
 
| Invite
 
| Invite
−
| Permits the use of /invite
+
| Allows to INVITE yourself in the channel with /CHANSERV INVITE #channel
 
| 5
 
| 5
 
|-
 
|-
 
| OpDeop
 
| OpDeop
−
| Permits use of /cs (de)op
+
| Permits use of /CHANSERV OP and /CHANSERV DEOP on others
 
| 5
 
| 5
 
|-
 
|-
 
| OpDeopMe
 
| OpDeopMe
−
| Permits self-(de)opping
+
| Permits use of /CHANSERV OP and /CHANSERV DEOP on yourself
 
| 5
 
| 5
 
|-
 
|-
 
| Protect
 
| Protect
−
| Permits use of /cs (de)protect
+
| Permits use of /CHANSERV PROTECT and /CHANSERV DEPROTECT on others
 
| Disabled
 
| Disabled
 
|-
 
|-
 
| ProtectMe
 
| ProtectMe
−
| Permits self-(de)protecting
+
| Permits use of /CHANSERV PROTECT and /CHANSERV DEPROTECT on yourself
 
| 10
 
| 10
 
|-
 
|-
Line 145: Line 168:
 
|-
 
|-
 
| Unban
 
| Unban
−
| Permits self-unbanning with /cs unban
+
| Permits removing all bans that would prevent you from entering the channel with /CHANSERV UNBAN #channel
 
| 5
 
| 5
 
|-
 
|-
 
| Voice
 
| Voice
−
| Permits use of /cs (de)voice
+
| Permits use of /CHANSERV VOICE and /CHANSERV DEVOICE on others
 
| 5
 
| 5
 
|-
 
|-
 
| VoiceMe
 
| VoiceMe
−
| Permits self-(de)voicing
+
| Permits use of /CHANSERV VOICE and /CHANSERV DEVOICE on yourself
 
| 3
 
| 3
 
|-
 
|-
 
| Memo
 
| Memo
−
| Permits the reading of channel memos sent to the channel via [[MemoServ]]
+
| Permits the reading of channel memos sent to the channel via [[MemoServ]] (/MEMOSERV READ #channel)
 
| 10
 
| 10
 
|-
 
|-
Line 181: Line 204:
 
|-
 
|-
 
| Say
 
| Say
−
| Permits the use of /bs say and /bs act, to talk through a Services Bot (useless without a bot assigned to your channel)
+
| Permits the use of /BOTSERV SAY and /BOTSERV ACT, to talk through a Services Bot (useless without a bot assigned to your channel)
 
| 5
 
| 5
 
|-
 
|-
Line 188: Line 211:
 
== Additional LEVELS options ==
 
== Additional LEVELS options ==
 
Disable the given option, restricting it to founder only
 
Disable the given option, restricting it to founder only
 +
  /CHANSERV LEVELS #channel DISABLE option
 +
 +
Reset all the levels on options to their default settings (which are shown in the above table):
 +
  /CHANSERV LEVELS #channel RESET
 +
 +
== Additional ACCESS options ==
 +
Delete a user from the access list (this will reset them to level 0)
 +
  /CHANSERV ACCESS #channel DEL nickname
 +
For instance to revoke DennisOpper's access level on channel #filmfreaks, type:
 +
  /CHANSERV ACCESS #filmfreaks DEL DennisOpper
  
−
   /cs LEVELS #channel DISABLE option
+
Note: You may also use the entry number from the LIST command in place of a nick. This will let you provide a list of numbers for mass removal
 +
   /CHANSERV ACCESS #channel DEL 1-3,5,13
 +
You can also first view the list of affected nicknames to be sure you have the right numbers with:
 +
  /CHANSERV ACCESS #channel LIST 1-3,5,13
  
−
Reset all the levels on options to their default settings (which are shown in the above table):
+
Wipe out the entire access list in one go
 +
  /CHANSERV ACCESS #channel CLEAR
  
−
  /cs LEVELS #channel RESET
+
== Other useful options to use in conjunction with LEVELS ==
 +
=== Secure Ops ===
  
−
== Additional ACCESS options ==
+
  /CHANSERV SET #channel SECUREOPS ON
  
−
Delete 'Person' from the access list (this will reset them to level 0)
+
Users who are not on the channel's ACCESS list, will not be allowed chanop status.
  
−
  /cs ACCESS #channel DEL Person
+
=== Secure Channel ===
  
−
Note: You may also use the entry number from the LIST command in place of a nick. This will let you provide a list of numbers for mass removal
+
  /CHANSERV SET #channel SECURE [OFF|ON]
  
−
  /cs ACCESS #channel DEL 1,2,3,13
+
This setting is a tricky one.. /CHANSERV HELP SET SECURE describes it as follows:
 +
  Enables or disables ChanServ's security features for a channel. 
 +
  When SECURE is set, only users who have registered their nicknames with NickServ
 +
  and IDENTIFY'd with their password will be given access to the channel as controlled by the access list.                     
  
−
Wipe out the entire access list in one go
+
However, it does not mention how NickServ's ACCESS and SECURE settings are in effect as well.
  
−
  /cs ACCESS #channel CLEAR
+
For your NickServ account you can add your current hostname to the ACCESS list (/NICKSERV ACCESS ADD *@*.your.host). This will automatically semi-identify you for your nickname if you connect from a host on your NickServ Access list. If your NickServ SECURE setting is OFF (/NICKSERV SET SECURE OFF), it will even grant you access to chanserv commands based on the access level of the nick you are using. But, only when the channel's SECURE setting is set to OFF.
  
−
== Other useful options to use in conjunction with LEVELS ==
+
So, here's a quick overview of what is possible with /CHANSERV SET #channel SECURE OFF:
 +
# Your current hostname appears on the NICKSERV ACCESS list of your current nickname.
 +
# Your current nickname has NICKSERV SECURE set to OFF
 +
# The channel's CHANSERV SECURE setting is set to OFF
 +
# Your nickname is on the channels CHANSERV ACCESS list with a level greater or equal to the OPDEOPME LEVEL
 +
# You '''''can''''' use ''/CHANSERV OP #channel'' now
  
−
=== Restricted channel ===
+
But with /CHANSERV SET #channel SECURE ON:
 +
# Your current hostname appears on the NICKSERV ACCESS list of your current nickname.
 +
# Your current nickname has NICKSERV SECURE set to OFF
 +
# The channel's CHANSERV SECURE setting is set to ON
 +
# Your nickname is on the channels CHANSERV ACCESS list with a level greater or equal to the OPDEOPME LEVEL
 +
# You ''can '''not''''' use ''/CHANSERV OP #channel'' now
  
−
  /cs SET #channel Restricted ON  
+
The only way you can use the CHANSERV commands when ''/CHANSERV SET #channel SECURE ON'' is in effect, is by being identified for your registered nickname through NickServ.
  
−
This option will automatically kick and ban users that have a negative access level upon joining.
 
−
If '''SecureOps''' is also set to ON, anyone '''not''' on the access list will also meet this fate.
 
  
−
=== Secure Channel ===
+
=== Restricted channel ===
  
−
   /cs SET #channel Secure ON  
+
   /CHANSERV SET #channel RESTRICTED ON  
  
−
A 'nicer' method of Restricted, this will only allow users who have '''registered with [[NickServ]]''' AND '''identified to NickServ''' to join the channel, based on the access list
+
This option will automatically kick and ban users that have a negative access level upon joining (in other words, those who are NOT on the CHANSERV ACCESS list).
 +
If '''SecureOps''' is also set to ON, anyone '''not''' on the access list will also meet this fate.

Revision as of 12:50, 26 September 2010

Levels

The Levels system is an alternative to the xOP channel access system. This method allows for finer control of various channel features and user rights as opposed to the predefined VOP/HOP/AOP/SOP/ used in the xOPs system. Read on for the details.

Syntax and Enabling

First things first, you will have to disabled the xOP system to be able to use the Levels system on your channel: 

 /CHANSERV SET #channel XOP off

Your current xOP user access list will be converted into the Levels system automatically, following this conversion table: 

 xOP -> LEVEL
 -----------
 VOP ->  3
 HOP ->  4
 AOP ->  5
 SOP -> 10

From here on, you will not be able to use the old xOP edit commands to maintain user accesses, unless you switch back to the xOP system (which typically isn't recommended to do). So, the following does NOT work anymore: 

 /CHANSERV [VOP|HOP|AOP|SOP] #channel ADD nick

Instead you will have to assign an access level instead, using the following command syntax: 

 /CHANSERV ACCESS #channel ADD nickname level

For instance, to grant aRandomUser the equivalent rights of HOP on your channel #testingIsFun, you have to issue the following command: 

 /CHANSERV ACCESS #testingIsFun ADD aRandomUser 4

Basic commands overview

Now for some basic access list management commands:

Viewing the access list: 

 /CHANSERV ACCESS #channel LIST

Adding a registereduser to the access list: 

 /CHANSERV ACCESS #channel ADD nickname level

For instance, assigning level 5 (the equivalent of AOP) to the user DennisOpper on channel #filmfreaks: 

 /CHANSERV ACCESS #filmfreaks ADD DennisOpper 5

See the complete list of possible LEVELS descriptions: 

 /CHANSERV HELP LEVELS DESC

See a rather large list of all configurable channel options and their current minimum required levels: 

 /CHANSERV LEVELS #channel LIST

This will for instance show: 

 KICKME       5

which means you'll need at least level 5 before you can kick yourself. Or you'll see: 

 AUTOPROTECT  10

which means that you need at least level 10 before you will automatically get channel-usermode +a (admin/PROTECT).

A complete list of options is in the [#ChannelOptions Channel Options section].

AutoVoice everyone

If you want to auto-voice everyone who enters your channel, you can lower the minimum required level for AUTOVOICE to 0 (the default user level) 

 /CHANSERV LEVELS #channel SET autovoice 0

Channel Options

With the Levels system comes the ability to set what level of user can use a given function or gain a specific channel status. This is the complete list as extracted from /CHANSERV help levels desc

Notes:

  1. Casing was added to the option names for readability
  2. 'Disabled' as the default level means 'Restricted to Founder'

User statuses

Option Description Default Min.Level
AutoDeOp Disallow a user operator access, even if someone manually ops with /mode #channel +o nickname -1
AutoHalfop Automatic halfop (+h) on join (Same effect as /CHANSERV HOP in xOP) 4
AutoOp Automatic op (+o) on join. (Same as /CHANSERV AOP in xOP) 5
AutoProtect Automatic admin/protected op (+a) on join. (Same as /CHANSERV SOP in xOP) 10
AutoVoice Automatic voice (+v) on join. (Same as /CHANSERV VOP in xOP) 3
NoJoin Disallowed to join the channel. -2
SignKick Kick messages done through ChanServ or a Services Bot will not be signed when the level is equal or above this number if /CHANSERV SET #channel SIGNKICK LEVEL is set.
However, this seems to be broken currently in the Anope services, since it will always sign regardless of level. 		Disabled
Acc-List Permit the viewing of the access list via /CHANSERV access #channel list (useful if you want to let people see who your channel staff is) 1
Acc-Change Permit the modification of the access list 10
AKick Permit the use of the AKick command. 10
Set Permit the use of /CHANSERV SET, except for the FOUNDER and PASSWORD options which remain restricted to the channel founder. Disabled
Ban Permit the banning of users via ChanServ's /CHANSERV BAN 5
BanMe Permits you to...ban yourself! (through /CHANSERV BAN) 5
Clear Permit the use of the Clear command (/CHANSERV CLEAR) Disabled
GetKey Permit a user to get the channel key of a +k channel with /CHANSERV GETKEY 5
HalfOp Permit the use of the /CHANSERV HALFOP and /CHANSERV DEHALFOP commands on others. 5
HalfOpMe Permit the use of /CHANSERV HALFOP and /CHANSERV DEHALFOP on yourself. 4
Info Permit the viewing of the output of all info (/CHANSERV INFO #channel ALL) instead of basic info only. Disabled
Kick Permits use of /CHANSERV KICK on others 5
KickMe Permits use of /CHANSERV KICK on yourself 5
Invite Allows to INVITE yourself in the channel with /CHANSERV INVITE #channel 5
OpDeop Permits use of /CHANSERV OP and /CHANSERV DEOP on others 5
OpDeopMe Permits use of /CHANSERV OP and /CHANSERV DEOP on yourself 5
Protect Permits use of /CHANSERV PROTECT and /CHANSERV DEPROTECT on others Disabled
ProtectMe Permits use of /CHANSERV PROTECT and /CHANSERV DEPROTECT on yourself 10
Topic Permits changing of the channel topic. Disabled
Unban Permits removing all bans that would prevent you from entering the channel with /CHANSERV UNBAN #channel 5
Voice Permits use of /CHANSERV VOICE and /CHANSERV DEVOICE on others 5
VoiceMe Permits use of /CHANSERV VOICE and /CHANSERV DEVOICE on yourself 3
Memo Permits the reading of channel memos sent to the channel via MemoServ (/MEMOSERV READ #channel) 10
Assign Permits the (un)assigning of a Services Bot Disabled
BadWords Permit the manipulation of the Badwords list of a Services Bot (useless unless you have one assigned to your channel) 10
Fantasia Permit the use of 'fantasy commands', such as !op, !kick, etc. (Proper access is still required for some functions, like user statuses, kicks and bans) 3
Greet Users this level and above will have the greet message they set with NickServ displayed by a Services Bot when they join (useless without a bot assigned to your channel) 5
NoKick Users this level and above will *not* be affected by any bot kick triggers, like flood, badwords, etc 1
Say Permits the use of /BOTSERV SAY and /BOTSERV ACT, to talk through a Services Bot (useless without a bot assigned to your channel) 5

Additional LEVELS options

Disable the given option, restricting it to founder only 

  /CHANSERV LEVELS #channel DISABLE option

Reset all the levels on options to their default settings (which are shown in the above table): 

  /CHANSERV LEVELS #channel RESET

Additional ACCESS options

Delete a user from the access list (this will reset them to level 0) 

  /CHANSERV ACCESS #channel DEL nickname

For instance to revoke DennisOpper's access level on channel #filmfreaks, type: 

 /CHANSERV ACCESS #filmfreaks DEL DennisOpper

Note: You may also use the entry number from the LIST command in place of a nick. This will let you provide a list of numbers for mass removal 

  /CHANSERV ACCESS #channel DEL 1-3,5,13

You can also first view the list of affected nicknames to be sure you have the right numbers with: 

  /CHANSERV ACCESS #channel LIST 1-3,5,13

Wipe out the entire access list in one go 

  /CHANSERV ACCESS #channel CLEAR

Other useful options to use in conjunction with LEVELS

Secure Ops

  /CHANSERV SET #channel SECUREOPS ON

Users who are not on the channel's ACCESS list, will not be allowed chanop status.

Secure Channel

  /CHANSERV SET #channel SECURE [OFF|ON]

This setting is a tricky one.. /CHANSERV HELP SET SECURE describes it as follows: 

 Enables or disables ChanServ's security features for a channel.  
 When SECURE is set, only users who have registered their nicknames with NickServ 
 and IDENTIFY'd with their password will be given access to the channel as controlled by the access list.

However, it does not mention how NickServ's ACCESS and SECURE settings are in effect as well.

For your NickServ account you can add your current hostname to the ACCESS list (/NICKSERV ACCESS ADD *@*.your.host). This will automatically semi-identify you for your nickname if you connect from a host on your NickServ Access list. If your NickServ SECURE setting is OFF (/NICKSERV SET SECURE OFF), it will even grant you access to chanserv commands based on the access level of the nick you are using. But, only when the channel's SECURE setting is set to OFF.

So, here's a quick overview of what is possible with /CHANSERV SET #channel SECURE OFF:

  1. Your current hostname appears on the NICKSERV ACCESS list of your current nickname.
  2. Your current nickname has NICKSERV SECURE set to OFF
  3. The channel's CHANSERV SECURE setting is set to OFF
  4. Your nickname is on the channels CHANSERV ACCESS list with a level greater or equal to the OPDEOPME LEVEL
  5. You can use /CHANSERV OP #channel now

But with /CHANSERV SET #channel SECURE ON:

  1. Your current hostname appears on the NICKSERV ACCESS list of your current nickname.
  2. Your current nickname has NICKSERV SECURE set to OFF
  3. The channel's CHANSERV SECURE setting is set to ON
  4. Your nickname is on the channels CHANSERV ACCESS list with a level greater or equal to the OPDEOPME LEVEL
  5. You can not use /CHANSERV OP #channel now

The only way you can use the CHANSERV commands when /CHANSERV SET #channel SECURE ON is in effect, is by being identified for your registered nickname through NickServ.


Restricted channel

  /CHANSERV SET #channel RESTRICTED ON

This option will automatically kick and ban users that have a negative access level upon joining (in other words, those who are NOT on the CHANSERV ACCESS list). If SecureOps is also set to ON, anyone not on the access list will also meet this fate.

Retrieved from "https://wiki.chat4all.org/index.php?title=Levels&oldid=2104"