Set command permissions by category

[edocsil47]

Has there been any consideration of allowing command permissions to be set by category? I was surprised to see that automod could be set up to whitelist categories when there isn't a similar feature for setting command permissions. This would vastly simplify our permission settings and save us a lot of work as we frequently create/delete channels and currently have to denylist a couple dozen commands for each of them.

Automod:

[onerandomusername]

This would be amazing if it were to be implemented, I don't want to set overrides for a bunch of channels in a category, or have to update the overrides whenever I make a new channel!

[RealAlphabet]

Or give the possibility to a bot to modify the permissions of other bots (integrations). This would automate the process and would be even better I think.

[ghost]

+1 Was looking for this before I posted one myself.

Or give the possibility to a bot to modify the permissions of other bots (integrations). This would automate the process and would be even better I think.

This would be amazing!

[advaith1]

bots with appropriate permissions can modify everything else in server settings so currently this is a weird exception

[RealAlphabet]

That sounds scary tho, what's your use case?

A new kind of raid is to use a selfbot to bulk change the permissions of all bots. This is very annoying especially on large servers.
Imagine an anti-raid bot... that could restore bot (integrations) permissions.

Unfortunately, anti-raid and backup bots cannot save or restore these settings.
It could also allow a bot to present a simpler GUI to edit multiple permission groups directly.
A new OAuth2 scope should be added.

[AlmostSuspense]

users without perms can't edit command permissions selfbot or not though, so what raid are you talking about?

[RealAlphabet]

Raids are often initiated by malicious staff members or compromised staff accounts. At least, in french communities.

EDIT :

Selfbot accounts are user accounts. So yes, they can change command permissions.

Also, Fr communities have found a way to edit role and integration permissions without generating logs in audit logs. (Confirmed)

But that's not the primary case I'm thinking of for setting commands of other integrations by a bot.

There are plenty of other cases that could be used. in particular helping newcomers to configure their roles more easily from an embed or a web page.

The permissions of the integrations are good but clearly lack control. If I want to allow a user to setup a particular bot without granting them "Manage Server" permission (dangerous if the person changes vanity URL and snipe) I absolutely cannot.

[ghost]

I wonder what you mean by "scary". Bots currently, using a bearer token can update their own integrations permissions. However, this doesnt extend to other bots. Servers having multiple bots which want to effectively sort bots based on commands, types etc find it very difficult to for example, when a new channel is created and all bots need to be added to it.

Going to each integration and adding the bot is a huge waste of time.

A bot could just request authentication, which will give the bot a bearer token, which will be able to loop over integrations and enable the bot in the channel, or loop over certain commands enabling them in a channel etc etc.

[ahnolds]

This seems like a complete no-brainer. Why make guild admins set these permissiond on every individual channel when every other type of permission (includibg automod) can be set by category?

Plus requiring these permissions to be by individual channel almost guartees new channels will have the wrong permissions - either blocked when they should be allowed, or (probably worse) allowed when everything else in the category blocks them.