- 1 Register
- 2 Identify
- 3 Set
- 4 Sop - Aop - Hop - Vop
- 5 Access
- 6 Levels
- 7 Akick
- 8 Drop
- 9 Ban - Unban
- 10 Clear
- 11 Owner - Deowner
- 12 Protect - Deprotect
- 13 Op - Deop
- 14 Halfop - Dehalfop
- 15 Voice - Devoice
- 16 Getkey
- 17 Invite
- 18 Kick
- 19 Logout
- 20 Topic - Appendtopic
- 21 Info
- 22 Enforce
Note: If you have a specific question, you may find your answer at the ChanServ Frequently Asked Questions page.
Chanserv is a major part of the network services and maintains channel registrations and use. This service generally restricts channel management through a hierarchy system of access: the channel registrar (otherwise known as founder) retains the highest level of power. The founder may set the proper settings via ChanServ to grant certain privileges to other users. Depending on your access or rank, you may or may not be able to set/use all the settings and modes available through ChanServ (depending on the channel's levels).
As a note, the timer to drop the channel will be reset as soon as anyone with access joins the channel. If not, an empty channel will be automatically dropped after 14 days. If anyone without access stays in the channel, the channel won't drop either, though the timer will be not reset. The channel will drop as soon as this person leaves & the channel becomes empty.
Below you will see the navigation bar of settable commands via the user of ChanServ. Each command is in correspondance to "/cs command you see #channel paramaters." Each command is taken into depth, so don't fret if you feel as though you are lost.
Help Video: registering a channel
The register command allows a registered user to register a channel under their current (or grouped) nickname.
The syntax is as follows:
/cs register #channel channelpassword description
/cs register #SwiftChannel SwiftChannelPassword123 Example channel for the Wiki
In order to register a channel, you must be an operator (@) and have a registered nickname.
If you have entered the register command correctly, you should see something similar to this:
[05:02:11 PM] -ChanServ- Channel #SwiftChannel registered under your nickname: SwiftUser
You should also see something such as:
[05:02:11 PM] * ChanServ sets mode: +r [05:02:11 PM] * ChanServ sets mode: +q SwiftUser
Once you have registered a channel, you will now be recognized as the founder when you join, provided your nickname is identified.
Identifying to a channel using the set channel password will give you owner access. You will generally have as much access as the original founder, excluding a few commands such as dropping the channel and changing the channel founder. You must be identified on your nickname in order to identify to a specific channel.
In order to identify to the channel you must type:
/cs id #channel channelpassword
/cs id #SwiftChannel SwiftChannelPassword123
This command is used to change various setting for your channel.
/cs set #channel option parameter
This command allows the current founder of the channel to give the channel to someone else. If you change the founder you will lose all of your control and access unless you have added yourself to the access list first. Do not use this command unless you are certain you want to give away your channel.
/cs set #channel founder nickname
/cs set #SwiftChannel founder SwiftUser2 [11:02:47] -ChanServ- Founder of #SwiftChannel changed to SwiftUser2.
This command is a back up command for the founder. It enables a back up nickname to become founder if the founder's nickname drops.
/cs set #channel successor nickname
/cs set #SwiftChannel successor SwiftUser [11:07:14] -ChanServ- Successor for #SwiftChannel changed to SwiftUser
This command is used to change the channel's password (not a channel key). The only time you will need to use the channel password is when you want to share ownership of a channel.
/cs set #channel password newpassword newpassword
/cs set #SwiftChannel password SwiftChannelPassword111 SwiftChannelPassword111 [11:10:58] -ChanServ- #SwiftChannel password changed.
This command is to change the description of the channel. (Provided with the channel's registercommand.)
/cs set #channel desc descriptiontext
/cs set #SwiftChannel desc Example channel for the Wiki [11:13:22] -ChanServ- Description of #SwiftChannel changed to Example channel for the Wiki.
This command is to associate a website link to your channel, it is not the custom bot command !setsite.
/cs set #channel url weblink-here
/cs set #SwiftChannel url http://swiftirc.net [11:16:30] -ChanServ- URL for #SwiftChannel changed to http://swiftirc.net.
This command associated an email address to your channel, not a command that is used often.
/cs set #channel email email@address
/cs set #SwiftChannel email SwiftEmail@SwiftIRC.net [11:19:05] -ChanServ- E-mail address for #SwiftChannel changed to SwiftEmail@SwiftIRC.net.
You can also unset this command with the command below.
/cs set #channel email
/cs set #SwiftChannel email [11:19:44] -ChanServ- E-mail address for #SwiftChannel unset.
This command allows you to change the entrymsg of your channel. This msg is a notice to everyone that joins your channel. (It can be seen as a second channeltopic.)
/cs set #channel entrymsg text-here
/cs set #SwiftChannel entrymsg Welcome to #SwiftChannel. Please, enjoy yourself! [11:25:11] -ChanServ- Entry message for #SwiftChannel changed.
To remove your entrymsg, type
/cs set #channel entrymsg
This command is used to change the default mask which users are banned from your channel with.
/cs set #channel bantype number
0: ban in the form *!user@host 1: ban in the form *!*user@host 2: ban in the form *!*@host 3: ban in the form *!*user@*.domain
/cs set #SwiftChannel bantype 2 [11:28:44] -ChanServ- Ban type for channel #SwiftChannel is now #2.
This command is used to lock channel modes so they can not be easily changed. See channel modes for more information on each mode.
/cs set #channel mlock +nt
The above command is the default setting of a channel.
If you want your channel set to +s and no one be able to set a key the following command is used.
/cs set #SwiftChannel mlock +nts-k [13:11:19] -ChanServ- Mode lock on channel #SwiftChannel changed to +nrst-k. [13:11:19] * ChanServ sets mode: +s
As the example shows, you can lock a mode on or off in a channel.
This command turns the topic retention on or off. When this is turned on, chanserv will remember the topic even when the channel is empty.
/cs set #channel keeptopic on|off
/cs set #SwiftChannel keeptopic on [13:52:41] -ChanServ- Topic retention option for #SwiftChannel is now ON.
This command is used to turn op-deop notices on or off. If opnotice is turned on, chanserv will send a notice to the channel if /cs op/deop #channel (nick) is used.
/cs set #channel opnotice on|off
/cs set #SwiftChannel opnotice on [13:59:15] -ChanServ- Op-notice option for #SwiftChannel is now ON.
When this option is set, a user can not kick, ban or change the status of another user who has the same or higher access by using the /cs commands.
/cs set #channel peace on|off
/cs set #SwiftChannel peace on [14:45:50] -ChanServ- Peace option for #SwiftChannel is now ON.
This option only allows identified users with positive access to join the channel. Anyone else who tries to join will be kicked and banned by chanserv.
/cs set #channel restricted on|off
/cs set #SwiftChannel restricted on [14:56:59] -ChanServ- Restricted access option for #SwiftChannel is now ON.
This option only allows people identified with their password to receive their access. (By using /ns id password and not /ns access authentication.)
/cs set #channel secure on|off
/cs set #SwiftChannel secure on [15:00:32] -ChanServ- Secure option for #SwiftChannel is now ON.
This option, when enabled, only allows users to be (h)op'ed if they have channel access.
/cs set #channel secureops on|off
/cs set #SwiftChannel secureops on [15:08:10] -ChanServ- Secure ops option for #SwiftChannel is now ON.
We recommend this option is set to on at all times.
This option only allows the real channel founder to drop the channel and change its password or founder. This is turned on by default.
/cs set #channel securefounder on|off
/cs set #SwiftChannel securefounder on [15:33:11] -ChanServ- Secure founder option for #SwiftChannel is now ON.
This option shouldn't be disabled in any regular case and should only be considered using by experienced users.
This option is used to toggle signkick on, off or level. If you use the level setting, users with this level of access or higher in your channel will not have their nickname shown when they use /cs kick.
/cs set #channel signkick on|off|level
/cs set #SwiftChannel signkick on [15:54:01] -ChanServ- Signed kick option for #SwiftChannel is now ON.
Turning this command on will allow no one to change the topic using /topic #channel text-here.
/cs set #channel topiclock on|off
/cs set #SwiftChannel topiclock on [16:12:55] -ChanServ- Topic lock option for #SwiftChannel is now ON.
If you decide you want to use SOP, AOP, HOP, and VOP for your channel access you will need to turn this option on. For more detailed information see here
/cs set #channel xop on|off
/cs set #SwiftChannel xop on [16:20:32 PM] -ChanServ- xOP lists system for #SwiftChannel is now ON.
This changes the way you add channel access. By default, chanserv uses the access level (numbers) system.
Sop - Aop - Hop - Vop
In order to use SOP, AOP, HOP, and VOP, the XOP system first needs to be enabled.
/cs set #channel XOP on
/cs set #SwiftChannel xOP on [06:04:52 PM] -ChanServ- xOP lists system for #SwiftChannel is now ON.
Once the system is enabled, you can add users to the different lists.
This is also known as SuperOP. Users on the SuperOP list can perform the same actions as a user with 10 access.
/cs sop #channel add nickname
/cs sop #SwiftChannel add SwiftUser [06:09:46 PM] -ChanServ- SwiftUser added to #SwiftChannel SOP list.
Also known as AutoOp, a user on the AOP list can perform the same actions as a user with 5 access.
/cs aop #channel add nickname
/cs aop #SwiftChannel add SwiftUser [06:11:46 PM] -ChanServ- SwiftUser added to #SwiftChannel AOP list.
This is known as HalfOp list for the channel. A user on this list has the same abilities as a user with 4 access.
/cs hop #channel add nickname
/cs hop #SwiftChannel add SwiftUser [06:13:46 PM] -ChanServ- SwiftUser added to #SwiftChannel HOP list.
The Voice list for a channel. A user on the VOP list has many of the same powers as a user with 3 access.
/cs vop #channel add nickname
/cs vop #SwiftChannel add SwiftUser [06:14:46 PM] -ChanServ- SwiftUser added to #SwiftChannel VOP list.
Help Video: adding access
Granting user's access is by far one of the most important aspects of owning a channel. By default, anyone with over 10 access may add access to other users with an access level below theirs. It is wise to pick loyal, and trustworthy members when giving out access, many malicious users may misuse this power resulting in problematic situations for yourself and the channel. Users must have a registered nick in order to receive access, and an identified nick in order to receive the appropriate rank.
To add access to a registered user, use:
/cs access #channel add nickname level
Default access levels are as followed:
- -9999 to -2 - No status. User autokicked and banned when joining the channel.
- -1 - No status. These are the users without a registered or identified nickname.
- 0 - No status. These are the users with a registered and identified nickname but without any access in the channel.
- 1 to 2 - No status. Regular user. Used when RESTRICTED is enabled.
- 3 - +Voice
- 4 - %Halfop
- 5 to 9 - @Operator
- 10 to 9999 - @Admin-Op
IRCd "rank" flags as followed:
- Voice - (+v)
- Halfop - (+h)
- Operator - (+o)
- Admin - (+a)
- Owner - (+q)
(other servers may have ~ as the owners mark in the nicklist. But in Swiftirc ~ was removed.)
/cs access #SwiftChannel add SwiftUser 5
(This would give the user nick SwiftUser an access level of 5 and therefore a rank as channel operator.)
There are also other /cs access commands that are listed here. The clear command WILL remove everyone's access from your channel, there is no undo button, once you have typed the command the access list is empty.
/cs access #chan clear
With the command below you can view your channel access list.
/cs access #chan list
With this command you can delete a nickname from your access list.
/cs access #channel del nickname
/cs access #SwiftChannel del SwiftUser
Levels The levels feature allows channel owners to edit default access level requirements for other chanserv commands.
You may use the following command for a list of configurable levels and their descriptions:
/cs help levels desc
You may also view the current channel levels if you are owner access by using:
/cs levels #channel list
/cs levels #SwiftChannel list
You may edit the minimal access requirement for a level to any number between -9999 and 9999. In order to restrict commands to owner access only, you must disable it. In order to set a level you must use:
/cs levels #channel set option level
In order to disable a command and as such restrict it to owner only access, you must use:
/cs levels #channel dis option
You can also reset all channels levels to the defaults, you will need to use:
/cs levels #channel reset
Default cs levels
Note that the levels for AUTODEOP and NOJOIN are maximum levels, while all others are minimum levels.
the level 0 = registered nickname (and identified)
(disabled) = founder only can change (and owners)
For more detailed information about ChanServ levels see here.
|Default cs levels|
|Feature or Function||Default level||Description|
|AUTODEOP||-1||Channel operator status disallowed (does not work on SwiftIRC)|
|AUTOHALFOP||4||Automatic mode +h|
|AUTOOP||5||Automatic mode +o|
|AUTOPROTECT||10||Automatic mode +a|
|AUTOVOICE||3||Automatic mode +v|
|NOJOIN||-2||Not allowed to join channel|
|SIGNKICK||(disabled)||No signed kick when SIGNKICK LEVEL is used|
|ACC-LIST||1||Allowed to view the access list|
|ACC-CHANGE||10||Allowed to modify the access list|
|AKICK||10||Allowed to use AKICK command|
|SET||(disabled)||Allowed to use SET command (not FOUNDER/PASSWORD)|
|BAN||5||Allowed to use BAN command|
|BANME||5||Allowed to ban him/herself|
|CLEAR||(disabled)||Allowed to use CLEAR command|
|GETKEY||5||Allowed to use GETKEY command|
|HALFOP||5||Allowed to use HALFOP/DEHALFOP commands|
|HALFOPME||4||Allowed to (de)halfop him/herself|
|INFO||(disabled)||Allowed to use INFO command with ALL option|
|KICK||5||Allowed to use KICK command|
|KICKME||5||Allowed to kick him/herself|
|INVITE||5||Allowed to use INVITE command|
|OPDEOP||5||Allowed to use OP/DEOP commands|
|OPDEOPME||5||Allowed to (de)op him/herself|
|PROTECT||(disabled)||Allowed to use PROTECT/DEPROTECT commands|
|PROTECTME||10||Allowed to (de)protect him/herself|
|TOPIC||(disabled)||Allowed to use TOPIC command|
|UNBAN||5||Allowed to use UNBAN command|
|VOICE||5||Allowed to use VOICE/DEVOICE commands|
|VOICEME||3||Allowed to (de)voice him/herself|
|MEMO||10||Allowed to list/read channel memos|
|ASSIGN||(disabled)||Allowed to assign/unassign a bot|
|BADWORDS||10||Allowed to use BADWORDS command|
|FANTASIA||3||Allowed to use fantaisist commands|
|GREET||5||Greet message displayed|
|NOKICK||1||Never kicked by the bot's kickers|
|SAY or ACT||(completely disabled on SwiftIRC due to abuse)|
Akick, also known as auto kick, will remove a user or host from the channel constantly. It will kick-ban the user upon joining or residing in the channel at any given point. The only way to exempt yourself or a user from an akick is the channel mode +e (/mode #channel +e nick/hostmask). The default access requirement to add an akick is 10.
In order to place an akick on a user nick or hostmask, you must use:
/cs akick #channel add nick/hostmask (reason)
Adding a reason to the akick is optional; if left blank the default message of "User has been banned from the channel" will appear upon being kick-banned.
/cs akick #SwiftChannel add SwiftUser Auto-kicked for spam.
/cs akick #SwiftChannel add *!*@Swift-D1FF2A60.swiftexample.com Auto-kicked for spam.
To view your channels akick list, you must:
/cs akick #channel list
Please note that you can replace list with view for a similar result; the only difference being that view will show who placed the akick and the date it was placed.
It is also possible to clear all entries from the akick list. This should only be done if you are certain that it is necessary, or you wish to completely remove all akicks. The clear command WILL remove everyone from your akick list.
/cs akick #channel clear
To make an akick always active and prevent the ban from being removed, you can stick it on the akick list. You can only stick a hostmask, not a nickname.
/cs akick #channel stick entry
To unstick an akick that has been previously been stuck use the following command.
/cs akick #channel unstick entry
You may also enforce akicks – This will enforce the channel akick list by removing users who match an akick mask. For more information on enforcing certain settings and modes, visit this part.
/cs akick #channel enforce
The drop command will drop and unregister your channel should you no longer feel the need to own nor manage it. Beware, once a channel is dropped, you will no longer be founder, and all previously set services modes and settings will be cleared. An example of this would be your channel's staff access, edited levels, and akicks.
Once your channel is dropped, any other registered user may register it should they receive op.
In order to drop your channel you must use:
/cs drop #channel
/cs drop #SwiftChannel
Ban - Unban
The ban command will kick-ban a selected user from your channel. If a nick is not given, it will ban yourself. By default this command is restricted for user to users with an access of 5 and above.
In order to ban a residing user in your channel, you must use:
/cs ban #channel nickname (reason)
Just like the akick feature, the reason is not required. Should it be left blank, the default kick message of "Requested" will be used.
/cs ban #SwiftChannel SwiftUser You are not welcome
The unban command will remove a ban that matches your mask from a specified channel. By default, users need 5 access in order to use this command.
In order to remove a matching ban upon yourself from a channel you must use:
/cs unban #channel
/cs unban #SwiftChannel
This command clears various setting from the channel, The syntax for the clear command is
/cs clear #channel item
Modes This command will clear all channel modes that are not locked on the channel by the /cs set #chan mlock command.
/cs clear #channel modes
Bans This command will clear all of the channels ban list.
/cs clear #channel bans
Excepts,Invites This command will clear all of the channels excepts ( where people have added /mode #chan +e nick/host or /mode #chan +I nick/host
/cs clear #channel excepts /cs clear #channel invites
Ops - Hops - Voices This command will remove all +o (channel operator status) or +h (halfop status) or +v (voices) from the channel, but will not kick them.
/cs clear #channel ops /cs clear #channel hops /cs clear #channel voices
Users This command will remove all users from your channel (kick them)
/cs clear #channel users
Owner - Deowner
The owner command will grant owner access (ChanServ and +q wise) to a user assuming that they are the channel founder or otherwise identified through Chanserv. This command is generally used to place +q on yourself after identifying with the channel password or otherwise having your founder status setup.
In order to set yourself as owner access, you must type:
/cs owner #channel
/cs owner #SwiftChannel
Deowner - This command will remove your owner status from ChanServ, likewise to the OWNER command.
/cs deowner #channel
/cs deowner #SwiftChannel
As a founder you can use both commands to change someone else's ownership. Add the nickname of the user at the end of the command to make him owner or remove his owneraccess.
Protect - Deprotect
Protect (+a) will prevent other users from directly kicking or kick-banning a user in your channel. This excludes kicks initiated by a higher access-level user via ChanServ, should the proper settings not be set. By default, users with 10 or more access will gain protection in the channel upon identification and joining. SecureOps must also be turned off in order to place protection on users whom are do not have access, or are unidentified.
Protected users (+a) is generally superior to all other rank modes including +o, +h, and +v. (Operator, Halfop-Operator, and Voice.)
In order to place protection on yourself or others, you must use:
/cs protect #channel (nickname)
Should the nickname field be blank, protection will be set on yourself if you have the correct access level.
/cs protect #SwiftChannel SwiftUser
Deprotect – Likewise to the protect command, this command will remove protection (+a) on a user.
Op - Deop
Op Command to place op (+o) on a certain user or yourself, assuming the other user has access should SecureOps be set. By default, you must have 5+ access in order to use this command.
In order to use the op feature on yourself or others:
/cs op #channel (nickname)
/cs op #SwiftChannel SwiftUser
Should the nickname field be left null, services will attempt to op yourself in the given channel.
Deop Likewise to the OP command, DEOP will deop yourself or a given user. By default, you are required to have at least 5 access in order initiate this command.
In order to deop yourself or others:
/cs deop #channel (nickname)
/cs deop #SwiftChannel SwiftUser
Halfop - Dehalfop
Halfop - The halfop command will place halfop (+h) upon a user via services. The minimum, default access level to use this command upon yourself is 4; To place halfop upon other users, you must have at least 5+ access.
/cs halfop #channel (nickname)
/cs halfop #SwiftChannel SwiftUser
Dehalfop - Likewise to HALFOP, this command will dehalfop or otherwise remove the given (+h) mode previously placed upon a user. In order to use this command, you must have at least 5 access, and to use this upon yourself, at least 4 access.
/cs dehalfop #channel (nickname)
/cs dehalfop #SwiftChannel SwiftUser
Voice - Devoice
Voice The voice command will give a designated user voice or yourself voice, should the nickname parameter be left null. By default, 3+ access is required to use this command, and 5+ for usage upon other users.
/cs voice #channel (nickname)
/cs dehalfop #SwiftChannel SwiftUser
Devoice Likewise to the VOICE command, DEVOICE will devoice yourself or a given user. By default, you are required to have at least 3 access in order initiate this command.
/cs devoice #channel (nickname)
/cs devoice #SwiftChannel SwiftUser
If a channel has had a key set with /mode #chan +k key you can find out what this key is by using the following command, please be aware you will need 5 access ( or higher ) by default to use the getkey command.
/cs getkey #channel
/cs getkey #SwiftChannel -ChanServ- Key for channel #SwiftChannel is SwiftKey123.
Sometimes invite only is set on a channel with /mode #channel +i. You can invite yourself into the channel if you have 5 access (or higher), with this command.
/cs invite #channel
/cs invite #SwiftChannel * ChanServ (email@example.com) invites you to join #SwiftChannel
This command is used to kick a user from the channel using ChanServ. Please be aware you will need 5 access ( or higher ) by default to use this command.
/cs kick #channel nickname reason
/cs kick #SwiftChannel SwiftUser You are kicked!
You may also use the unrealircd command /kick.
If you have given someone your channel password and they have identified as owner with it, you can log them out of owner status with the following command.
/cs logout #channel nickname
/cs logout #SwiftChannel SwiftUser -ChanServ- User SwiftUser has been logged out of channel #SwiftChannel.
Topic - Appendtopic
This command is used to change your channel's topic. Commonly used in conjunction with the /cs set #channel topiclock command.
/cs topic #channel text-here
/cs topic #SwiftChannel Welcome to the example channel of the wiki [16:50:54] * ChanServ changes topic to 'Welcome to the example channel of the wiki'
To unset a topic for a channel you can use
/cs topic #channel
Appendtopic will add more text to the end of a topic that has already been set
/cs appendtopic #channel topictext
/cs appendtopic #SwiftChannel For IRC related questions, /join #help [16:59:01] * ChanServ changes topic to 'Welcome to the example channel of the wiki. For IRC related questions, /join #help'
This command is used to see information about a channel,
/cs info #channel
the response you get will either tell you the channel is not registered or will give you some information about the channels shown in the below examples.
/cs info #SwiftChannel -ChanServ- Channel #SwiftChannel isn't registered.
In the above example the channel #SwiftChannel is not a registered channel.
/cs info #SwiftChannel -ChanServ- Information for channel #SwiftChannel: -ChanServ- Founder: SwiftUser -ChanServ- Description: Example channel for the wiki -ChanServ- Registered: Jul 10 21:31:30 2008 UTC -ChanServ- Last used: Feb 24 15:24:41 2009 UTC -ChanServ- Last topic: Welcome to the example channel of the wiki. For IRC related questions, /join #help -ChanServ- Topic set by: SwiftUser
In the above example you can see the channel founder, the description, when it was registered, last used, the last topic and who set the topic.
There is also a command that you can use for your own channels.
/cs info #SwiftChannel all -ChanServ- Information for channel #SwiftChannel: -ChanServ- Founder: SwiftUser -ChanServ- Description: Example channel for the wiki -ChanServ- Registered: Jul 10 21:31:30 2008 UTC -ChanServ- Last used: Feb 24 15:24:41 2009 UTC -ChanServ- Last topic: Welcome to the example channel of the wiki. For IRC related questions, /join #help -ChanServ- Topic set by: SwiftUser -ChanServ- Ban type: 2 -ChanServ- Options: Topic Retention, OP Notice, Peace, Secure, Secure Founder, Signed kicks, Topic Lock -ChanServ- Mode lock: +nrt
As you can see in the above example it show you the same only a few things added like Ban type, Options and Mode lock. Which are all explained on this page.
ChanServ’s unique ENFORCE command can be used to impose various modes, or settings onto a channel and put the channel in the state of that mode or setting. Enforce is only available for usage by the channel founder, or owner access users.
/cs enforce #channel item
There are several different times that can be enforced: set, secureops, restricted, mode +R, modes
You may enforce all SET options such as secureops, restricted if they're already set on the channel but not being executed correctly via
/cs enforce #channel set
For more information on SET commands, visit this page.
You may enforce secureops specifically to deop/dehalfop any users that do not have the correct access, even if it's not set on the channel via
/cs enforce #channel secureops
You may enforce restricted specifically to remove any users without access from the channel, even if it's not set on the channel via
/cs enforce #channel restricted
If mode +R is set on the channel and you wish to enforce it, you have 2 options. You either enforce via MODES or you enforce via +R
When enforcing mode +R via MODES, you will kick all unidentified nicknames from your channel.
/cs enforce #channel modes
When enforcing mode +R via +R, you will kickban all unidentified nicknames from your channel. Mode +R doesn't have to be currently enabled on the channel.
/cs enforce #channel +R
There is also an option to enforce akicks, visit this.