Skip to main content


ACCESS ADD will assign the given user to the given channel role.

Syntax: ACCESS <#channel> ADD


/msg ChanServ ACCESS #atheme ADD stitch helpers


ACCESS DEL will remove all channel access from a given user.

Syntax: ACCESS <#channel> DEL


/msg ChanServ ACCESS #atheme DEL stitch


ACCESS INFO displays what level of access a given user has in a given channel. It will display role, long-form flags and short-form flags along with the last date the user’s access was modified.

Syntax: ACCESS <#channel> INFO


/msg ChanServ ACCESS #atheme INFO nenolod


ACCESS LIST lists all users with channel access and their roles in the channel. It uses fuzzy matching so if a user does not exactly match any role, they will be listed as the closest role they match.

Syntax: ACCESS <#channel> LIST


/msg ChanServ ACCESS #atheme LIST


ACCESS SET will change the given user’s role to the given channel role.

Syntax: ACCESS <#channel> SET


/msg ChanServ ACCESS #atheme SET stitch lowlevel-staff


The AKICK command allows you to maintain channel ban lists. Users on the AKICK list will be automatically kickbanned when they join the channel, removing any matching ban exceptions first. Users with the +r flag are exempt.

Syntax: AKICK <#channel> ADD <nickname|hostmask> [!P|!T ] [reason]

You may also specify a hostmask (nick!user@host) for the AKICK list.

The reason is used when kicking and is visible in AKICK LIST. If the reason contains a ‘|’ character, everything after it does not appear in kick reasons but does appear in AKICK LIST.

If the !P token is specified, the AKICK will never expire (permanent). If the !T token is specified, expiry time must follow, in minutes, hours (“h”), days (“d”) or weeks (“w”).

Syntax: AKICK <#channel> DEL <nickname|hostmask>

This will remove an entry from the AKICK list. Removing an entry will remove any matching channel bans unless the channel is set NOSYNC.

Syntax: AKICK <#channel> LIST

This will list all entries in the AKICK list, including the reason and time left until expiration.


/msg ChanServ AKICK #foo ADD bar you are annoying | private op info

/msg ChanServ AKICK #foo ADD *!*[email protected] !T 5d

/msg ChanServ AKICK #foo DEL bar

/msg ChanServ AKICK #foo LIST


The BAN command allows you to ban a user or hostmask from a channel.

Syntax: BAN <#channel> <nickname|hostmask>


/msg ChanServ BAN #chat carnell

/msg ChanServ BAN #chat !@*


CLEAR AKICKS will remove all AKICK entries, including all access list entries whose only flags are +b, from a channel’s access list.

This command can only be used by users with the +R and +f flags.

Syntax: CLEAR <#channel> AKICKS


/msg ChanServ CLEAR #atheme AKICKS


Clear bans will remove all bans found in a specific channel. If your ircd supports other lists associated with a channel (e.g. ban exceptions), you can clear these by specifying the mode letters. Specify an asterisk to clear all lists.

Syntax: CLEAR <#channel> BANS [types]


/msg ChanServ CLEAR #support BANS

Clears #support ban list. /msg ChanServ CLEAR #support BANS eI

Removes all ban and invite exceptions on #support (if your ircd supports them). /msg ChanServ CLEAR #support BANS *

Clears all lists of #support. /msg ChanServ CLEAR #support BANS +

Shows the possible letters.


CLEAR FLAGS will remove all flags from all users (or groups) with channel access on the channel specified except for users who are channel founders.

This command can only be used by channel founders.

Syntax: CLEAR <#channel> FLAGS


/msg ChanServ CLEAR #atheme FLAGS


Clear users will kick all users out of the channel, except you. The channel will be cycled (recreated) if you are not on it.

If a reason is specified, it will be included in the kick message.

Syntax: CLEAR <#channel> USERS [reason]


/msg ChanServ CLEAR #ChatZone USERS


CLONE copies a channel’s chanacs and metadata to a new channel. Both channels must be registered with ChanServ and you must be founder in the target channel for this command to work.

It will not copy the topic as most people will want that different between the 2 channels.

It will also remove all chanacs (except founders) and metadata of the same type from the target channel.

Syntax: CLONE <#source-channel> <#target-channel>


/msg ChanServ CLONE #funstuff #morefun


CLOSE prevents a channel from being used. Anyone who enters is immediately kickbanned. The channel cannot be dropped and foundership cannot be transferred.

Enabling CLOSE will immediately kick all users from the channel.

Use CLOSE OFF to reopen a channel. While closed, channels will still expire.

Syntax: CLOSE <#channel> ON|OFF [reason]


/msg ChanServ CLOSE #lamers ON spamming

/msg ChanServ CLOSE #spiderslair OFF


This will give a count of how many entries are in each of the channel’s xOP lists and how many entries on the access list do not match a xOP value.

The second line shows how many access entries have each flag.

Syntax: COUNT <#channel>


/msg ChanServ COUNT #oscn


DROP allows you to “unregister” a registered channel.

Once you DROP a channel all of the data associated with it (access lists, etc) are removed and cannot be restored.

See help on SET FOUNDER and FLAGS for transferring a channel to another user.

Syntax: DROP <#channel>


/msg ChanServ DROP #foo


FDROP allows dropping any registered channel, provided it is not set held (see help on HOLD).

Once you FDROP a channel all of the data associated with it (access lists, etc) are removed and cannot be restored.

Syntax: FDROP <#channel>


/msg ChanServ FDROP #foo


The FFLAGS command allows an oper to force a flags change on a channel. The syntax is the same as FLAGS, except that the target and flags changes must be given. Viewing any channel’s access list is done with FLAGS.

Syntax: FFLAGS <#channel> <nickname|hostmask>