Set up a study server: info category with rules and announcements only mods can post in, general and resources channels, a study voice room, and a private staff area.
How to set up a Discord server
In Discord you create the server, then build its categories, channels and roles by hand and lock the right ones down in each channel's permissions. With Bond you describe the server in one message, it shows a plan listing every channel and role before it builds anything, and it builds only what you approve.
Verified 27 Sept 2026 on a test server · build d0bec7a
In Discord, without a bot.
- Press + at the bottom of the server list, choose Create My Own, pick who the server is for, and give it a name and an icon.
- Right-click the channel list and choose Create Category for each area, for example Info, Study and Staff.
- Press + next to a category to add its channels: #rules and #announcements under Info, #general, #resources and a voice channel under Study.
- Create a moderator role in Server Settings, Roles with only the permissions it needs, and drag the roles into order: moderators above members, and each bot's role above the roles it manages.
- Make the Info category read-only: Edit Category, Permissions, deny @everyone Send Messages, and allow it for the moderator role. Channels synced to the category follow it.
- When you create the Staff category, switch on Private Category and add the moderator role, so it is hidden from everyone else from the start.
- Set a Verification Level in Server Settings, Safety Setup, and consider Enable Community in Server Settings for Onboarding, Rules Screening and announcement channels.
Every step above repeats for each channel and role you add. Bond does the same build from one message. See it as an AI Discord server builder.
For a layout made for one kind of server, with its channels, roles and who sees what, start from a guide: D&D campaign, study server, support server or gaming community.
With Bond, in one message.
A real run, recorded on a test server: what was asked, what Bond asked you to approve, what it did, and what members saw afterwards.
@Bond Set up a study server: info category with rules and announcements only mods can post in, general and resources channels, a study voice room, and a private staff area.
In #admin-chat
Y
you27 Sept 2026
@Bond Set up a study server: info category with rules and announcements only mods can post in, general and resources channels, a study voice room, and a private staff area.
BondAPP27 Sept 2026
Build itChange somethingCancel
BondAPP27 Sept 2026
AllowAlways allowDeny
BondAPP27 Sept 2026
AllowAlways allowDeny
BondAPP27 Sept 2026
AllowAlways allowDeny
BondAPP27 Sept 2026
AllowAlways allowDeny
BondAPP27 Sept 2026
AllowAlways allowDeny
BondAPP27 Sept 2026
AllowAlways allowDeny
BondAPP27 Sept 2026
ConfirmCancel
BondAPP27 Sept 2026
AllowAlways allowDeny
BondAPP27 Sept 2026
AllowAlways allowDeny
What Bond did
Study server setup is complete and access was verified.
- Created Info with
#rulesand#announcements. Everyone can view them but cannot post; Moderator can post. - Created Study with
#general,#resources, and thestudy-roomvoice channel, open to everyone. - Created Staff with
#staff-chat, visible only to Moderator and server admins. - Created the Moderator role. It currently has no members; assign it to your moderators to give them the access above.
The access check passed: unverified members can see Info, the study channels, and the two info channels, but not Staff or #staff-chat. Moderators can see all the new channels and can post in Info. Existing content was left unchanged.
The new channels, afterwards
Who can see and post
- Info · rules, announcementsEveryone reads, Moderator posts
- Study · general, resources, study-roomOpen to everyone
- Staff · staff-chatPrivate to Moderator
- New roleModerator
Light tier · 1 message · 84 seconds · 90K tokens
Recorded on a Bond test server on the Light tier, the tier every free plan runs on. Server, channel and member IDs are placeholders, the test bot is shown as Bond, and the steps where Bond loads its own tools or pages through a long result are left out. The test server has no plan limits, so the plan limits a step reports are left out.
Bond showed its plan first. The recording pressed Build it, then Allow on every card after that, Confirm on the one that let Moderator into Staff, and never Always allow. Bond's first try at the Staff category left its own role out, so that step was refused before anything was created, and Bond asked again with its role added. The test server already had the #general every new server starts with. Bond left it where it was and made a second #general inside Study, as its plan said.
The permissions it takes.
Bond checks every step against your own Discord permissions and role position before it acts, and what it reads back is only what you can already see.
What you need
- List channelsNothing extra
- List rolesNothing extra
- Ask questionsNothing extra
- Create categoryManage Channels
- Bulk create channelsManage Channels
- Create roleManage Roles
- Set channel permissionsManage Roles in that channel
- Check channel accessManage Roles
What Bond needs
- Manage Channels to create categories and channels, and Manage Roles to create roles and set who can see and post where.
- Bond creates new roles below its own highest role. It cannot place a role above itself or give a role permissions it does not hold.
- A private area has to let Bond's role in as well, or Bond could not build inside it or fix it later. Bond adds its own role when it makes an area private, as it did for Staff in this run.
- It never needs Administrator, and it checks every change against your own permissions too.
What to watch for.
- Approving the plan is not the last question. Bond still asks before each kind of change, such as a new category, a new role or a permission change, and Always allow on a card stops it asking about that kind. Opening up a place it just made private always asks.
- Bond creates up to 20 channels in one step, so a bigger build takes a few steps under the same plan.
- A private area is private from the moment it is created: Bond makes the staff category with its permissions in place rather than locking it afterwards.
- Bond builds beside what the server already has. Name a channel you want used or moved, such as your own #general, or you may get a second one.
- The new moderator role starts with no permissions of its own and no members. Give it to your moderators, or they cannot post in the read-only channels.
- Bond keeps track of each part of the plan as it lands, and does not call the build done while a part is missing.
Questions people ask.
Will Bond delete my existing channels?
No. Setting up adds and changes, and a delete only happens after you confirm the exact channel or category Bond names.
Can I undo the changes?
Bond keeps a record of the channel permissions it changed and can put them back exactly as they were. New channels and roles can be removed by asking, each delete confirmed by name.
Does Bond need Administrator?
No. Every action maps to one Discord permission, and Bond's invite asks for those rather than Administrator. It also checks that you hold the permission for each change you ask for.
Why not use a server template?
A Discord server template copies a whole layout into a new server in one click, and that is the fastest start for an empty server. Bond is for the server you already run: it changes it in place, keeps your members and history, and can make the same kind of change again six months later.
Is it free?
Yes. Every tool works on the free plan, and a build uses tokens from your weekly allowance. A free account gets 600K tokens a week.
Ask for it in your own words.
Free to start. Bond never needs Administrator, and it shows you what it is about to change before it changes it.