Blog · Guide

How to set up your guild's TeamSpeak from scratch: channels, groups and privilege key

By TXBot Team · Published October 30, 2026 · Updated October 30, 2026

Quick answer: Create a few channels with a clear purpose (reception, leadership, hunts and war, AFK), split people into server groups (leader, member, visitor), lock the leadership area with the channel join permission and use a privilege key to hand out roles without sharing passwords. Last, add a bot to show hunteds, deaths and respawns right on TS.

Guild TeamSpeaks are usually born messy: someone rents a server, creates twenty joke-named channels, gives admin to half the world and, at the first war, nobody knows where the call is. Half an hour of organizing avoids that. This step by step works for TeamSpeak 3 and TeamSpeak 6; menu names change a little, the logic is the same.

Which channels does the guild need?

Less is more. Each channel should have a reason to exist, and a first-time visitor must understand the layout at a glance. A layout that works for most guilds:

Reception: the default channel, where everyone lands on connecting. Visitors wait here until someone from leadership picks them up.
Restricted area: leadership and council. Locked by permission, not by password (explained below).
Hunts and war: a row of numbered channels (Channel 01, 02, 03…) instead of fixed names. The hunt, boss or war team takes the next free one, no arguing.
AFK: for people who left the PC without disconnecting, so they do not get in the way of the call.
Bot channels: if the guild uses a bot, it creates its own information channels. Leave room for them right below the default channel.

Create them all as permanent channels (right-click the tree → Create channel). A temporary channel disappears when the last person leaves, and a password-protected channel becomes a headache: the password leaks in the first screenshot and nobody remembers to change it.

How should you organize the server groups?

A server group is the person's role across the whole TS. The server already comes with Server Admin, Normal and Guest (whoever just arrived). For a guild, three or four roles are enough:

Leader: few names, with the administrator group. Whoever has it can do anything, including deleting the server.
Member: create it by copying Normal (Permissions → Server Groups, right-click → Copy). Talks in every guild channel but does not touch the structure.
Ally or visitor: people from another guild who come for a war or a boss. They join the hunt channels, not the restricted area.
Guest: leave it as it is and remove its permission to create channels, so outsiders do not fill the tree with temporary channels.

Give the groups icons: with 40 people in a war call, spotting the leader by the icon next to the name saves time.

How do you lock the restricted area without a password?

The right way is join power. In the restricted channel's permissions, set i_channel_needed_join_power to a number, for example 50. Then, in the Leader group's permissions, give i_channel_join_power 50. Anyone with equal or higher power gets in; everyone else sees the channel but cannot pass the door. Leadership changed? Just change the person's group, no new password to spread around.

The same idea works for the war call: with i_client_needed_talk_power on the channel, only people with enough talk power can speak, and the caller is not run over by twenty open mics.

How do you hand out roles with a privilege key?

A privilege key is a single-use code that puts whoever uses it into a group. Instead of handing the server password to the new vice leader, you create a Leader group key and send it to them; they use it once and that is it. The step by step for TS3 and TS6 is in the how to create a privilege key guide.

On TeamSpeak 6, if the bot or a visitor with no group is refused on joining, give the Guest group permission to join the default channel (or leave the default channel open).

And how do you add TXBot to the TeamSpeak?

In the TXBot panel, under Connection, enter the TS address and paste a privilege key for the administrator group. The bot joins, uses the key once, creates its own TXBot group and leaves the admin group.
It builds a block of information channels below the default channel: hunted and friend online, deaths, occupied respawns and the commands.
For automatic groups, create level range groups named NUMBER+ (100+, 200+…) and vocation groups with the abbreviation (EK, RP, ED, MS, EM). The bot only uses groups that already exist; it never creates or deletes any.
Ask each member to write Main: Character Name in their own TS description. That is how the bot knows everyone's level and vocation.
If you want, turn on automatic AFK in the panel: anyone away, muted or idle for the time you choose goes to the AFK channel, and the groups you tick are left out.

To get the description right, use the TS description generator. And if the guild has no server yet, the TXBot TeamSpeak 3 server comes with a restricted area, Channels 01 to 12, AFK and groups with vocation icons ready, in São Paulo and with anti-DDoS.

Frequently asked questions

Do I need a ServerQuery password to add the bot?

No. TXBot joins as a regular client and only needs a privilege key for the administrator group. If your TS cannot create keys, it joins as a guest and sets itself up once you give it the highest group from TeamSpeak itself.

Does this work on TeamSpeak 6?

Yes. Channels, server groups and privilege keys exist on TS6 with the same logic, and TXBot works on TS3 and TS6. On TS6, if the bot is refused for being a visitor with no group, let Guest join the default channel.

Does the bot create the level and vocation groups on its own?

No. It only uses groups that already exist on the server, recognized by name: level ranges like 100+ or 200+ and vocations by abbreviation (EK, RP, ED, MS, EM). The panel's Automatic groups page shows which ones it found.

Try TXBot free for 3 days: no card needed, and the bot joins your TeamSpeak in a few minutes.