Keeps a member or a role out of your room. The target option takes either. Same checks as the other owner commands: the service is on, you are inside a Join-to-Create room, and you own it (or you hold Manage Channels or Administrator on the server).
In Discord, the bot denies Connect on the target's own permission entry for the room. Then it disconnects anyone in the room who matches, that is the member, or every member holding the role, leaving bots and the room's owner alone. The reject is remembered for you on this server and applied to every new room you create, under the same 25-entry list as permits; when the list is full the reject still applies to this room but is not kept.
You see a private reply: "🚫 {name} is kept out of this room."
Targets the bot refuses, with its reply:
- @everyone: "That is everyone. Use
/voice lockor/voice hidefor the whole room." - A role owned by an integration: "That role belongs to an integration and cannot be changed here."
- The bot's own role: "That is the bot's own role. The bot keeps its access to the room." The bot itself: "The bot keeps its own access to the room."
- The room's owner: "You cannot reject the room's owner."
Unless you hold Manage Channels or Administrator on the server, staff and people above you are off limits too:
- A role with Manage Channels or Administrator: "That role is server staff. Only a server manager can do that."
- A role at or above your top role: "That role is ranked above yours."
- A member with Manage Channels or Administrator: "That member is server staff. Only a server manager can do that."
- A member whose top role is at or above yours: "That member is ranked above you."
Good to know
- Reject changes Connect only. The room stays visible to them unless you also hide it.
- /voice unreject lets them back in. /voice permit does too, and replaces the remembered reject.
- /voice kick removes someone once without keeping them out.
- The panel's Reject button opens a picker with the prompt "Who should be kept out?"