TeamSpeak 6 Permissions & Communities Best Practices
Management in TeamSpeak 6 has evolved significantly from the classic "Group List" view. With the introduction of Communities, the permission system is now more intuitive but also introduces new layers of flexibility.
🤝 What are Communities?
Communities are a new way to organize servers and users in TeamSpeak 6. They allow you to bundle multiple virtual servers, sub-channels, and social features into a single logical entity with shared permissions and discoverability.
The New Permission Interface
Gone are the days of searching through thousands of numeric IDs (though they still exist for power users). The TS6 UI focuses on Roles and Capabilities.
Hierarchy in TS6:
- Community Owner: Absolute control over all servers in the community.
- Global Roles: Permissions that apply across the entire community.
- Server Roles: Traditional Server Groups (like Server Admin, Moderator).
- Channel Roles: Modern version of Channel Groups.
Best Practice: The "Modular Role" Approach
In 2026, successful communities move away from "Jack-of-all-trades" roles towards modular permissions. This makes it easier to manage staff and automated bots.
Recommended Role Setup:
| Role Name | Type | Primary Responsibility |
|---|---|---|
| Community Architect | Global | Permissions, structure, and API integrations. |
| Streamer Manager | Global | Manages guest permissions and screen sharing limits. |
| Server Guardian | Server | Day-to-day moderation (kick, ban, move). |
| Supporter | Channel | Assistance within specific help channels. |
Managing Screen Sharing & Video Permissions
One of the most common tasks in TS6 is managing the high-bandwidth features like 1440p Screen Sharing.
Permission Nodes to Watch:
b_client_screenshare_allowed: Master switch for screen sharing.i_client_screenshare_max_resolution: Limit users to 720p, 1080p, or 1440p.i_client_screenshare_max_fps: Limit to 30 or 60 FPS (useful for saving server bandwidth).b_client_camera_sharing_allowed: Toggle for webcam usage.
Communities Permission Syncing
A flagship feature of TS6 is the ability to Sync Roles across multiple servers within a community. If you have a "Minecraft" server and a "General Chat" server, you can ensure your Moderators have the same powers on both without manual setup.
How to enable sync:
- Navigate to the Community Dashboard.
- Select Role Management.
- Click on the Role (e.g., "Moderator").
- Enable "Propagate to all Virtual Servers".
Transitioning from TeamSpeak 3
⚠️ Legacy Permissions
When you migrate a TS3 server to TS6, your old groups are imported as "Legacy Server Groups". While they still work, it is highly recommended to convert them to the new Role System to take advantage of the modern UI and syncing features.
Steps for a clean migration:
- Backup your
ts3server.sqlitedb. - Run the TS6 Migration Tool (included with the TS6 Server package).
- Audit "Skip" and "Negate" flags, as the logic remains the same but the UI might hide them under "Advanced Mode".
- Move your "Query Logins" to the new API Keys system for better security.
Advanced: Offsets and Power Values
For large competitive communities, the "Power vs Needed Power" system is still the gold standard for protection.
# Scenario: Only Senior Mods can ban Junior Mods
Senior Mod: i_client_ban_power = 75
Junior Mod: i_client_needed_ban_power = 75
Junior Mod: i_client_ban_power = 50
Senior Mod: i_client_needed_ban_power = 100
Expert Tip: Always use Templates when creating new Roles. TeamSpeak 6 comes with pre-configured templates for "Gaming", "Business", and "Privacy-Focused" setups that save hours of clicking.