A blueprint is one file that describes a Discord server: its roles and channels, and how each Packet feature is set up. This page explains every part of it, with 41 worked examples you can copy. Rather not write JSON? Configure sets up the same features with forms, and the Guide explains each one.
01 How to use an example
Copy it, name it, preview it.
Open your server on the dashboard and choose Blueprint.
In the side panel, open Snippets, then Features, and press Insert on the example you want. Or paste one you copied here into your blueprint.
Change the channel and role names to match your server, then preview the plan before you apply.
Names in an example, like welcome or Moderator, are matched against your server when you apply. If one is missing, that setting waits until it exists, and the plan tells you.
Leave a setting out and an additive apply keeps what your server has now. To switch a feature off, set "enabled": false.
02 Packet's features
Every feature, worked out.
Each block goes under packet in your blueprint. Jump to a group:
Welcome and the way in
Greet new members, keep the rules in view, and see who invited whom.
packet.greeter
object
Welcome, goodbye and ban messages, and an optional welcome DM.
Welcome card with an embed
Greets each new member in #welcome with a picture card and an embed, and says goodbye when someone leaves.
{"packet":{"greeter":{"welcome":{"enabled":true,"channel":"welcome","content":"Welcome {user.mention}!","card":true,"embed":{"title":"Welcome to {server}!","description":"You are our {memberCount.ordinal} member. Read #rules, then pick your roles in #get-roles.","color":"#5865F2","thumbnailUrl":"{user.avatar}","footer":{"text":"Member #{memberCount}"},"timestamp":true}},"goodbye":{"enabled":true,"channel":"welcome","content":"**{user.tag}** has left the server."}}}}
Rules panel and a welcome DM
Keeps a pinned rules post in #rules up to date on every apply, and sends each new member a short DM.
{"packet":{"greeter":{"panel":{"enabled":true,"channel":"rules","pin":true,"embed":{"title":"{server} rules","description":"1. Be kind.\n2. No spam or ads.\n3. Keep things in the right channel.\n4. Follow Discord's Terms of Service.","color":"#ED4245"}},"welcomeDm":{"enabled":true,"content":"Thanks for joining **{server}**! Pick your roles in #get-roles to get started."}}}}
packet.invites
object
Tracks which invite each member joined with.
Invite tracking with rewards
Tracks which invite each member joined with, and gives a role at 5 and 25 invites.
Roles members pick themselves, roles given on join, and roles that follow what members are doing.
packet.roleCaller
object
Self-serve role pickers, roles given on join, sticky roles and temporary roles.
Role picker and an auto-role
Posts a button picker in #get-roles for platform and ping roles, and gives every new member the Member role.
{"packet":{"roleCaller":{"enabled":true,"pickers":[{"id":"platforms","channel":"get-roles","title":"Pick your platform and pings","description":"Click a button to add or remove a role.","style":"buttons","mode":"toggle","options":[{"role":"PC","emoji":"๐ฅ๏ธ"},{"role":"Console","emoji":"๐ฎ"},{"role":"Event Pings","emoji":"๐"}]}],"autoRole":{"roles":["Member"]}}}}
Member verification
New members press a button in #verify to get the Verified role, and the welcome waits until they do.
Events, giveaways, forms, polls, posts on a schedule and the small tools that keep a server lively.
packet.events
object
Your server events in Discord: each one set up once, its next date kept listed, with an optional reminder.
Weekly game night with a waitlist
Lists a game night every Friday in Discord, takes 20 sign-ups with a waitlist, and reminds them 30 minutes before.
{"packet":{"events":{"enabled":true,"timezone":"America/New_York","events":[{"id":"game-night","name":"Game night","description":"Bring a friend. We pick the games on the night.","repeat":"weekly","weekday":"friday","time":"20:00","durationMinutes":120,"channel":"game-night-vc","reminder":{"minutesBefore":30,"dm":true},"rsvp":{"enabled":true,"limit":20,"waitlist":true,"channel":"events"}}]}}}
Tournament with teams and a bracket
Takes 40 sign-ups for a monthly tournament, draws eight teams of 5 and runs a single-elimination bracket.
Forms members fill with an Apply button, reviewed by staff with Accept and Deny.
Staff application
Posts an Apply button in #apply. Answers go to #applications, and Accept gives the Trial Moderator role.
{"packet":{"forms":{"enabled":true,"forms":[{"id":"staff-application","title":"Staff application","description":"Want to help run the server? Tell us a little about yourself.","buttonLabel":"Apply","channel":"apply","reviewChannel":"applications","questions":[{"label":"How old are you?","type":"short"},{"label":"Why do you want to help?","type":"paragraph"},{"label":"What time zone are you in?","type":"short","required":false}],"acceptRole":"Trial Moderator","reviewerRoles":["Admin"],"cooldownDays":14}]}}}
packet.forums
list
Managed forums: polls that pick the best posts, a first post, rewards and suggestions.
Weekly suggestion poll
Each week ranks the top posts in the #suggestions forum, opens a poll in #general and pins the winner.
{"packet":{"forums":[{"enabled":true,"forum":"suggestions","pollChannel":"general","intervalHours":168,"topN":3,"rankBy":"reactions_plus_replies","pollDurationHours":72,"pollMessage":"Vote on this week's top suggestions!","pinWinner":true,"firstPost":{"enabled":true,"title":"How suggestions work","content":"One idea per post. Each week the top posts go to a poll, and the winner is pinned for staff.","pin":true,"lock":true}}]}}
packet.scheduledMessages
list
Messages Packet posts on a schedule, once or on repeat.
Weekly announcement
Posts a reminder in #announcements every Monday at 9:00 New York time.
{"packet":{"scheduledMessages":[{"id":"weekly-reminder","channel":"announcements","content":"New week! Check #events for what is on, and say hi in #general.","schedule":{"kind":"calendar","times":["09:00"],"daysOfWeek":[1],"timezone":"America/New_York"}}]}}
Question of the day
Asks one question a day in #general, from your list first and then from Packet's starter questions.
{"packet":{"scheduledMessages":[{"id":"daily-question","channel":"general","content":"Question of the day: {question}","schedule":{"kind":"calendar","times":["17:00"],"timezone":"UTC"},"questions":{"list":["What game are you playing this week?","What is the best snack for a long session?"],"starter":true}}]}}
The Daily Word, every day
Posts the Daily Word in #games every day at 18:00 New York time, with yesterday's word and who solved it. The word changes when it posts.
{"packet":{"scheduledMessages":[{"id":"daily-word","channel":"games","content":"A new Daily Word is up.","schedule":{"kind":"calendar","times":["18:00"],"timezone":"America/New_York"},"daily":{"kind":"dailyWord","names":true}}]}}
packet.customCommands
list
Your own slash commands for this server.
A /rules command
Adds a /rules command that shows the server rules to whoever runs it.
{"packet":{"customCommands":[{"id":"rules","name":"rules","description":"Show the server rules","type":"leaf","response":{"content":"Please read the rules before you post.","embed":{"title":"Server rules","description":"1. Be kind.\n2. No spam or ads.\n3. Keep things in the right channel.","color":"#5865F2"},"ephemeral":true}}]}}
packet.birthdays
object
The /birthday command: a birthday message, a role for the day and a time zone.
Birthdays
Members save their birthday with /birthday. On the day, Packet posts in #general and gives the Birthday role.
Channels where Packet publishes, reacts to or opens a thread on each new message, or keeps a sticky message at the bottom.
Auto-threads and a sticky message
Opens a thread on every post in #showcase, adds a reaction, and keeps a note at the bottom of #general.
{"packet":{"channelAutomation":{"enabled":true,"rules":[{"channel":"showcase","reactions":["๐ฅ"],"thread":{"name":"{user}'s post"}},{"channel":"general","sticky":{"content":"New here? Pick your roles in #get-roles."}}]}}}
packet.autoDelete
object
Deletes messages in the channels you pick, a set time after they are sent.
Clear a channel after a day
Deletes messages in #bot-commands a day after they are sent, and keeps pinned messages.
A post in a channel you pick when a member shares their screen in a voice channel everyone can see, edited when the stream ends, and an optional list of who is live now.
Screen shares in voice
Posts in #live-now when a member shares their screen in a public voice channel, and keeps a list of who is live.
{"packet":{"liveInVoice":{"enabled":true,"rules":[{"id":"everywhere","scope":"any","channel":"live-now","content":"{user} is live in {channel}."}],"onEnd":"edit","boardChannel":"live-now"}}}
packet.gameServers
list
Live status, schedule and join info boards for your game servers.
Game server status board
Keeps a live status board for a Palworld server in #server-status. Change the address and port to yours.
Posts when a creator goes live or uploads, and Packet's own news.
packet.socialAlerts
list
Announcements when a creator you follow goes live or posts.
Twitch go-live with a Live role
Announces in #live when the channel goes live, pings Stream Pings, and gives the streamer a Live role meanwhile. Put the streamer's Discord user id in liveMember.
{"packet":{"socialAlerts":[{"id":"twitch-live","platform":"twitch","source":"yourchannel","channel":"live","event":"live","style":"card","content":"{creator} is live: {title}","mentionRole":"Stream Pings","liveRole":"Live","liveMember":"300000000000000051"}]}}
New YouTube videos
Posts each new video from a YouTube channel in #videos. Put your channel id in source.
Ticket desks, cases and protections, a server log and a weekly summary for staff.
packet.tickets
object
Support panels that open private, staff-only ticket channels.
Two ticket desks
A help desk for Support staff and a report desk for Moderators, each opening a private ticket with a short form and saving a transcript.
{"packet":{"tickets":{"enabled":true,"panels":[{"id":"help-desk","channel":"get-help","title":"Need help?","description":"Open a ticket and the support team will get back to you. Only you and staff can see it.","buttonLabel":"Get help","buttonEmoji":"๐ซ","ticketCategory":"Help tickets","staffRoles":["Support"],"openMessage":{"content":"Thanks {opener}, someone will be with you shortly."},"formFields":[{"label":"What do you need help with?","placeholder":"One line is plenty","required":true}],"transcripts":{"enabled":true,"channel":"ticket-transcripts"}},{"id":"report-desk","channel":"report","title":"Report a member","description":"Tell the moderators what happened. Your report stays private.","buttonLabel":"Make a report","buttonEmoji":"๐ฉ","ticketCategory":"Reports","staffRoles":["Moderator"],"defaultPriority":"high","formFields":[{"label":"Who are you reporting?","required":true},{"label":"What happened?","paragraph":true,"required":true}],"transcripts":{"enabled":true,"channel":"ticket-transcripts"}}],"logChannel":"ticket-log"}}}
packet.moderation
object
Warn, mute, kick and ban commands with case history and escalation.
Warnings that escalate
Turns on /mod cases. Three warnings mean a one-hour timeout, five a day, and seven a kick. Staff are never counted.
The top-level parts of a blueprint, in the order they are written. Only meta is required.
meta
required
Identity: name, schema version, and what kind of document it is.
Every blueprint declares its name (any string) and its schema version (1.4.0 is the current one). It can also carry a description, an author, free-form tags, and a kind: server for a whole server (the default when kind is left out) or addon for a part of one. The Document type switch above sets kind for you. A blueprint written for an older schema version is migrated forward when it loads.
{"meta":{"name":"gaming-hub","schemaVersion":"1.4.0","description":"Multi-game community hub","author":"alice","tags":["gaming","community","starter"]}}
An add-on
A part of a server, added to one that already exists.
The current schema version is 1.4.0. An older version still loads, because Packet migrates it forward. A newer one is refused.
An add-on only ever adds. It never removes anything you did not ask it to, so it is applied additively.
When you rename a blueprint via the dashboard, meta.name follows automatically. Don't skew them apart by editing the JSON directly.
server
optional
Guild-level settings: verification, AFK, system flags, community.
Mirrors Discord's Server Settings tab. Verification level, default notification setting, explicit content filter, system channel flags, and the "system" channel pointers (system, rules, public-updates, AFK, safety alerts). Setting community.enabled: true toggles the COMMUNITY feature; rules + public-updates channels become required when it's on.
rulesChannel and publicUpdatesChannel MUST point at channel names that exist in channels[] or categories[].children[] when community.enabled: true. Discord rejects Community without them.
The verificationLevel enum is none | low | medium | high | very_high โ lowercase, underscores between words.
System channel pointers are blueprint channel NAMES (not snowflakes). The bot resolves them to IDs at apply time.
permissionPresets
optional
Named groups of permission flags, referenced as `preset:<name>`.
Sugar over raw flag arrays. Define a preset once, reference it from any role's permissions array or any channel/category overwrite's allow/deny. Presets expand at apply time; Discord never sees them.
Reference syntax is preset:<name>, not @<name> or $<name>.
A preset can't reference another preset (no recursion). Inline what you need.
Names must be alphanumeric with - and _ only โ no spaces.
roles
optional
Role hierarchy, top-down (index 0 = highest).
Each entry has a name, optional color, hoist (separate sidebar group), mentionable, and a permissions array. The order in the array *is* the role-list order on Discord โ index 0 sits highest. @everyone is implicit and never appears here.
Permission flag names are PascalCase: ManageChannels, not MANAGE_CHANNELS.
The bot's own role must sit ABOVE every blueprint role on the live server, otherwise role moves and deletes fail mid-apply with "Missing Permissions". Drag it to the top of Server Settings โ Roles.
Don't declare @everyone here โ reference it only inside permission overwrites as role: "@everyone".
categories
optional
Channel categories with permission overwrites.
Discord channel categories. Each has a name, optional position, permission overwrites, and either inline children (channel definitions nested for compactness) or no children (channels reference the category by name in the top-level channels[] array). Both shapes are equivalent โ the loader normalizes nested children into the flat channels[] form before validation.
Plain category
Just a bucket. Channels point at it via category:.
Category names are unique guild-wide. Two categories with the same name will fail validation.
Channel names are unique *per category* (Discord allows info in Rust AND info in ARK as separate channels). The engine handles this with composite identity.
channels
optional
Channels at the top level. Discriminated by `type`: text | announcement | voice | stage | forum | media.
Each channel has a type discriminator and shape-specific fields. Use category: "<name>" to nest under a category. Voice channels carry bitrate and userLimit; forum/media carry availableTags; text, voice, stage, forum and media carry slowmode. Announcement and stage channels require a fully-configured Community server (server.community.enabled: true plus rulesChannel and publicUpdatesChannel). Text, voice, and forum channels work on every server. Media channels are not creatable via the API on any guild โ use forum instead for the same gallery/tag behavior.
Text channel
Plain text channel inside a category.
{"channels":[{"type":"text","name":"general","topic":"Main community chat.","category":"Community","nsfw":false,"permissionOverwrites":[],"slowmode":0}]}
Threaded discussion. Tags can be moderated: true so only mods can apply them.
{"type":"forum","name":"ideas","topic":"Pitch ideas โ one thread per idea.","category":"Community","permissionOverwrites":[],"slowmode":0,"availableTags":[{"name":"QoL","moderated":false},{"name":"Planned","moderated":true}]}
Good to know
availableTags is only valid on type: forum. Tags on text/voice/announcement/stage channels are a schema error.
**Forum channels work on every server** โ they do NOT require Community. (Common misconception โ forums were Community-only when Discord launched them in 2022 but have been generally available since.)
**Announcement and stage channels require Community.** Set server.community.enabled: true plus rulesChannel and publicUpdatesChannel. Without all three, the create fails.
**Media channels (type: media) are not creatable via the API on any server** โ Discord refuses with 50024 regardless of Community state. Use type: forum instead; forum supports the same gallery + tag + sort behavior and works everywhere.
defaultAutoArchiveDuration accepts only 60 | 1440 | 4320 | 10080 (minutes) or omitted. null is not valid โ Discord returns null for unset, but blueprints should leave the field out.
Channel position within a category is determined by order in the array, not an explicit position field.
content
optional
Channel topics and pinned messages.
Per-channel content the engine writes alongside structure: channel topics and pinned messages. References channels by name; the engine resolves them at apply time. A forum has no plain messages, so its pinned post is its first post, a thread set under packet.forums (Configure โ Forums).
Topics + pins
Common rules-channel pattern.
{"content":{"channels":[{"channel":"rules","topic":"Read these before chatting.","pinnedMessages":["Be kind. No NSFW. No real-money trading."]}]}}
A forum's first post
Pin a "how to use this" thread at the top of a forum.
{"packet":{"forums":[{"forum":"ideas","enabled":false,"firstPost":{"enabled":true,"title":"How to write a good idea post","content":"Be specific. Include context."}}]}}
Good to know
Pinned messages re-send on every apply if the engine can't fingerprint them. Avoid heavy edits to existing content.channels entries during iteration.
Channel name lookup in content.channels[] matches the FIRST channel of that name in channels[]. If you have duplicate names across categories, content goes to whichever appears first.
Pinned messages can't go in a forum or media channel: Discord has no plain messages there, so the plan refuses them. Give a forum a first post instead.
A pinned message can be up to 1,971 characters. Packet adds a 29-character marker to every message it posts so it can find it again, and Discord takes 2,000. #channel and @role names become longer links when sent, so leave a little room.
content.forumStarterPosts is retired: Packet no longer posts it, and the plan refuses a blueprint that still has one. Put its text in the forum's first post and remove it.
onboarding
optional
Onboarding wizard prompts and default channels.
Discord's server onboarding flow. Set enabled: true and mode: default | advanced, then list default channels (channel names from channels[]) and prompts. Each prompt is multiple_choice or dropdown with options that grant roles and/or unlock channels.
Game-picker prompt
Onboarding multi-select that hands out game roles.
{"onboarding":{"enabled":true,"mode":"advanced","defaultChannels":["welcome","rules","general"],"prompts":[{"type":"multiple_choice","title":"Which games do you play?","required":false,"inOnboarding":true,"singleSelect":false,"options":[{"title":"Minecraft","roles":["Minecraft"]},{"title":"Rust","roles":["Rust"]}]}]}}
Good to know
Onboarding requires Community to be enabled. The preflight catches this; double-check server.community.enabled: true is set if onboarding.enabled: true.
Prompt option roles and channels reference names โ they must exist in roles[] and channels[] respectively or apply fails name-resolution.
welcomeScreen
optional
The Welcome Screen new members see: a blurb and shortcuts to channels.
The panel a new member sees when they join through an invite. It is not the onboarding wizard. enabled turns it on, description is the blurb at the top (up to 140 characters), and channels[] holds up to 5 shortcuts. Each shortcut names a channel from your blueprint, a short description (up to 50 characters) and an optional emoji. Your server needs Community on.
A welcome screen
A blurb and two shortcuts.
{"welcomeScreen":{"enabled":true,"description":"A friendly place to play and plan together.","channels":[{"channel":"rules","description":"Read these first","emoji":"๐"},{"channel":"general","description":"Say hello","emoji":"๐"}]}}
Good to know
It needs server.community.enabled: true. Discord refuses a Welcome Screen on a server without Community.
A shortcut's channel is a channel NAME from this blueprint, not an id. The bot resolves it when you apply.
A shortcut's emoji is a Unicode emoji or a custom one written <:name:id>.
widget
optional
The public server widget: on or off, and where its invite points.
The embeddable widget that shows your member count and an invite. enabled turns it on. channel names the channel its instant invite points at (any channel type, by name). Leave channel out for no invite. It works on any server, with or without Community.
A widget with an invite
On, with the invite pointing at your welcome channel.
{"widget":{"enabled":true,"channel":"welcome"}}
Good to know
channel is a channel NAME from this blueprint, not an id. The bot resolves it when you apply.
assets
optional
Custom emoji + stickers โ referenced by name, or uploaded.
Server emoji and stickers. Each entry is referenced BY NAME: with no image, it points at the existing server emoji/sticker (Packet never holds the file, a full-mirror won't delete it, and a snapshot round-trips it). Add an image only if you want Packet to UPLOAD/create it: the image itself as a data:image/png;base64,โฆ value. Links and file paths are refused. A snapshot of a live server captures emoji + stickers as name-only references.
Reference existing emoji + stickers
Name-only โ Packet keeps these, never uploads or deletes them.
An image-less entry references an emoji that must already exist on the server โ Packet can't create it without an image, so on a fresh server it simply won't appear until you upload it.
Packet only adds emoji and stickers. It never renames, replaces or deletes one, in any apply mode, so leaving one out of assets keeps it on the server.
An emoji image is PNG, JPEG, GIF, WebP or AVIF, up to 256 KB. A sticker image is PNG or GIF, still or animated, up to 512 KB.
automod
optional
AutoMod rules: what to catch, who is exempt, and what happens.
Discord AutoMod rules. Each rule has a name, a type, enabled, exemptRoles, exemptChannels and at least one action. The actions are block_message, send_alert, timeout, block_member_interaction. Each kind of rule has fields of its own, such as keywords, a preset list or a mention limit. The kinds are listed below, with how many of each Discord lets a server have.
Rule kinds (6)
keywordBlocks messages containing your words/phrases (or regex). Up to 6 of these per server.
keyword_presetBlocks Discord's built-in wordlists (profanity / sexual content / slurs). One per server.
spamBlocks generic spam using Discord's heuristics. One per server.
mention_spamBlocks messages with more mentions than your limit. One per server.
member_profileQuarantines a member whose name/profile matches your words. One per server.
linknot creatableDiscord removed this trigger โ it can no longer be created. Remove it, or use a keyword rule with URL patterns / the spam rule.
A keyword rule
Blocks messages with an invite link and says why.
{"automod":{"rules":[{"type":"keyword","name":"No invite links","keywords":["*discord.gg/*"],"actions":[{"type":"block_message","customMessage":"Invite links are not allowed here."}]}]}}
A mention limit
Blocks a message that mentions more than 8 people or roles.
States that the server should have none. A full apply removes the rules it has. To leave AutoMod alone, leave the automod block out.
{"automod":{"rules":[]}}
Good to know
Discord decides which actions a kind of rule may carry. A combination it refuses is reported when you apply, not when you save.
In a full apply, a rule that is missing from automod.rules is removed from the server. An additive apply never removes one, and a blueprint with no automod block leaves AutoMod alone. While Community is on, Discord will not let the mention-spam rule be removed.
exemptRoles, exemptChannels and an alert's channel are NAMES from this blueprint, not ids.
packet
optional
Packet features: 34 blocks, each a feature you switch on and set up.
Packet's own features, configured inside the blueprint. Each block under packet is one feature, written as an object or as a list (the tag after each name says which). They are all listed below, and the Role Caller has the worked example. roleCaller.pickers[] are self-serve role-picker messages Packet posts and keeps in sync, each listing options that members toggle via buttons (style: "buttons") or a dropdown (style: "dropdown"); mode: "toggle" lets them pick any, "single" makes the options mutually exclusive. An option references a blueprint role by name and may carry a label and an emoji. The emoji is either a Unicode glyph ("๐ฉ") or a Discord CUSTOM emoji as the resolvable <:name:id> (animated: <a:name:id>); the Configure editor's emoji picker has a "Server" tab that inserts the right <:name:id> for you. roleCaller.autoRole.roles[] lists roles given to every member on join.
Every feature block is listed under Packet's features above, with worked examples.
Role picker + auto-role
A button picker with a Unicode and a custom emoji, plus an auto-role on join.
{"packet":{"roleCaller":{"enabled":true,"pickers":[{"channel":"roles","title":"Choose your games","description":"Click a button to add or remove a role.","style":"buttons","mode":"toggle","options":[{"role":"Minecraft","emoji":"๐ฉ"},{"role":"Rust","label":"Rustacean","emoji":"<:rust:123456789012345678>"}]}],"autoRole":{"roles":["Member"]}}}}
Switch a feature off
Say enabled: false to switch a block off. Leaving the block out does not: an additive apply keeps what the server has.
{"packet":{"tickets":{"enabled":false}}}
Good to know
Leave a block or a setting out and an additive apply keeps what the server has now. A full apply puts it back to its default. To switch a feature off, say enabled: false.
A name in a packet setting (a picker's channel, an option's role) can point at something this blueprint does not declare. Packet matches these by name against your server when you apply. If a name is not there, that one setting stays off until it is, and the rest of the blueprint applies normally. The plan page checks each one against your server before you apply.
A custom emoji can be the server emoji's NAME (e.g. rust), which Packet resolves to that server's emoji at apply time, or the explicit <:name:id> resolvable (<a:name:id> for animated). The Configure editor's emoji picker inserts the <:name:id> form; a bare name keeps a blueprint portable across servers.
A picker hosts on a text channel; Packet posts the message there and edits it in place on each apply.
optionalFeatures
optional
Sections a template offers as checkboxes.
Used by templates. Each entry is a named section (an id, a label, an optional description, recommended, and an exclusiveGroup for either-or choices) that carries the same kinds of content a blueprint holds: roles, categories, channels, permission presets and packet blocks. A person ticks the sections they want before the blueprint is created, and the ticked ones are folded in. A blueprint made that way does not keep this list.
A template section
A support desk the person can tick, pre-ticked.
{"optionalFeatures":[{"id":"support-desk","label":"Support desk","description":"A support category with a channel to ask for help.","recommended":true,"categories":[{"name":"Support","children":[{"type":"text","name":"get-support"}]}]}]}
Good to know
Most blueprints do not need this. It only matters when you are building a template.
An id uses lowercase letters, digits and hyphens.
Sections that share an exclusiveGroup are either-or: at most one can be ticked, and ticking none is fine.