Discord · Discord desktop and browser

Create a Private Support Channel System on Discord

Source-checked 9 August 2026About 10 minutes

Answer

Discord does not document a native ticket object. For a small server, create a private Support category, deny @everyone the View Channel permission, allow a limited Support Team role, then create one private text channel per request and explicitly add that requester. Test with an unrelated member before accepting real requests; private channels are not suitable for passwords, codes, payment details, or regulated records.

Define the support boundary first

Choose the staff who will answer requests, a neutral channel naming pattern, support hours, and when closed channels will be deleted. Publish a short notice telling members never to post passwords, login codes, payment details, identity documents, or regulated records.

Create a limited Support Team role

Select the server name > Server Settings > Roles > Create Role. Name it Support Team and grant only the server permissions staff genuinely need; do not enable Administrator. Assign it only to the intended staff and confirm its member list is correct.

Make the Support category private

Create a category named Support, right-click it, then select Edit Category > Permissions. Add @everyone and deny View Channel. Add Support Team and allow View Channel, Send Messages, and Read Message History, then save. Confirm an unrelated test member cannot see the empty category.

Create one channel for the requester

Create a text channel inside Support using the neutral ticket name. Open Edit Channel > Permissions, add the requester as a member override, and allow View Channel, Send Messages, and Read Message History. Keep @everyone denied and Support Team allowed. The requester override makes this channel different from the category defaults, so inspect it directly instead of assuming it remains fully synced.

Test all three visibility states

Before posting real details, verify that the requester can open and reply in the channel, a Support Team test account can open and reply, and an unrelated normal member cannot see the channel at all. Correct the smallest channel override that fails; do not grant Administrator to make the test pass.

Close the request without exposing it

When support is complete, tell the requester when the channel will close, then remove their View Channel override or move the channel to a staff-only archive with verified permissions. Preserve only the moderation evidence your published policy requires, then delete the channel according to that policy.

If it does not work

If the requester cannot see the channel, open that channel's Permissions page and confirm their individual override allows View Channel. A category permission alone does not identify the requester.
If an unrelated member can see a request, immediately remove their access and confirm @everyone is denied View Channel on both the category and any non-synced ticket channel.
If staff lose access after a category change, check whether the ticket channel is marked non-synced. Review its Support Team override directly before choosing Sync Now, because syncing can erase the requester's individual access setup.
If the number of requests makes manual channel creation or closure unreliable, pause expansion and evaluate a current App Directory ticket app. Review its developer, privacy policy, support route, and every permission; do not rely on the historical video's Ticket Tool screens.

Sources and verification

Checked against official documentation on 9 August 2026. Scope: Discord desktop and browser.

Discord documents private role-exclusive channels plus category and member permission overrides, but not a native ticket object. This procedure builds a small manual system from those supported controls.