Building servers for other people
What Q asks before it builds, what it decides for itself, and what it will never decide for you.
If you set servers up for clients, the part of the job worth your time is the judgment: which ranks a community needs, how tight its permissions should be, what its front door does to a stranger. The part that is not worth your time is doing it by hand for the fourth time this month. That split is what Q is for. You decide, Q implements, and you review the whole thing before any of it reaches Discord.
What Q asks before it builds a server
A whole-server request opens with a questions card rather than a plan, because a wrong guess here costs a rebuild. Every row is skippable and a skipped row is answered with a stated default, so you are never blocked, and you always know what was assumed.
- The topic and what the server is for.
- The audience and tone the community should have.
- How names should look. Emoji in channel, category and role names, a separator like โ or ใป, or plain lowercase. When the server already has rooms, Q copies their shape instead of asking.
- How strict the structure is. A tight ladder of ranks with narrow permissions, or a relaxed one with few roles and wide access. The same brief produces two very different servers.
- Which modules to switch on.
- How familiar you are with Discord's own settings. This decides how much Q explains and how much it simply does. Say you build servers professionally and you get the plan without the tutorial.
When the build has a staff ladder, Q also asks whether ranks group into families, for example Junior Mod, Mod and Senior Mod under Moderation, and whether you want separate mention-only roles so announcements never reach for @everyone.
Rank families are positions, not parents
Discord has no role nesting. A family reads as a family only because its roles sit next to each other in the right order, so Q sets role positions as part of the build. Roles it creates are placed below QREATE's own role, because Discord refuses anything above it.
Security means permissions, not just modules
Automod, anti-raid and anti-nuke are the part everyone names. The part that gets missed is @everyone's own permissions, and the one worth raising first is Use External Apps: external applications are a common delivery route for scam spam.
@everyone also stops other bots' slash commands for ordinary members. That is a real trade, it is yours to make, and Q will never apply a server-wide permission change that was not on screen in front of you.What the platform enforces, whatever the plan says
Two rules are applied by the code that builds the server, not by Q's judgment, so they hold on every build:
- A room whose name says it is not for everyone is created closed. Staff, mod, admin, team, log, audit, ticket, private, internal and their equivalents in every language QREATE ships.
@everyoneis denied View Channel. If a plan explicitly granted@everyoneaccess to such a room, that grant is refused and the denial applied instead. Rooms inside a closed category inherit it. - A generated role is never given Administrator, nor Manage Server, Manage Roles or Manage Webhooks. Each of those lets whoever holds the role grant itself the rest. Everything a moderator actually needs is granted normally: Kick Members, Ban Members, Timeout Members, Manage Messages, Manage Channels.
Moderation permissions live in two places
Worth knowing before it surprises you. The per-action role lists in the Moderation module are QREATE's permissions, alongside Discord's rather than instead of them. A role on the list can use the command through QREATE without holding the matching Discord permission, and a role holding the Discord permission but absent from the list cannot use it through QREATE. This is deliberate: you can let a trusted member ban through QREATE without handing them Ban Members on the server.
Review and undo
Nothing reaches Discord until you press Apply. The plan names every channel, role and setting it touches before it runs, and what actually ran is kept in the run record with who approved it, so a build can be put back.
Plans and support
Priority support is included on the Growth and Studio plans. Studio also raises the ceilings that matter when you run more than one community: up to 5 servers, more Q turns per day, 20 ticket panels, 200 automation rules, 500 custom commands, custom branding and a custom bot name. Compare the tiers on the pricing page.