Bitmap Image
ACC 
Format: /cs acc #room nick
Use the acc command to find out what access level you or another user has to a registered room.
ChanServ will return one of the following values:
7 Identified as founder of the room by the room's password.
6 Identified to the founder's nick.
5 Matches an entry in the access list of the founder's nick.
4 SOP
3 AOP
2 VOP
1 UOP
0 Normal User
-1 AKICKed user
Example:
/cs acc #conferenceroom joeuser

ACCESS 
Format: /cs access #room nick
Use the access command to find out what access level you or another user has to a registered room.
ChanServ will return one of the following values:
7 Identified as founder of the room by the room's password.
6 Identified to the founder's nick.
5 Matches an entry in the access list of the founder's nick.
4 SOP
3 AOP
2 VOP
1 UOP
0 Normal User
-1 AKICKed user
Example:
/cs access #conferenceroom jimmy
This command is useful to determine what level of power someone has in a room. It can only be used by someone who has UOP access or higher. As a UOP or higher, you can use it as a quick way to check whether someone is akicked. This can be useful if they are having problems joining, but you're not sure why. Anyone can use it to check their own access on the room, if the command goes through, you see your access, if it does not you know you are either 0 or -1. Then if you can join you are 0, if you get kicked out after joining, you are akicked. UOPs and higher can also use it to check the access level of another op, if they need an AKICK set, they may want to see if a fellow op is an SOP.

AKICK 
Format: /cs akick #room add|del|list|wipe mask
SOPs and the founder of the room can add and delete AKICKs. If a user matches an entry in your room's akick list, he is immediately kicked and banned from the room. The WIPE command will clear out the entire AKICK list. Only the founder may use the wipe command. UOPs and above may use the list command to see the current AKICKs.
ADD - Add a user to a room's AKICK list.
DEL - Remove a user from a room's AKICK list.
LIST - List the AKICK list entries.
WIPE - Clear all the AKICK list entries
Examples:
/cs akick #support del *!user@domain.com
/cs akick #support wipe
This command is an important part of room security. It allows you to remove troublesome users. It should not be used lightly though, as it will generally require keeping innocent users out as well. Since people online can only be recognized by IP address and most people use dialup connections, all users from a big ISP may look the same. However, UOPs and higher will not be kicked out of the room even if they are akicked.

AOP 
Format: /cs aop #room add|del|list|wipe nick
AOPs have the third level of access in a room. Only an SOP or the founder can add or delete an AOP or wipe the entire list. UOPs or higher can use the list command to see the current AOPs.
ADD - Add a user to a room's AOP list.
DEL - Remove a user from a room's AOP list.
LIST - View the AOP list entries.
WIPE - Remove all AOP list entries.
Examples:
/cs aop #support add theri
/cs aop #support del theri
/cs aop #support wipe
AOPs can always op themselves in a room. They have all of the powers of VOPs (see VOPs below), plus they can change modes or op/voice other people in the room. There are several abilities that can be set to be usable by AOPs, depending on the founder's desires. Most rooms will allow AOPs to send memos to the room. Topics may be locked to AOP or above.
Only people who are trusted should be added to the AOP list. While they do not have the power to do permanent damage, they cannot edit any of the room's lists or settings, they do have the ability to make the room unusable until another AOP is able to fix it. At times an SOP may be needed to sort out conflicts between AOPs.
All ops should be added by nick unless there is a specific need to add them by mask. Adding by nick allows for additional security and grants more privileges. For example, an op added by mask cannot receive memos sent to the room.

AUTH 
Format: /cs auth #room add|del|list|wipe mask
Allows ops to view (VIEW) auth entries pending for the channel; E.g. if I try to add you to #objectivism, and you have "auth on", that command will list you as "pending". SOPs and the founder of the room can add and delete Auth.
ADD - Add a user to a room's AUTH list.
DEL - Remove a user from a room's AUTH list.
LIST - List the AUTH entries.
WIPE - Clear all the AUTH list entries
Examples:
/cs auth #support del mark
/cs auth #support wipe
This command assists you in managing user additions to your room. You can create a request to add someone to your room and see how many of those requests are still pending. If you change your mind you can remove a single user or wipe the entire list.

COUNT 
Format: /cs count #room
This will give a count of how many entries are in each of the room's lists. UOPs and higher can get a count for a room.
Example:
/cs count #webchat
This command is primarily useful to get an idea of how many ops a room has or to see if the akick list is long enough to be worth considering reviewing. Actually listing people on the lists will fill your screen with information, while the count command is just a one line summary.

CS 
Format: /cs command [parameters]
This is an alias which calls to ChanServ. It reduces your amount of typing. Instead of always typing /cs <command|rooml> [parameters], you simply type /cs <command|room> [parameters].
Example:
/cs set #conferenceroom mlock +tn
Most clients will understand /cs, but if you are using one that does not try:
/quote cs <command>
/chanserv also works as an alias, and also may need a quote, depending on the program you use.

DEOP 
Format: /cs deop #room nick
If you are an AOP in a room, you can use services to deop people in the room who do not outrank you..
Example:
/cs deop #support webmaster
This should be used if someone was given ops and is misusing them. If the person is an AOP then if you are an SOP you should delete the entry to prevent them from reopping themselves. You will rarely want to deop someone who has the same status in the room as you do, since they can just reop themselves, and you can start a pointless struggle for control that no one can win. If you have problems with someone who has the same status, find someone of higher status in the room to deal with it. You might want to deop someone of the same status if he/she went away for a time and forgot to deop first.
Note: if you are opped and wish to deop yourself, you still need to be an AOP or higher to do it with services. But you can mode yourself -o in the room.

DEVOICE 
Format: /cs devoice #room nick
You must be a UOP or higher to use this command in the room. This command will remove your (+v) voice status. If you are an AOP or higher you can devoice other people who do not outrank you.
Example:
/cs #spiderslair devoice Jenkins
This command is useful in rooms where voice is used to symbolize some level of ability in the room. Many help rooms will voice helpers who are still in training. If you are voiced but are going to be inactive you cannot simply mode yourself -v in the room, since only ops can set room modes. This command has services remove the voice for you. AOPs and higher can use services to devoice people who do not outrank them, but they can also just mode them -v normally. The services command would be useful if you are an AOP or higher, but not currently opped and want to devoice someone without having to op yourself first.

DROP 
Format: /cs drop #room
Used to drop a registered room. Only the founder can do this.
Example:
/cs drop #conferenceroom
This command should be used when a room is no longer wanted. It drops all of the
information about the room from services' database and makes the room available for registration by someone else. The room will be treated like any other dynamic room until it is registered again.

HELP 
Format: /cs help command command
Display a list of all commands you can get help on.
Examples:
/cs help
/cs help identify
/cs help set topiclock
This is the command to check how to use any command related to chanserv. It is useful to check syntax, or to check which commands are available. The help command will give the list of commands, while help <command> will give more information on a specific command. For commands such as set that have numerous options you will get a list of those options. Then you can use help <command> <option> to get more information on any of these options.

IDENTIFY 
Format: /cs identify #room password
This command is used to gain founder access to a room, level 7 access as shown by the acc and access commands. After identifying to a room, you have complete control over it and can use any of the services commands that relate to room management.
Example:
/cs identify #conferenceroom mypass
This command should be used when you own a room and wish to make changes to its settings. As founder you should not need to identify with the room's password very often. You should be opped based upon your nick, and if need be, identify for your nick. The room won't expire so long as the founder's nick does not and people get opped in the room regularly. If a root sets keep on for the room, then it will not expire from lack of use.

INFO 
Format: /cs info #room
The info command will show you the available information on a room including founder, registration time, room options and more.
Example:
/cs info #conferenceroom
This command is useful when you want to check if a room is registered, or are trying to find out why services are behaving in a particular way. If you want to change the topic, or send a memo, or similar you can use this to see what level those abilities are set to. If services keeps tampering with the modes or is doing anything inexplicable, a check to the room's info may explain why it is acting that way. It's generally a good place to start when troubleshooting.

INVITE 
Format: /cs invite #room
This command is used to invite yourself into a room that is set to invite only. You need to have User (UOP) or higher access in the target room to utilize this command. This command cannot be used to invite others into the room.
Example:
/cs invite #conferenceroom
This command is useful if the room is set +i, because without inviting yourself, you cannot join. To invite others, use the command /invite <nick> <room> while opped in the room. Invite-only rooms allow for some privacy, since people cannot join without the approval of the ops.

MDEOP 
Format: /cs mdeop #room
Used to deop every user in the room including yourself. You must be an AOP or higher in the room to use this command. It will not work if anyone is present who outranks you.
Example:
/cs mdeop #conferenceroom
This is a useful command to regain control in a room if someone has become inappropriately opped. It should not need to be used often.

MKICK 
Format: /cs mkick #room
Used to kick every user out of your room. You must be an AOP or higher in the room to use this command. It will not work if anyone currently in the room outranks you.
Example:
/cs mkick #conferenceroom
This command should not often be needed. But it can reset a room to its default settings by forcing everyone to leave. Every once in a while a room can become desynched, such that services thinks someone is in the room when no one is. Then services do not properly set the topic or modes, because they do not realize they were erased when the room emptied. An mkick will usually fix this.

OP 
Format: /cs op #room nick
If you are an AOP or higher in a room you can use services to op yourself or others. All of the ops in the room will see a notice telling them that you used services to op the person.
Example:
/cs op #conferenceroom webmaster
This is mostly useful when opping yourself. If you deop yourself for whatever reason, you can reop yourself without having to part and rejoin. Opping other people is usually easily done by moding them +o, but occasionally a bot or script will have problems with people opping others, then services can be used to avoid problems.

REGISTER 
Format: /cs register #room password description
Used to register a room with services. After registering your room, you will be able to determine how it is run. You can control who may join and how much power each user has. The room will remain yours so long as your nick does not expire and someone is opped in the room regularly (the exact time period is settable). The room will not expire from lack of use if a root sets held on for it, see the root command section for more information on held. Who may register a room is settable by a root. Some networks will allow any user to register a room while others may restrict it to network operators.
Example:
/cs register #support mypasswd Product Support Room
If you plan to talk to a group of people regularly you should register a room in which to do it. It is important to register a room rather than just using a dynamic room so that you can guarantee it will remain yours. Otherwise you might have to switch rooms, and informing people will be tedious. You can also register a room if there is a topic that interests you, but you're not sure who would want to discuss it. Just register a room with a name that implies that topic, say #baseball, and with time people interested in talking about baseball will be likely to join.

SOP 
Format: /cs sop #room add|del|list|wipe nick
SOps have the second highest level of control in a room. They can add and delete AOPs and AKICKs in addition to all of the AOP commands. The founder is the only one who can add ordelete an SOP. The WIPE command will clear out the entire SOP list. You can delete a user by entering the number value besides his nickname when you do a list on the SOP list for the room.
ADD - Add a user to a room's SOP list.
DEL - Remove a user from a room's SOP list.
LIST - List the SOPs for the room.
WIPE - Clear the SOP list of all entries
Examples:
/cs sop #conferenceroom add Samurai
/cs sop #conferenceroom del Samurai
/cs sop #conferenceroom wipe
/cs sop #conferenceroom list
SOPs should be chosen very carefully since they manage all of the other staff in the room. A room will generally not require a large SOP list. Most of the people who will actually be looking after the room can be AOPs.

UNBAN 
Format: /cs unban #room *|nick|mask
The unban room command with no arguments will cause services to unban you from that room. Unbanning a nick will cause services to unban that nick, and unbanning a mask will remove a ban for that mask. The * is used to remove all bans in the room. AOPs and above can unban themselves, other nicks, and masks, but only SOPs and the founder can use the * to remove all bans.
Examples:
/cs unban #webmaster
/cs unban #services *
/cs unban #webchat mark
/cs unban #conferenceroom *!jennifer@*.webchat.org
The unban command is primarily useful for unbanning yourself. If you are outside the room you cannot remove bans manually. However unbanning a particular nick can be useful if you're not sure how that person is being banned, services will do the work of figuring out how to unban the person. Unbanning all is a convenience, since any op could manually remove the bans, but it might take a lot of work. The command is restricted to SOPs because it is powerful, and if an AOP started manually removing bans, others would likely notice.

UOP 
Format: /cs uop #room add|del|list|wipe nick
UOPs have the fifth highest level of access in a room. Only SOPs or higher may use WIPE, ADD and DEL. UOPs or above may use LIST. UOPs will be moded +u when they join the room. They will be able to receive memos sent to that room, as well as be able to enter even if the room is restricted. UOPs can use count, why, acc, access and see the room's lists. Please note: There is a limit of 250 users that can be added to each list..
ADD - Add a user to a room's UOP list.
DEL - Remove a user from a room's UOP list.
LIST - List the UOPs for a room.
WIPE - Clear the UOP list of all entries.
Examples:
/cs uop #webchat ADD Trab
/cs uop #webchat DEL 2
/cs uop #webchat LIST
/cs uop #webchat WIPE
UserOps do not have much ability in a room. Basically, user ops are a part of the room, but they have no authority. They can enter unless banned, but they cannot change any modes. You might want to add UOPs if you often send memos to the room and you want to include these people in those memos, without giving them much power. You also would want to add UOPs if you wish to set up a restricted room, so you can let them join without giving them power.

VOICE 
Format: /cs voice #room nick
This command will voice (+v) you in the room. You must be a VOP or higher to use this command in the selected room. Much like the op command. You must be an AOP or higher to voice someone else.
Example:
/cs voice #spiderslair Jenkins
This command is mostly useful for voicing yourself in rooms where you are a VOP. When voicing others you would generally just mode them +v, but you can use services if you wish. Being able to voice yourself with services means that you do not need to leave and rejoin the room to be revoiced.

VOP 
Format: /cs vop #room add|del|list|wipe nick
VOPs have the fourth level of access in a room. They will be voiced when they enter the room, and they can always speak in the room.. Only an SOP can add or delete a VOP. The WIPE command will clear out the entire VOP list.
ADD - Add a user to a room's VOP list.
DEL - Remove a user from a room's VOP list.
LIST - List the VOP list entries.
WIPE - Clear the VOP list of all entries.
Examples:
/cs vop #support add theri
/cs vop #support del theri
/cs vop #support WIPE
/cs vop #support list

WHY 
Format: /cs why #room nick
This command allows you to see why a certain user has status in a room. It will tell you what level of access services sees the user as having and why. For example, it might say that someone has AOP access because they identified with the nick password for a particular nick in the AOP list.
Example:
/cs why #conferenceroom Surfin
If someone enters the room and is given access that they should not have, you should always do a why on them. This will determine what problem needs to be fixed. The most common problem for rooms that do not set ident on is that the person happens to match a mask in the access lists for an op's nick.