Discord server for a business: layout and roles

For a business or brand community, set up read-only rules, announcements and product updates, open channels for introductions, feedback and showing off, a voice room for live sessions, and a private room for your team. Bond, an AI Discord bot, can build all nine channels from one message after you approve its plan. By hand, the same layout takes seven steps.

A business, brand or creator that wants its customers in one community.

4 categories · 9 channels · 1 role

Channels and roles for a business community server.

The channel list as members see it, and who can see and post in each channel.

The channel list

Corner Shop Community
START HERE
rules
announcements
product-updates
COMMUNITY
general
introductions
feedback
showcase
EVENTS
Town Hall
STAFF
team-chat
Y
youonline

Who sees and posts where

ChannelEveryoneTeam
Start Here
#rules
#announcements
#product-updates
Community
#general
#introductions
#feedback
#showcase
Events
Town Hall · voice
Staff
#team-chat
  • Sees and posts, or joins voice
  • Reads only
  • Hidden

Roles · Team

Who this is for.

You run a business, a brand, a shop or a creator channel, and you want the people who buy from you or follow you in one place you control. You want news and product updates where nobody can bury them, a place for customers to talk to each other and tell you what they think, and a room your team can use without customers reading it.

If most of what people bring is a problem to fix, the support server layout fits better: it puts help, bug reports and feature requests first.

The one prompt to give Bond.

An example, not a recording: the plan Bond shows before it builds anything, and what it does once you approve it.

@Bond Set up a community server for my business: a start here category with rules, announcements and product-updates channels only the Team can post in, a community category with general, introductions, feedback and showcase channels, an events category with a Town Hall voice channel, and a private staff area with team-chat. Make a Team role.

The plan Bond shows first

general
BondAPPexample

Business community layout

plan for @You

4 categories, 9 channels and 1 role. Your current channels stay as they are.

▼ START HERE · 🔒 Everyone can read; Team can post

rules Community rules

announcements News and launches

product-updates Release notes

▼ COMMUNITY · Open to everyone (default)

general Chat

introductions New members say hello

feedback Tell the team

showcase Show your work

▼ EVENTS · Open to everyone (default)

🔊 Town Hall Live sessions and Q&As

▼ STAFF · 🔒 Team only

team-chat Team coordination

Roles · Team

Everyone can view #rules, #announcements and #product-updates but cannot send messages; Team can send there.

Only Team can view Staff and its channels.

Keeps Existing categories, channels and roles stay unchanged.

# grey planned · Expires in 10 minutes

Build it approves everything drawn above, for this run.

Deletions, @everyone access and Bond's own access still ask.

Build itChange somethingCancel

After the plan, Bond asks before each change: 10 times in this example. Always allow on a card stops it asking about that kind of change.

What Bond does

The business community server is built and access was checked.

  • Created Start Here with #rules, #announcements and #product-updates. Everyone can read them, and only Team can post.
  • Created Community with #general, #introductions, #feedback and #showcase, open to everyone.
  • Created Events with the Town Hall voice channel, open to everyone.
  • Created Staff with #team-chat, visible only to Team.
  • Created the Team role. It has no members yet, so give it to your staff.

The access check passed: everyone can see Start Here, Community and Events, and only Team can see Staff. Your existing channels were left unchanged.

This is an example, not a recording of a real run. Bond's own code draws the cards. The request, the plan, Bond's steps and its reply are written from how Bond handles a request like this one. The server, channel and member names are made up.

In Discord, without a bot.

  1. Create the Team role. Open Server Settings, Roles, Create Role, name it Team, and save.
  2. Create the Start Here category. Right-click the channel list, Create Category, name it Start Here, and add three text channels: rules, announcements and product-updates.
  3. Make it read-only. Right-click the category, Edit Category, Permissions. For @everyone, set Send Messages to the red cross. Add the Team role and set Send Messages to the green tick.
  4. Create the Community category with four text channels: general, introductions, feedback and showcase.
  5. Create the Events category with one voice channel, Town Hall.
  6. Create the Staff category with Private Category switched on, pick the Team role, and add a team-chat text channel.
  7. Give the Team role to your staff. Right-click a member, Roles, and tick it.

Channels created inside a category take the category's permissions, so each rule is set once on the category.

What to watch for.

  • The Team role this builds has no permissions of its own. It can post in Start Here and see Staff, and nothing more. To let your team time members out or delete messages, give the role those permissions in Server Settings, Roles, or ask Bond to and name the permissions.
  • The role is empty after the build. Give it to your staff, or nobody but admins can post in #announcements.
  • The server owner and anyone with Administrator can read the Staff category.
  • An announcement channel that other servers can follow, and Onboarding, need Community turned on first, under Server Settings, Enable Community.
  • Bond leaves existing channels alone, so Discord's default #general stays beside the new one until you delete it or ask Bond to.
  • Building this uses tokens from your weekly allowance. A free account gets 1M tokens a week.

After the build.

Questions people ask.

  • What channels should a business Discord server have?

    Rules, announcements and product updates that only your team posts in, a general chat, an introductions channel, a feedback channel, a showcase channel, a voice channel for live sessions, and a private team channel. That is nine channels in four categories.

  • How do I keep customer support out of the general chat?

    Add tickets. A ticket is a private thread between one member and your team, opened from a button. Ask Bond for a ticket system and it installs the button in a support channel, with a log of closed tickets that only your team can read.

  • How do I let other servers follow our announcements?

    Turn on Community in Server Settings, then make announcements an announcement channel. Other servers can follow it and get each post in a channel of their own. Once Community is on, ask Bond to convert the channel and it keeps the channel's name, place and permissions.

  • How do I run a live launch or Q&A?

    Hold it in the Town Hall voice channel and create a Discord event for it, so members see it coming and can mark themselves interested. Ask Bond to schedule the event for that channel and announce it in announcements.

Ask for it in your own words.

Free to start. Bond never needs Administrator, and it shows you the plan before it builds anything.