Set Up TeamSpeak 3 Permissions and Groups

If you want to set up TeamSpeak permissions cleanly, do not start with individual checkboxes, but with a role model. Server groups control global privileges, channel groups only apply in specific channels, and direct client permissions remain the exception. Power and needed-power values are also crucial because they define who may perform actions against whom.

Requirements

You need server admin permissions on your TeamSpeak 3 server and access to the TeamSpeak client with visible permission management. After a fresh TS3 installation, according to the official TeamSpeak help, you receive a server admin token that you can redeem in the client under Permissions → Use Token: Documentation at support.teamspeak.com

For the actual permission work, you should also prepare a short role list: Who administers the server? Who moderates conversations? Who may create channels? Who should only listen or speak only after approval? If you run multiple game server communities, a consistent pattern is worthwhile. You can find suitable examples in our guide to Rent and Set Up a Minecraft Server and in the Rent and Set Up a Rust Server Guide, because community structures and moderation should also be clarified early there.

Understand the Permission System

TeamSpeak has a powerful permission system with three levels:

1. Server groups (global)
2. Channel groups (per channel)
3. Client permissions (per user)

Server groups are the normal case. They define what a user is generally allowed to do on the server: speak, write, see channels, move users, kick, ban, or manage groups. Channel groups extend the model where a user only needs additional permissions in a specific channel. You should use direct client permissions sparingly because they are harder to understand later.

The official TeamSpeak documentation also describes the separation between server groups and channel groups as well as the permission types Boolean, Integer, and Power: Documentation at support.teamspeak.com

Standard Server Groups

A practical starting point is four groups. The following values are a clear example, not a universal required configuration:

For game-serverhosting as paid multi-game hosting, the separation is especially important: You want to retain technical control, make support cases traceable, and keep changes to server operation transparent. So not every regular user should get administrative permissions. A clear model with a few admins, several moderators, and a normal member group is better.

Create a New Group

1. Right-click the server → Server Groups
2. "Add Group" → enter name
3. Set permissions

In practice, it is often cleaner to copy an existing default group and then reduce it or expand it selectively. This helps you avoid missing important basic permissions. Name groups clearly, for example Server Admin, Moderator, Member, Guest, and optionally Event Host or Clan Lead. Avoid fantasy names for technical roles if several people administer the server.

Important Permissions

You should check the following permissions from the initial model especially carefully:

i_group_needed_modify_power     # Who may change this group
i_group_needed_member_add_power # Who may add members
b_client_kick_from_server       # Kick players from the server
b_client_ban_create             # Create bans
b_channel_create_temporary      # Create temporary channels
b_channel_create_permanent      # Create permanent channels
i_channel_subscribe_power       # Enter channel

The pair logic for power values is important: A role needs enough of its own power to perform an action against a target with a certain needed value. If a moderator is allowed to kick users, but the target user or target group has a needed value that is too high, the action still fails. That is not an error, but part of the protection model.

Use Channel Groups Sensibly

Channel groups only apply in specific channels:

Use channel groups for limited responsibility. A raid leader, clan officer, or event host does not automatically need global moderation permissions. They can move or mute users in their channel without being allowed to manage groups, bans, or permanent channels server-wide.

If you separate voice areas for different games, keep the structure simple: lobby, game areas, private group rooms, and support channel. For larger communities with multiple game servers, consistent names help. You can also look at the organization logic from the FiveM Roleplay Guide or the Palworld Server Guide.

Check the Result

Test every role practically after setup. Connect with a second client or a test user and check at least these cases: Can a guest enter the server? Does the guest only see the intended channels? Can a member speak and write? Can a moderator kick, but not change admins? Can a channel admin moderate only in their own channel? Can nobody except admins change server groups?

Then briefly document which group is intended for what. This does not have to be a long operations manual. A table in your internal note system is enough so support and future admins understand why permissions were set this way.

Troubleshooting

User Cannot Enter a Channel

First check i_channel_subscribe_power and the matching needed values of the channel. Then check whether a channel group or direct client permission overrides the server group.

Moderator Cannot Kick or Ban

Check b_client_kick_from_server and b_client_ban_create. If the permissions are active, it is often due to power values: the moderator's kick or ban power must match the needed power of the target user.

A User Has Too Many Permissions

Do not only search in server groups. Also check channel groups and direct client permissions. Old exceptions on individual users are especially easy to miss.

Groups Cannot Be Changed

Check i_group_needed_modify_power and i_group_needed_member_add_power. If these values are set too high, even a role that is generally authorized cannot add members or edit groups.

Tips

• Least privilege: Give only the permissions that are really necessary
• Power system: Higher power can override lower power
• Icons: Upload icons for groups (64x64 PNG)
• Automatic groups: Use bots for automatic group assignment

Checks, Limits, and a Safe Rollback Path

The guide “Set Up TeamSpeak 3 Permissions and Groups” applies to the server type described in the article and the version state visible at the time of review. Menu names, available versions, mod or plugin compatibility, and required resources may differ after updates. So do not transfer values to another game, loader, or server version without checking them.

Before changing the world, savegame, configuration, or extensions, create a backup of the affected files. Then change only one related step and test it with the same client and server version you want to play with later.

A successful single test is not a performance or availability guarantee. World size, mods, plugins, player count, network path, and simultaneous load can change the result. Document the version, change, and test result so you can understand later deviations.

FAQ

Which Permissions Should a TeamSpeak Moderator Get?

A moderator typically needs permissions to move, mute, kick, and, depending on the community, also create temporary bans. Group management and server settings should only be given to admins.

Are Channel Groups Better Than Server Groups?

No, they serve different purposes. Server groups control global permissions. Channel groups are useful when someone needs additional privileges only in a specific channel.

Why Does a Set Permission Still Not Work?

Usually a needed-power value blocks the action. Check the role's own power and the target's needed value. Then check channel groups and direct client permissions.

Should I Use Direct Client Permissions?

Only in exceptional cases. Individual permissions per user are harder to maintain than groups. For permanent roles, server groups or channel groups are almost always clearer.

How Do I Prevent Moderators from Editing Other Moderators?

Set the needed power of the moderator group higher than the moderators' own modify or member-add power. Admins keep correspondingly higher values.