A better server.
One change at a time.

Your first few minutes.

1. Sign in with Discord

   Use the account that owns your server. Your dashboard shows servers where you are the current owner.

2. Invite Forge

   Choose Invite Forge next to your server. Forge currently needs Administrator to build and manage your approved setup. On joining, Forge posts a short getting-started guide with an introduction video in a channel it can use. If file uploads are restricted, it links to the video instead.

3. Move Forge’s role up

   In Discord, open Server Settings → Roles. Place Forge above the ordinary roles you want it to manage. It cannot change integration roles or roles above its own.

4. Open Studio

   Return to your dashboard, refresh Discord if needed, and choose Open Studio. Pick a mode and start with a draft.

A small change or a fresh start.

A Full Rebuild is unavailable when a Community server has designated rules or updates channels. Use Add / Edit to keep those channels.

Build your draft, piece by piece.

Structure

Add text or voice channels, organise categories and drag items into order. In Add / Edit, select an existing channel to mark it for removal.

Themes

Choose a starting look or layout. Review the draft afterwards: a layout theme may add channels and roles.

Roles

Create roles, choose colours and set permissions. Keep powerful roles for people you trust. Use Forge AI to propose edits to existing roles.

Permissions

Set @everyone defaults, then choose a channel and role to control access. Presets help with public chat, read-only channels, private staff rooms and voice.

Embeds & modules

Edit the messages Forge posts and choose the bot features your community needs.

Undo and Redo help you adjust your draft. Drafts and recent activity are saved in this browser, so a different device will not have the same local history.

Give members the access they need.

The @everyone role is the baseline for every member. On each confirmed build, Forge removes mass mentions, administrator access, moderation powers and server-management permissions from this role. It also removes dangerous explicit @everyone allows on existing channels.

In Permissions → @everyone, you can keep, enable or disable everyday access such as sending messages, creating invites and uploading files. Your choices appear in Review before they are applied.

Discord’s permissions guide ↗

Say what you want to change.

Describe the result in plain language. Forge AI prepares a proposal for your current mode. Inspect it, accept it into your draft or reject it, then review the final build.

Be specific about existing channels and roles. AI can make mistakes, so check names, permissions and the proposed changes before accepting.

Describe the access you want.

Try: “Create a VIP Lounge voice channel everyone can see, but only members with the VIP role can join. Create the role if it is missing.” You can also ask for private staff channels, read-only announcements, or different speaking and streaming rules for each room.

Forge AI reads current role and channel permissions and prepares a draft. The preview and Review & Build list the proposed access rules. Existing roles are reused. For an “only these roles” rule, Forge clears conflicting role and member overrides for that permission while preserving unrelated settings.

Server owners and administrators bypass Discord channel restrictions. Category changes cover synced channels; ask for individual channel changes when you want the whole category covered. Nothing is applied until you accept, review and confirm the build.

Personalise welcome messages.

Use {server} for your server name and {user} or {@user} for the member. In an embed title, {user} shows their display name. In a welcome message body it becomes a mention. Goodbye messages use their display name. Use {#rules} to link to your rules channel in the body; titles show its readable name. Styled Unicode channel names can be referenced with their plain spelling. For duplicate channel names, use {#CHANNEL_ID}. Missing or ambiguous channels appear as plain #names instead of a guessed link.

Styled channel and role names.

Ask Forge AI to use a Unicode style, such as “Make my text channel names monospace like 𝚌𝚑𝚊𝚝” or “Make the Moderator role bold.” You can also paste the exact name you want. Supported styles include monospace, bold, italic, bold italic, sans, sans bold and double struck. Ask for plain text to remove those styles.

You can refer to 𝚌𝚑𝚊𝚝 as “chat” in later requests. Include the category or channel ID when several channels share that name. Styling stays in place during unrelated edits. Discord uses Unicode characters rather than uploaded font files, and their appearance can vary by device. Review the names in your draft before building.

Choose what your server needs.

Studio shows when a feature is unavailable. Member events and counting depend on Forge’s Discord access. Server owners do not need to create their own bot or configure hosting.

Put modules where you want them.

Open Modules, enable a feature and choose its destination. In Add / Edit you can select an existing text or voice channel, or name one for Forge to create. Reaction Roles use the selected channel for the role message; Tickets use it for the open-ticket button. Private ticket conversations still get separate channels. Read the destination permission note, then Review & Build.

Message logs record edits, deletions and bulk deletions in a staff channel. Setup hides the chosen channel from @everyone; other role access is kept, so review which roles can view it. Available message text is a separate option, off by default. Forge cannot recover uncached deleted messages or identify who deleted them. Logs remain in Discord until staff delete them. Turning off a module stops its automation and keeps its channel.

Developer announcements.

Forge creates a public, read-only #forge-announcements channel for product updates, maintenance notices and service announcements. It starts enabled for new and existing servers, with one automated setup message.

Open Modules → Developer announcements to choose another channel, select the types you want, or turn announcements off. Click Save preferences to apply these settings. No server build is needed. Forge needs permission to view the channel, send messages and read recent history.

Reuse a backup or template.

Structure → Backups & templates lets you download a structural backup, export your current draft or import a Forge JSON file up to 200 KB. Preview the import notes before choosing Use imported draft. Undo restores your previous draft. Review & Build is still required to change Discord.

Structural backups import into Add / Edit, preserving extra current channels. Supported text/voice channels and ordinary roles can be recreated or matched by original IDs. Message history, member role assignments, integration roles, category-only overrides and advanced channel settings are not restored. Unsupported items are reported. Templates with live Discord IDs belong to that server; templates containing only planned structure can be reused elsewhere.

Check it. Confirm it. Build it.

1. Review the changes

   Check added and removed channels, roles, permissions and safety notices. Resolve any role-hierarchy warning.

2. Save a backup for Full Rebuild

   Download a fresh structural backup, then enter the exact confirmation phrase. A structural backup records the server layout; it cannot recover deleted messages.

3. Follow the build

   Forge shows progress as changes are applied. If you cancel, it stops at the next checkpoint. Changes already made remain in Discord.

When Forge updates.

After a deployment, Forge signs you out and asks you to sign back in. Open pages show a short update screen. Your saved drafts stay on this device. If your browser cannot save your latest draft, download it from the update screen before continuing. A build that was already running needs checking after sign-in before you start another.

Common questions.