Add TicketCrew to your server
Discord shows the permissions below on its own screen before you confirm. The optional ones, Administrator included, can be unticked there or taken away later. You need Manage Server in the server you add it to.
What it asks for
Without these it cannot open or look after a ticket.
| View Channel | See the channels your panels live in, and the tickets it creates. |
| Send Messages | Post ticket panels and reply inside tickets. |
| Embed Links | Render ticket panels and ticket headers as rich embeds. |
| Read Message History | Build transcripts and detect inactivity for auto-close. |
| Manage Channels | Create, rename, lock and delete the ticket channels themselves. |
| Manage Roles | Grant a ticket opener access to their own ticket channel. Only ever applied to channels TicketCrew created. |
Optional: it works without these, and only loses what is described.
| Attach Files | Attach the generated transcript when a ticket is closed. |
| Manage Messages | Pin the ticket header so it stays reachable in long tickets. |
| Administrator | Not needed. It saves letting TicketCrew into each channel by hand if your server locks them all down. Untick it on Discord’s screen if you would rather not give it. |
What it never does
Administrator or not: these are things TicketCrew is built never to do.
- Banning, kicking or timing out members
- TicketCrew never acts on a member's account.
- Pinging everyone
- @everyone and @here are blocked in everything it sends. It only pings the staff roles you chose for a ticket type, when a ticket opens.
- Reading your email
- Signing in to the website asks Discord only for
identifyandguilds: your name, and which servers you are in.
Two things Discord asks us to declare
TicketCrew uses Message Content, so transcripts contain the messages, and Server Members, so staff roles can be checked without asking Discord for every message. Both are switched on on our side; there is nothing for you to set.