TeamSpeak 3 Permissions & Groups
Channel Hierarchy, server/channel groups, advanced permissions and row management on TS3 server.
Ready to start your service? Check offers and order online.
View offers and orderTeamSpeak 3 Permissions & Groups
The fine management of permissions TeamSpeak 3 is based on server groups, channel groups and overrides. This guide explains the hierarchy, numerical permission values, row creation (Admin, Modo, Member, VIP) and common errors to avoid.
Key concepts
- Server group, applies globally (Admin, Member...)
- channel group, rights in a specific living room
- Channel admin, managing a trade show without full server rights
- Token / privilege key, assigns a group to the connection
Prerequisite
- Admin access TS3, start & token
- TS3 Client with Admin Server Rights
Create a hierarchy of groups
- Open Permissions → Server Groups
- Duplicate "Server Admin" to create "Admin", "Modo", "Member"
- For each group, adjust permissions (i_client_*, b_channel_*, i_group_* )
- Set group inherit : Member inherits Guest, Modo inherits Member...
- Assign the default group to new customers (Guest → Member after registration)
- Generate tokens per group for Discord/site attribution
b_client_is_sticky, i_needed_modify_power) may block any modification. Keep an emergency Server Admin account.Essential losses
| Action | Standard permission |
|---|---|
| Kick / ban | i_client_kick_from_server, b_client_ban_create |
| Create channels | b_channel_create_child, i_channel_need_create |
| Private channel joiner | i_channel_needed_join, i_channel_need_subscribe |
| Upload icons | i_icon_id, b_icon_manage |
Trade Shows & Channel Permissions
Channels "Staff only": increase i_channel_needed_join_power and give to the Modos a i_join_power sufficient. Channel groups can give temporary access without changing the server group.
Tokens privilege
Generate a token per member staff rather than share a single reusable token. Revoke compromised tokens via Permissions → List tokens.
Audit & debug
Use the TS3 client's "Test permissions" tool on a simulated user before publishing major changes.
Troubleshooting
- insufficient client permissions, modify power too low vs target permission
- Inheritance circle, circular groups, reset legacy
- Guest too many rights, harden Guest group by default