Start Your Server turns a plain-language description into a complete Discord server plan, lets you review the channels, roles, permissions, content, and YourBot services visually, then applies only the changes you approve. It works for a new community, an existing server that needs organization, or a migration that should be staged beside the current setup.

The best results come from explaining who the server serves, what members should do after joining, which roles need private access, which activities happen repeatedly, and what must remain untouched.

This guide covers the full workflow and includes practical builds for a World of Warcraft guild, a college study group, and an automotive hobby community.

Editorial disclosure: This guide is published by YourBot.gg and reflects the current Start Your Server product and documentation. The live layout preview is always the source of truth before a build.

What Start Your Server Can Build

Start Your Server can prepare:

The workflow is:

1. Describe the community or start from a template.
2. Review the proposed Channels, Roles, and Services.
3. Build the checked changes live, with a pre-build snapshot, progress log, report, and structural undo.

Nothing is applied merely because the AI proposed it.

Before You Start

Only the server owner can open it

Start Your Server is owner-only because it can restructure the entire server. Moderators and managers cannot be granted access to the builder.

Confirm the bot and permissions

The bot needs at least View Channels to inspect the current layout and generally needs Manage Channels plus Manage Roles to build.

Discord only lets a bot manage roles below its highest role. Review Discord’s role hierarchy and place the bot above every role it must create, assign, or change.

Check the building as @bot badge. If the server uses a connected custom bot identity, that application—not another YourBot identity—is the bot that needs access.

Hidden channels and roles above the bot may fail without broader permissions. The build report identifies the blocked item and explains why.

Define the type of project

State whether you are creating, reorganizing, or migrating:

Create a new server for...

Reorganize this existing server while preserving...

Stage a replacement beside our current bot setup. Do not delete anything yet.

For an established community, keep the first build add-only.

How to Write a Strong First Prompt

Include:

• Community purpose and expected size
• What a newcomer should see and do first
• Staff, member, interest, course, region, or activity roles
• Recurring events and support needs
• Private areas and sensitive information
• Permanent versus temporary voice rooms
• YourBot services to prepare
• Existing channels or roles that must remain
• Desired tone and naming style

Use this framework:

Create or reorganize a Discord server for [community and size].

New members should [first actions and access path].
Create roles for [staff, access, and self-selection].
We regularly run [activities].
We need [support, moderation, events, voice, analytics, announcements].
Keep [existing items] and do not [changes to avoid].
Use a [tone] style for names and starter content.

Describe outcomes, not only channel names. “Members should choose their courses and see only the relevant study channels” is more useful than “add three course channels.”

Step 1: Open the Builder and Choose a Starting Point

Sign in with the Discord account that owns the server, select the server in the YourBot dashboard, then open Start Your Server.

You can:

• Write a custom description
• Choose a curated starting template
• Reuse one of Your templates
• Open a shared Community template

Templates remain editable through chat.

When the request is ambiguous, the builder may ask follow-up questions. Answer them instead of starting a new design.

Step 2: Review the Layout Panel, Not Only the Chat

The chat gives a summary. The Channels, Roles, and Services tabs show what will actually be built.

Click each important channel to inspect:

• Category and channel type
• Topic and first message
• Who can view it
• Who can post
• Whether it is new or already exists

Review the role hierarchy and service destinations. For example, a Tickets channel may exist while the service still points to the wrong staff role or log channel.

Large requests can produce an incomplete layout even when the conversational summary sounds complete. Ask for the missing items or split the project into phases:

1. Foundation and onboarding
2. Staff, permissions, and moderation
3. Events, support, voice, and activity areas
4. Specialist channels and final polish

The layout panel is the build specification.

Step 3: Make Direct Edits and Chat-Based Revisions

Hover categories, channels, or roles to rename them, remove them from the proposed design, or move channels between categories.

Use direct edits for small corrections. Use chat when the change affects several parts of the server:

Make every resource channel read-only for members, but writable by Tutor
and Organizer.

Keep one permanent raid voice room and use temporary rooms for all other groups.

Removing something from the proposal does not delete it from Discord.

Step 4: Test Visibility With “See It As”

The See it as picker redraws the design through a selected role.

Preview at least:

• New member with no roles
• Verified member
• Important interest, course, or activity role
• Moderator
• Senior staff role

Check visibility and posting rights. Discord channels can inherit category permissions or use unsynchronized channel overrides, so review Discord’s permissions FAQ when the result is unexpected.

This step catches servers where newcomers see nothing, staff areas leak, or role-selected channels remain inaccessible.

Step 5: Resolve the Safety Check

Every design receives an automatic safety review.

It can flag:

• An empty newcomer experience
• Missing welcome, rules, or moderator areas
• Hidden channels no staff role can access
• A service without a required destination
• Permission problems that would break the workflow

Many findings offer Fix in chat. Review the suggested correction before applying it because a warning may reflect an intentional privacy decision.

Step 6: Review Services and the Build Checklist

The Services tab can connect the Discord structure to supported YourBot workflows, including:

• Tickets panels
• Welcome messages and roles
• Group Finder channels
• Join-to-Create Voice lobbies
• Sentinel moderation
• Announcements

Review each field before building. Start Your Server provides a working foundation; deeper configuration remains available on each service’s dashboard.

Select Review and build to see every planned operation. Uncheck any row you want omitted.

Deletions remain opt-in

The normal build adds and updates. Proposed deletions stay unchecked until you select them and confirm that they are permanent.

Structural undo can recreate deleted channels, categories, and roles, but Discord cannot restore deleted channel messages. Leave deletions disabled until the replacement has been tested.

Optional Discord Community onboarding

When a design includes onboarding, Start Your Server may offer to configure Discord Community mode, default channels, the welcome screen, and starter questions.

That option requires the building bot to have Administrator. You still enable the rules agreement gate manually in Discord because bots cannot complete that step.

Discord’s Community Onboarding can assign channels and roles from member answers, making it useful for course, game, region, and interest selection.

Step 7: Build, Retry Failures, and Read the Report

YourBot applies the approved operations one at a time and displays progress as each lands.

One failed item does not stop the build. The final report explains:

• What succeeded
• What failed and why
• Which service wiring is valid
• Which features are ready to test
• Which items need a finishing step

The most common failures are locked channels and roles above the bot. Correct access or hierarchy, then retry the failed items.

Running the design again is safe: existing work is skipped instead of duplicated.

Step 8: Test, Refine, and Save the Design

After the build:

1. Download the pre-build snapshot.
2. Open each configured service and inspect its settings.
3. Test with non-administrator accounts.
4. Confirm newcomer visibility and role selection.
5. Open and close a test ticket.
6. Create a test event or group listing.
7. Join the temporary-voice lobby and confirm cleanup.
8. Verify staff-only channels remain private.
9. Check scheduled content destinations.
10. Review the build report for incomplete wiring.

You can structurally undo the build, continue the same conversation, and run another build that applies only the differences.

Save a successful design as a reusable template when you operate multiple related communities.

Example 1: World of Warcraft Guild

Scenario

A 120-member World of Warcraft guild runs two weekly raid teams, frequent Mythic+ groups, recruitment, profession coordination, and casual events. Applicants should not see officer planning or raid strategy until accepted.

Copy-ready prompt

Reorganize this existing Discord server for a 120-member World of Warcraft
guild. Keep our current Guild Master, Officer, Raider, Trial, and Social roles.

New arrivals should see a welcome area, rules, guild information,
recruitment instructions, and a private way to contact officers. After
verification, members should choose Tank, Healer, or DPS interests and
opt into Raid Alerts, Mythic+ Alerts, or Social Events.

Create areas for announcements, general chat, screenshots, crafting and
professions, recruitment, two raid teams, Mythic+, strategy, logs and VODs,
and private officer work.

Keep one permanent voice channel for each raid team. Add one Join-to-Create
lobby for Mythic+ and casual groups.

Configure Welcome, Tickets, Beacon Events, Group Finder, Join-to-Create
Voice, Sentinel, Analytics, and Announcements. Do not create a separate
channel for every class.

Do not delete or rename current channels yet. Stage the improved layout
beside the live structure so officers can test it first.

Practical structure

👋 START HERE
├── #welcome
├── #rules
├── #guild-information
├── #recruitment
├── #choose-roles
└── #contact-officers

📣 GUILD NEWS
├── #announcements
├── #raid-calendar
└── #event-updates

💬 COMMUNITY
├── #general
├── #introductions
├── #screenshots
├── #crafting-and-professions
└── #off-topic

⚔️ RAIDING
├── #raid-signups
├── #raid-strategy
├── #logs-and-vods
├── Raid Team One
└── Raid Team Two

🔑 MYTHIC+
├── #mythic-plus-lfg
├── #key-discussion
└── Join to Create

🛡️ OFFICERS
├── #officer-chat
├── #recruitment-review
├── #mod-log
└── Officer Voice

Role and service plan

Use See it as for Applicant, Raider, and Officer. Confirm that applicants cannot see officer or strategy areas and that Raiders can reach the full guild workflow.

Useful follow-ups:

Make #raid-strategy read-only for everyone except Raid Lead and Officer.

Put Tank, Healer, DPS, and notification roles into one Welcome role menu.

Create a private test Group Finder channel before replacing our current LFG.

A later Plugin Builder project could add raid-attendance history, crafting requests, or guild roster workflows.

Example 2: College Study Group

Scenario

A student-run college study community supports Biology 201, Chemistry 101, and Calculus II, with review sessions, peer tutoring, and temporary focus rooms. Students should see only the course areas they select.

Copy-ready prompt

Create a student-run Discord study community for about 80 college students
taking Biology 201, Chemistry 101, and Calculus II.

Make it clear that the server is student-run and is not an official college
service. New members should read the rules and academic-integrity guidance,
then choose one or more course roles before seeing those course channels.

Create a general commons, course discussion and resource channels,
exam-review areas, a tutoring request flow, scheduled study sessions,
and temporary focus rooms.

Roles should include Organizer, Tutor, Verified Student, the three course
roles, and Study Session Alerts. Tutors and organizers need a private area.

Configure Welcome, Tickets, Beacon Events, Join-to-Create Voice, Sentinel,
Announcements, and Analytics. Keep it easy to scan on mobile. Do not collect
grades, student IDs, or private academic records.

Practical structure

📚 START HERE
├── #welcome
├── #rules-and-academic-integrity
├── #how-this-group-works
├── #choose-your-courses
└── #announcements

☕ STUDENT COMMONS
├── #general
├── #introductions
├── #study-tips
└── #campus-resources

🧬 BIOLOGY 201
├── #bio-discussion
├── #bio-resources
└── #bio-exam-review

⚗️ CHEMISTRY 101
├── #chem-discussion
├── #chem-resources
└── #chem-exam-review

📐 CALCULUS II
├── #calc-discussion
├── #calc-resources
└── #calc-exam-review

🗓️ STUDY SESSIONS
├── #session-schedule
├── #request-a-tutor
└── Join a Focus Room

🧑‍🏫 ORGANIZERS
├── #organizer-chat
├── #tutor-coordination
└── #support-log

This example is well suited to Discord Community Onboarding. Course answers can assign the matching roles and channels, while broadly useful channels remain visible to everyone.

Ask for rules covering academic integrity, personal information, recording consent, and the server’s student-run status. Do not automatically assign “Expert” or “Official Tutor” without a real verification process.

Review as:

• New student with no course role
• Biology 201 student
• Tutor or Organizer

Useful follow-ups:

Make course resource channels read-only for students and writable by Tutor
and Organizer.

Create temporary focus rooms with a default limit of six people.

Ask course selection during onboarding, but leave optional interests for later.

A custom peer-tutor matching or scheduled-access workflow can move to the Plugin Builder if the built-in services do not cover it.

Example 3: Automotive Hobby Community

Scenario

A 300-member regional automotive community covers maintenance, modifications, detailing, project builds, local meets, and photography without creating a channel for every manufacturer.

Copy-ready prompt

Create a regional automotive hobby Discord server for about 300 members.

New members should read the community and safety rules, choose their region
and broad vehicle interests, then reach general discussion, technical help,
project updates, meets, and voice chat.

Use broad interest roles such as Domestic, European, Japanese, Classics,
Trucks and Off-Road, and EVs. Use region roles for North, South, East, and
West. Do not create manufacturer-specific channels.

Create private staff channels and an incident-report ticket flow. Add areas
for introductions, show-your-ride posts, diagnostics, maintenance, detailing,
fabrication, wheels and suspension, build logs, events, and photography.

Configure Welcome, Tickets, Beacon Events, Join-to-Create Voice, Sentinel,
Announcements, Analytics, and Social Feeds. Do not encourage members to post
home addresses, VINs, private phone numbers, or personal documents.

Practical structure

🚦 GARAGE ENTRANCE
├── #welcome
├── #rules-and-safety
├── #choose-region-and-interests
├── #announcements
└── #report-an-issue

🏁 COMMUNITY
├── #general
├── #introductions
├── #show-your-ride
├── #automotive-news
└── #off-topic

🔧 TECHNICAL GARAGE
├── #diagnostics
├── #maintenance
├── #detailing
├── #fabrication
├── #wheels-tires-suspension
└── #tools-and-parts

🚘 PROJECTS
├── #build-logs
├── #before-and-after
└── #project-help

📍 MEETS AND EVENTS
├── #upcoming-meets
├── #route-and-weather-updates
├── #event-photos
└── #post-event-recaps

🎙️ VOICE GARAGE
├── Garage Chat
└── Join a Garage Room

🛡️ STAFF
├── #staff-chat
├── #incident-reports
├── #mod-log
└── Staff Voice

Keep roles broad: staff, Verified Member, region, vehicle interest, and event alerts. Do not automatically label someone a professional mechanic, fabricator, or safety expert.

Services can support:

• Welcome: verification, region, vehicle interests, event alerts
• Tickets: private incident and moderation reports
• Beacon Events: meets, cruises, workshops, and photo sessions
• Join-to-Create Voice: temporary garage and troubleshooting rooms
• Sentinel: scam links, repeated advertising, harassment, and raid protection
• Announcements: meet reminders, rules updates, weather changes
• Analytics: identify useful technical and event channels
• Social Feeds: selected YouTube, RSS, status, or community sources

Useful follow-ups:

Make #build-logs use one thread per vehicle project and explain that in the
channel’s first message.

Create a private ticket type for scam reports and event safety concerns.

Show exact private-event details only to Verified Member and the matching
region role.

Possible later plugins include vehicle profile cards, maintenance reminder opt-ins, or meet check-in tracking.

Common Mistakes

• Vague first prompt: Explain the member journey and recurring work.
• Oversized single design: Split foundation, operations, and specialization.
• Trusting the chat summary: The layout panel is what gets built.
• Ignoring the building bot: Check the badge and its role hierarchy.
• Granting Administrator casually: Use it only when the chosen workflow requires it.
• Enabling every service: Activate only what solves a real need.
• Approving deletions during the first pass: Stage, test, then clean up.
• Testing only as owner: Use ordinary member and staff accounts.
• Assuming undo restores messages: It restores structure, not deleted history.
• Stopping after build: Fine-tune each service and test its complete lifecycle.

When to Use the AI Plugin Builder

Start Your Server creates the Discord structure and prepares supported services. Use the AI Plugin Builder when the design reveals a unique need such as:

• WoW raid attendance
• College peer-tutor matching
• Automotive vehicle profiles
• A custom application or approval process
• A specialized external integration

Start Your Server may suggest plugin ideas during review. They are optional next steps, not requirements for a successful build.

Frequently Asked Questions

Can it reorganize an existing server?

Yes. Tell it what must remain, keep deletions disabled, and stage additions beside the current setup.

Can moderators use it?

No. Start Your Server is limited to the server owner.

What permissions does the bot need?

It needs View Channels to inspect the layout and generally needs Manage Channels and Manage Roles to build. Role hierarchy and hidden-channel access still apply. Optional Community onboarding requires Administrator.

Will it delete existing channels?

Not by default. Deletions are unchecked and require explicit confirmation.

Can I undo a build?

Yes, structurally. The pre-build snapshot can recreate categories, channels, roles, settings, and permissions. Deleted messages cannot be restored.

Can I build more than once?

Yes. Repeated builds skip existing items and apply only missing or changed operations.

Does it configure YourBot services?

It can enable and prepare supported services, connect them to channels and roles, and apply editable settings. Use each service dashboard afterward for deeper configuration.

Can it import another bot’s data?

Do not assume so. It can stage replacement structure and YourBot configuration, but provider-specific XP, cases, transcripts, commands, analytics, and other history need separate preservation or a documented importer.

Does designing use AI credits?

The product shows the current estimate before an AI design request is sent. Templates and inline edits can follow different usage rules, so rely on the in-product amount.

Final Verdict

Start Your Server works best as an AI-assisted server architect, not a one-click theme generator.

Give it a clear brief. Review the visual layout, preview real member roles, resolve safety findings, inspect service settings, keep deletions off during the first build, and test every important workflow afterward.

For a World of Warcraft guild, that means recruitment, raid events, LFG, voice, and officer access. For a college study group, it means course-based onboarding, tutoring, sessions, focus rooms, and academic-integrity boundaries. For an automotive hobby group, it means broad interest roles, organized technical channels, event coordination, private reports, and sensible privacy rules.

Open Start Your Server, build the foundation carefully, and use the Plugin Builder only when the community needs a workflow beyond the built-in services.