Skip to main content
Most dashboard problems come down to what Bloom can see and what your account is allowed to open.
Bloom must be in the server, and you must be an administrator, the owner, or hold a dashboard access role there. If your access changed recently, sign out and back in so the dashboard refreshes your server list.
This usually means Bloom is no longer in that server. Re-invite Bloom, then reload the picker.
Bloom’s servers are split across shards, and the dashboard can return a temporary error for one it cannot reach yet. Try again shortly. If it keeps happening, report it in the support server.
Modules appear only to members holding the matching permission. If you got in through a dashboard access role rather than Administrator, you see only the modules for the permissions you hold. See the module matrix.
Bloom caches some settings briefly. Give it a moment, then confirm with the matching command in your server, for example !logs or !joingate, which always read the current values.

Dashboard access

Signing in and controlling who can open a server.

Permission errors

When the problem is a permission rather than the dashboard.

Permission reference

Which permission each module requires.

Support server

Report a dashboard error that persists.