Bug: A non-admin user can take away slash command permissions on 'All channels' but not give them back

[nmsturcke]

Description

You are able to remove permissions from an application command but not give them back.

Steps to Reproduce

1. Go to a server where you have manage server permissions, manage role permissions and you can manage some channels (not all).
2. Head over to Server Settings -> Integrations -> Bots and Apps and select any application with application commands.
3. Select a command (you can also use the global permissions), remove for "All Channels"
4. Try to re-add permissions for "All Channels"
5. Observen application command but not take them back.

Expected Behavior

One of two:

You can give back the permissions normally.

You cannot remove permissions as you cannot manage a certain channel.

Current Behavior

You can take away permissions, but not give them back. It returns a 403 error (Missing Access)

Screenshots/Videos

https://user-images.githubusercontent.com/30734036/181934136-b744ccd6-b0d4-466f-ae86-6fb183f877f5.mp4

Client and System Information

Discord Client Info - Canary 139257 (3c478a7) Host 1.0.48 Windows 10 64-Bit (10.0.19044) (It's an API issue so the client itself doesn't matter)

[erkinalp]

Possibly intentional?

[ratelimit-thief]

bro got his servers all in 500 folders

[nmsturcke]

bro got his servers all in 500 folders

8 folders

[Shark-93]

I've had a similar terrible experience the other day, when Slash Commands were forced on every bot: on the existing bot interaction, I couldn't save any modification of roles or channels that can receive slash commands - the popup Save button wouldn't do anything, I could modify but not save.

In other integrations I could save instead; in others I could only toggle the role off, save, but it wouldn't let me save when I toggled the permission back on. I had to delete the bot integration, re-invite the bot, and it worked but it was still finicky, sometimes the "Save" button wouldn't do a thing (it was like, stuck; only Reset would work).

I realize it's quite a generic feedback but, damn I was frustrated yesterday. Deleting the integration meant that I then had to re-configure all the permissions that I had assigned through the integration's generated role, in my server's channels. Loss of data that I didn't anticipate, because I erroneously thought the role was mine and not part of the integration.