Docs / Tickets / Commands / /ticket remove
Moderation Server only

/ticket remove

Remove a member or a role from a ticket

Usage

Generated
/ticket remove <target> [ticket]
OptionTypeRequiredDescription
target member or role Yes Member or role to remove
ticket channel No The ticket, when you are not in it (text, announcement, 10, 12, 11 channels)

Who can run it

Generated
Discord defaultEvery member
Command Access presetModerator roles
Always allowedThe server owner and, by default, Administrators
Change itDashboard, Services, Tickets, Commands

The Moderation preset limits it to the roles you mark as moderators. Server owners and Administrators can always run it. How Command Access works.

What the bot needs

Generated

Tickets is granted these permissions by the invite link. A command that finds one missing replies privately with what it could not do and changes nothing.

Manage ChannelsView ChannelSend MessagesEmbed LinksRead Message HistoryManage RolesManage ThreadsCreate Private ThreadsSend Messages in Threads

Behaviour

Checked against the code 2026-10-08

Takes a member's or a role's access to a ticket away: the one you are in, or any other ticket you pick in the ticket option.

The bot first applies the server's Command Access rules for /ticket remove and checks that Tickets is enabled ("❌ Tickets is not enabled for this server."). Without the ticket option the command only works inside a ticket channel or thread ("No ticket found in this channel."); a ticket option that points at another kind of channel answers "That channel is not a ticket." Only staff of that ticket may remove people: Manage Server, the ticket's staff team or a role given access when the ticket opened. Others see "Only staff can remove users." When the panel keeps the ticket actions to the claimer ("Taking a ticket" on 2 Answering), everyone except the claimer, the ticket's owner and server managers sees "Only @<claimer>, who claimed this ticket, or a server manager can do that."

Access that comes from the ticket itself stays, so these targets are refused:

  • @everyone: "Tickets stay private, so @everyone can't be added or removed."
  • any role on a thread ticket: "This ticket is a thread, and threads only take members. Add people one at a time instead."
  • one of the ticket's staff roles: "@role is one of this ticket's staff roles, so it keeps its access. Transfer the ticket to change the team."
  • a member of the ticket's staff team, and on a thread ticket anyone holding one of its staff roles: "@member is on this ticket's staff team, so they keep their access. Transfer the ticket to change the team."
  • the member who opened the ticket: "Cannot remove the ticket creator." A ticket by DM is the exception. Its member is in the channel or thread only when someone added them with /ticket add, so they are removed like any other added member.
  • the bot: "I need to stay in the ticket to run it."

The bot needs Manage Permissions in a ticket channel, or Manage Threads in a thread ticket; without it you get "⚠️ I'm missing the <permission> permission in #<ticket>." In a text channel the bot takes back the view and send permission from the target's own entry on the channel; a target without an entry answers "@target was not added to this ticket." In a thread the member is removed from the thread. On success the bot posts "➖ @target has been removed from this ticket." in the ticket without pinging anyone, and the removal is recorded in the ticket's "Activity log". Run from another channel, you also get a private "✅ Done in #<ticket>."

Good to know

  • A member who can still see the channel through one of their roles keeps seeing it, and the bot tells you so: "They can still see this ticket through one of their roles."
  • If Discord refuses the change, you get a private "⚠️ Missing permission to modify channel." and nothing is recorded.
  • /ticket add gives access back.
YourBot docs Reference tables are generated from the code that is running. Ask in Discord Suggest a correction