Add a permission like Cannot be blocked or muted (server-side)

TeamSpeak 6 Server
,
1

Add a permission like Cannot be blocked or muted (server-side)

It would be useful to introduce a server permission that prevents certain clients from being blocked or muted by others.

If a user has this right, other clients should not be able to block or mute them. This ensures that important roles like administrators, moderators, or official support accounts can always communicate with users, even if someone would normally try to block them.

Why should this be added?

Because it simplifies server moderation and enforcement. Instead of relying on rules like You are not allowed to block or mute team members, the server could technically enforce it.

It is especially important for bots and verification systems that need to deliver messages such as login codes or account confirmations. If a user blocks the bot, critical communication may fail.

Overall, this reduces support effort, because staff no longer needs to investigate cases where users claim they are not receiving messages, only to discover that they blocked the admin or the bot.

This permission would improve reliability, communication, and administration on TeamSpeak servers.

1 Like
2

I understand the use case, especially for bots, but making this a server permission does from my point of view not work.

Blocking and muting are important safety and privacy tools. If certain clients cannot be blocked or muted at all, users lose immediate control over unwanted contact. And if permissions are not configured like intended it could lead to abused. Leaving the user no option to mute an admin / bot could create trust issues or lead to confusion..

Adding to that I don’t see a proper way to implement this when TS3 is still around.

4 Likes
3

Well, it is server sided, and if you do not like it, then you simply do not join the server. You can find another one or run your own. With bots it is the same, it is only for a specific server anyway.

I honestly do not think it is as big of a problem as you describe, especially when you consider that basically all forum software includes similar functionality.

And regarding your point: “And if permissions are not configured like intended it could lead to abuse”
Yes, but that issue exists with every permission. Not only with this one. For example, adding or removing server groups, accessing IP addresses, or many other rights can also be abused if permissions are configured incorrectly.

In the end, it is the responsibility of the server owner to configure and manage everything properly.

Also, this is supposed to be a TeamSpeak 6 feature, right? Or are you saying that for you TS6 is only about the UI and you actually want to keep TS3 running underneath, just with a new TS6 server license system?

(And screensharing is client sided anyway, it has nothing to do with server side features.)

_______________

For me, and for many people I know, the current state of TeamSpeak 6 is basically just minimal improvements for the newgen users and nothing more.

It feels like almost only UI changes.

The self hosted Homebase feature is gone…, even though that was actually a really cool idea. Now even the chat is hosted by TeamSpeak Systems GmbH.

So to me it looks like:

TeamSpeak 6 = UI, p2p screenshare, and “offline” private chat.