FAQ & troubleshooting
Quick answers to the most common questions.
The bot is in my server but a command says it can't do something.
Almost always a role position issue: drag the Qreate role above the roles/members it needs to manage. Administrator doesn't bypass Discord's role hierarchy.
My dashboard shows a server but says 'Bot not added'.
You manage that server on Discord, but QREATE isn't in it yet. Click the server and choose Add a server to invite the bot.
I added the bot to a brand-new server but it doesn't appear.
After approving the invite, switch back to the dashboard tab — it refreshes automatically. If the server is brand-new to you (you just became its admin), sign out and back in once: your server list is built at login, so a fresh sign-in picks it up.
A module is on but nothing happens.
Check that you've set its required channel/role (e.g. a mod-log channel, a welcome channel) and that the bot can see/post in that channel.
Does QREATE need the Administrator permission?
No, and it will not ask for it. The invite requests 22 named permissions, each one used by a module, and the approval screen lists every one with its reason. If a module needs something the bot was not given, /setup names it and tells you what stops working without it.
Who on my team can configure QREATE?
Anyone with Manage Server. The in-Discord commands (/setup, /config, /module, /q) require that permission and Discord hides them from everyone else. On the dashboard, the same rule decides who can open a server. You can open individual commands up to specific roles from the Commands page, but a role that configures modules still needs Manage Server.
Is it really free?
Yes — during the open beta everything is unlocked at no cost. See The open beta.