Skip to content

Add TicketCrew

Eight permissions, each one justified below. You can review them on the Discord screen before confirming, and revoke any of them afterwards.

Continue to Discord

Required

Without these, TicketCrew cannot open or manage a ticket at all.

  • ViewChannel

    See the channels your panels live in, and the tickets it creates.

  • SendMessages

    Post ticket panels and reply inside tickets.

  • EmbedLinks

    Render ticket panels and ticket headers as rich embeds.

  • ReadMessageHistory

    Build transcripts and detect inactivity for auto-close.

  • ManageChannels

    Create, rename, lock and delete the ticket channels themselves.

  • ManageRoles

    Grant a ticket opener access to their own ticket channel. Only ever applied to channels TicketCrew created.

Optional

TicketCrew works without these; it just loses the feature described.

  • AttachFiles

    Attach the generated transcript when a ticket is closed.

  • ManageMessages

    Pin the ticket header so it stays reachable in long tickets.

What we deliberately do not ask for

  • Administrator. A support bot has no business holding the keys to your whole server.
  • Ban, kick or moderate members. TicketCrew never acts on a member account.
  • Mention everyone. Only to ping the support roles you picked for a category when a ticket opens. Never @everyone, and never a role you did not choose.
  • Your email. Signing in uses only identify and guilds.

Two privileged intents needed

TicketCrew asks Discord for Message Content and Server Members. The first is what makes transcripts contain anything; the second is how staff roles are checked without an API call for every message. Both are already enabled on our side - nothing for you to configure.

Already added it? Open the dashboard.