Using Channel & Bot Services
Chanserv lets you own (& operate) a channel, giving your /ACCESS
permissions to other channel operators you have granted them access to have, keeping people who match something on the AKICK
list out of the picture; modes that you can lock into place so not even another operator can change, or just remember the modes and re-set them if the channel goes empty (and disappears) when someone joins it again
Also, when chanserv
is looking after your registered channel, it will remember the list modes too. Setting bans [+b]
/ exceptions [+e]
/ guest list [+I]
Channel List Modes: If someone matches an entry on the +e
list, they will not be affected by a matching ban - but it doesn't override +i [invite only]
.
If a user matches an entry on the guest / invite list +I
then they will be allowed into the channel if it's invite only - but this doesn't override a ban they match also
Managing Access with chanserv
This could be a crude and oversimplified way of dealing with channel access permissions. If you want something more sophisticated and you don't mind learning some extra features chanserv has to offer, Read this user guide section about the /ACCESS command
chanserv maintains an access list (or multiple lists) for each registered channel, which determines who gets operator or voice status and who has what permissions. Rather than handing out ops manually every time someone joins, you can configure chanserv to do it automatically. The traditional way is via the XOP lists (so named for the commands ending in “OP”): VOP, HOP, AOP, SOP, etc
For example, to auto-op a trusted user on join, add them to the AutoOp list (AOP):
/chanserv AOP #YourChannel ADD SomeNick
Now “SomeNick” will receive ops (@) automatically whenever they join your channel. In addition, being on the AOP list typically grants a few extra abilities: they can invite themselves into +i channels, unban themselves if needed, and if the GREET feature is enabled, they can have a personal greeting message displayed on entry. Similarly, you can use:
- /chanserv VOP – to auto-voice users (give + voice on join, ideal for regulars in a moderated channel)
- /chanserv HOP – to auto-halfop users (give %, a mid-tier mod role)
- /chanserv AOP – to auto-op users (give @, full operator status)
- /chanserv SOP – to designate “super-ops” or co-owners (often given & admin or just op with elevated privileges)
You can list the current entries with, for example, /chanserv AOP #YourChannel LIST
(or VOP, SOP, etc.), and remove entries with DEL
. These lists are your primary way to control who has power in the channel even when you’re not around to /op them yourself. Keep them updated – if someone leaves your community, you should remove them so they don’t retain privileges
For fine-grained control, our services support an ACCESS level system or flags system, where you can assign specific flags (permissions) to each user. For instance, one user might only have +v (voice) permission, another might have +o (op) and +b (ban) but not +t (change topic). This can be done with commands like /ACCESS
or /chanserv FLAGS
For most cases, though, the simpler VOP/AOP lists suffice to cover typical roles
Some permissions (like ASSIGN
, OWNER
) are reserved for the channel founder only and cannot be delegated by access level alone. Others like INFO
, SIGNKICK
, and PROTECT
require extremely high levels (9999+) and are only appropriate for trusted admins
Channel Settings via chanserv
Beyond user access, chanserv allows the founder to configure a host of channel options. Use /chanserv SET
to tweak these. Here are some of the most useful settings for channel owners:
- SECURE: Only identified users are recognised. Prevents nick impersonation
- SECUREOPS: Blocks ops for users not on access list
- RESTRICTED: Kicks users not on the access list
- KEEPTOPIC: Remembers topic even when empty
- MLOCK: Forces modes on/off:
/chanserv MODE #channel LOCK ADD +nt-s
- OPNOTICE: Logs notice to ops when chanserv actions are taken
- PEACE: Prevents ops from using chanserv on equal/higher-ranked users
- PRIVATE: Hides channel from
/chanserv LIST
output - FOUNDER: Transfer ownership to another account
- SUCCESSOR: Designates fallback founder if yours disappears
- ENTRYMSG: Sends a custom welcome notice when users join
chanserv offers even more options /chanserv HELP SET
but the ones above are most relevant to maintaining control and security
Using botserv for Automation
botserv allows you to introduce a service bot into your channel – essentially a network-provided bot that can perform moderation tasks and entertainment functions under your direction
To get started, view the list of bots with:
/botserv BOTLIST
Then assign one to your channel:
/botserv ASSIGN #YourChannel BotName
Once assigned, the bot will join your channel and operate based on how you configure it. Key features include:
- GREET: Display nickserv greet messages. Enable with:
/botserv SET GREET #YourChannel ON
- FANTASY: Use in-channel commands like
!op
,!kick
. Enable with:
/botserv SET FANTASY #YourChannel ON
- Kick Modules: Kick for CAPS, FLOOD, REPEAT, COLORS, and BADWORDS:
/botserv KICK CAPS #YourChannel ON
/botserv KICK FLOOD #YourChannel ON
/botserv KICK REPEAT #YourChannel ON
/botserv KICK COLORS #YourChannel ON
/botserv KICK BADWORDS #YourChannel ON
Thresholds can be configured with additional parameters. See /botserv HELP KICK
botserv bots are hosted by the network. You don’t need to run anything yourself – the bot is always online and works in tandem with chanserv to enforce rules and maintain order
Pro Tips
- Audit your access lists regularly. Remove stale ops. Add new trusted users as needed
- Don't over-op. Keep your op team small and sane
- Tune botserv kickers. Prevent unnecessary kicks with sensible thresholds
- Encourage nickserv registration. Many features rely on users being identified