Configure permissions on a voice server (TeamSpeak/Mumble)

A voice server’s permissions control who can create channels, kick, ban, move or manage roles. On both TeamSpeak and Mumble, the system relies on groups to which rights are attached.

Cause / The problem

By default, only the Server Admin has all the rights, and everyone else is a Guest. Without intermediate groups (moderator, channel admin), you can’t delegate moderation without handing over everything. And without the “Advanced” permission mode, many options are hidden.

Solution

TeamSpeak 6

1. Enable Advanced mode: Options → Application → Advanced permission mode.
2. Understand the two families of groups:
   • Server Groups: global rights (Server Admin, Normal, Guest) — applied across the whole server.
   • Channel Groups: rights limited to one channel (Channel Admin, Channel Operator).
3. Edit a Server Group: right-click a player → Set Server Group, or open Permissions → Server Groups.
   • Create a Moderator group and grant it i_client_kick_from_server_power, i_client_move_power, b_client_ban_create.
4. Channel Admin: assign the Channel Admin group to a player in a specific channel (right-click → Channel Group → Channel Admin). They will only be able to manage that channel.
5. Per-channel client permissions (Channel Client Permissions): for an exceptional right on a single player in a single channel — e.g. priority speaker b_client_is_priority_speaker.
6. Organize by power: each permission has a grant power and a needed power. For a moderator to be able to kick, their kick_power must be ≥ the kick_needed of the target players.

Mumble

1. Open Server → Configure → ACL (Access Control Lists).
2. Each channel has its own ACL list. The predefined groups are all, auth, admin. Create your own (@mod, @vip).
3. Add an ACL entry: group @mod, rights Write, Move, Mute/Deafen, Kick/Ban as needed.
4. Inherit: check Inherit ACLs from parent so sub-channels inherit the parent channel’s rights.
5. Assign a user to a group via Server → Registered Users: create a registered certificate, then assign it to the group.

On both platforms, always test permissions with a “moderator” test account before going live in production. A permission wrongly assigned to Guest opens the door to everyone.