Discord Server Layout: Copy and Paste Channels, Categories and Who Sees What

Most layouts online stop at channel names. This one also says who should see each category, and spends longest on Support, the section most servers get wrong.

What is a good Discord server layout?

Short answer: one category per job, in the order a new member needs them. Information first, because a newcomer reads it first. Voice goes at the bottom.

INFORMATION
  #welcome
  #rules
  #announcements
  #roles
COMMUNITY
  #general
  #media
  #off-topic
  #suggestions
SUPPORT
  #faq             read-only
  #open-a-ticket   see it, cannot type
  #ask-the-bot     optional
🎫 Tickets         hidden, the bot fills it
STAFF ONLY
  #staff-chat
  #ticket-logs
  #mod-log
VOICE
  🔊 Lounge
  🔊 Gaming
  🔊 AFK

Start with fewer channels than you think. A channel nobody posts in makes a server look empty, so add one when members keep asking for it. #mod-log is where your moderation bot reports.

Discord allows 500 channels per server, categories included, and 50 per category. A layout like this never comes close. Ticket channels are what fill a server, as the 500 channel limit explains.

Discord server layout templates to copy and paste

Three variants of the same idea. Keep what fits and delete the rest.

Small friends or community server

INFORMATION
  #welcome
  #rules
CHAT
  #general
  #media
  #bot-commands
VOICE
  🔊 Hangout
  🔊 Gaming

No Support section: a server of friends does not need one until questions get lost in #general.

Gaming or roleplay server

INFORMATION
  #welcome
  #rules
  #announcements
  #how-to-join
  #server-status
ROLEPLAY
  #character-intros
  #in-character
  #out-of-character
  #screenshots
JOBS AND FACTIONS
  #jobs
  #whitelist
SUPPORT
  #faq
  #open-a-ticket
  #ask-the-bot
🎫 Tickets
STAFF ONLY
  #staff-chat
  #ticket-logs
  #reports-log
VOICE
  🔊 Waiting room
  🔊 Scene 1
  🔊 Scene 2

Reports, ban appeals and donation problems belong in tickets, not #general. Route each kind to its own staff role with ticket categories.

Shop or creator server

INFORMATION
  #welcome
  #rules
  #announcements
SHOP
  #prices
  #portfolio
  #commission-status
  #reviews
COMMUNITY
  #general
  #showcase
SUPPORT
  #faq
  #order-here
🎫 Tickets
STAFF ONLY
  #staff-chat
  #orders-log
VOICE
  🔊 Lounge

Here #order-here is the ticket panel, so every order is a private ticket and payment details stay out of public chat.

Should Discord channel names have emojis and symbols?

Short answer: plain words, with at most one emoji in front. Both of these work:

CLEAN             DECORATED
#welcome          #👋・welcome
#rules            #📜・rules
#announcements    #📢・announcements
#general          #💬・general
#open-a-ticket    #🎫・open-a-ticket

Decoration looks good in a screenshot, and it has costs. Screen readers read each emoji and symbol aloud, before every channel name. Letters from fancy font generators are symbols that only look like letters, so typing # and the word may not find the channel. And a bot that looks for a channel by its exact name, as /setup does below, will not recognise a decorated one.

Separators such as ・ or ┃ are a matter of taste. Pick one style and use it on every channel.

Who should see each category?

Set permissions on the category, not on each channel. Right-click the category, choose Edit Category, then Permissions. A channel synced with its category follows every change made there. Change one channel on its own and it stops following, until you press Sync Now in its permissions.

Read-only means @everyone keeps View Channel and loses Send Messages. Turn off Create Public Threads too: Send Messages does not cover threads, so members could otherwise start one under your rules or your panel.

Hidden means @everyone loses View Channel, and only the roles that need it get it back. Anyone with Administrator sees every channel whatever you set, so test as a member. Which roles your team needs is in Discord staff roles.

How do you set up the Support section?

Short answer: one job per channel, and members only type where you want them to.

The panel channel holds the panel and nothing else. A panel buried under chat is a panel nobody finds. For the channel above it, use the FAQ template.

The ticket category stays hidden. A Discord ticket bot fills it with one private channel per ticket. On AI Ticket Bot each ticket channel carries its own permissions: hidden from everyone, open to the member who opened it, the staff role set for that type of ticket, roles allowed to see every ticket, and the bot. So hiding the category hides nothing members need.

Tickets opened as private threads instead sit under a text channel members can see and do not count toward Discord's channel limits. Members then need Send Messages in Threads there. Threads or channels compares the two.

The log channel goes in Staff only. On AI Ticket Bot, log channels are free on every plan, set per panel and per event: opened, claimed, closed and transferred. The opened post names the member and the type of ticket, and the closed post links the transcript. Nothing stops you pointing logs at a public channel, so check who can see it.

The AI FAQ channel is optional. Unlike #faq, members type here. Pick it with /ai channel and the AI answers from what your staff taught it, when mentioned or on every message. Every plan has at least one: one on Free, three on Premium, five on Pro. When a question needs a person, it tells the member to open a ticket.

Does a Discord server template copy everything?

Short answer: the structure, never the content.

Only the owner or someone with Manage Server can make one, under Server Settings > Server Templates, on desktop or in the browser. Three catches:

• It does not follow your changes until someone presses Sync Template.
• It can disappear. If its creator deletes the template, the link stops working.
• Big servers can be refused. Past 1,000 channel permission settings, Discord makes no template until some are removed.

The catch for ticket servers: a ticket panel is a message posted by a bot, and a template brings neither the bot nor the message. The new server gets an empty #open-a-ticket.

How do you use a Discord server template link?

On AI Ticket Bot, the last step is /setup. It needs Manage Server, runs only on a server with no panel yet, and the bot needs Manage Channels and Manage Roles. It reuses what the template brought when the names match: a role with Support or Staff in its name, a category named 🎫 Tickets that the bot's role can see, and a channel named open-a-ticket. It creates what is missing, then posts the panel. With decorated names, use /panel instead and pick your own channels.

What AI Ticket Bot creates, and what it leaves to you

It does not build your layout, only what tickets need.

An overflow category takes your category's name with a number, such as Support_2. The switch is "Clone category when channel limit is reached" in /ticket settings, off by default. More in ticket category full.