> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bloombot.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Dashboard access

> Sign in to Bloom's web dashboard, pick your server, control who else can open it, and understand the public pages.

Bloom's dashboard at [dash.bloombot.cloud](https://dash.bloombot.cloud/) is a web interface for the settings that are easier to manage with forms, such as automod, welcome messages, tickets, and forms. This page covers signing in, choosing a server, who can open it, and the public pages that need no login.

## Sign in

The dashboard signs you in with your Discord account.

<Steps>
  <Step title="Open the dashboard">
    Go to [dash.bloombot.cloud](https://dash.bloombot.cloud/), or run `!dash` in your server to get a direct link.
  </Step>

  <Step title="Authorize with Discord">
    Sign in with Discord. The dashboard reads your account and your list of servers so it can show the ones you can manage. It does not gain any power over your account.
  </Step>

  <Step title="Pick a server">
    You land on the server picker. Choose the server you want to configure.
  </Step>
</Steps>

<Info>
  Your sign in lasts about a day of inactivity and refreshes while you keep using it. If your access to a server changes, sign out and back in so the dashboard sees the change.
</Info>

## The server picker

The picker only lists servers where **both** of these are true:

* **Bloom is in the server.** If Bloom is not present, the server does not appear. [Add Bloom](/getting-started/first-setup) first.
* **You can manage it.** You are an administrator or the server owner, or you hold a dashboard access role that the server has configured.

If a server you expect is missing, confirm Bloom is a member and that you have one of those forms of access. A server where you are only a regular member will not show up.

## Who can open a server's dashboard

Access to a server's dashboard is granted if you are any of the following:

| Access                | Who                                                                   |
| --------------------- | --------------------------------------------------------------------- |
| Administrator         | Any member with Discord's Administrator permission                    |
| Server owner          | The Discord server owner                                              |
| Dashboard access role | A member holding a role the server added to its dashboard access list |

A dashboard access role lets you delegate the dashboard to trusted staff without giving them Administrator. Holding an access role gets you **in**; it does not, by itself, unlock every setting.

### Configure a dashboard access role

<ParamField path="dash" type="prefix command">
  Replies with this server's dashboard link. Administrators and the server owner also get a **Manage Dashboard Access** button. Aliases: `dashboard`, `panel`.
</ParamField>

Run `!dash`, click **Manage Dashboard Access**, and pick the roles that may open the dashboard. Choosing **Restrict to Admins Only** removes all custom roles, leaving access to administrators and the owner. Only administrators and the owner see this button and can change the list.

## What each person sees

Inside a server's dashboard, each module appears only to members who hold the permission it requires. Administrators and the owner see everything; a member who got in through an access role sees only the modules matching the permissions they actually have.

A few examples:

* **Server Configuration**, **Automod**, **Jail**, **Logging**, **Join Gate**, and **Tickets** need Administrator.
* **Welcome**, **Leveling**, **Starboard**, **Forms**, and **Boosters** need Manage Server.
* **Antinuke** and **Fake Permissions** are limited to the server owner and anti-nuke admins.
* **Server Analytics** is visible to any member who can open the dashboard.

The full module list is in the [Permission reference](/reference/permissions#dashboard-module-access).

## Public pages

Some dashboard pages are meant for people who are not staff and do not sign in as administrators. They have their own access rules:

* **Forms** and **appeals** are public links. A respondent signs in with Discord to submit, and the form or appeal decides who may respond.
* **Transcripts** open a saved record of a ticket or channel by its link, subject to the access the transcript requires.
* **Monthly recap** opens a personal activity page through a private link.

These pages do not require administrator access to the dashboard. They are shared as links, and each enforces its own rules on who can view or submit.

## Troubleshooting

<AccordionGroup>
  <Accordion title="A server is missing from the picker">
    Bloom must be in the server, and you must be an administrator, the owner, or hold a dashboard access role there. If you gained access recently, sign out and back in so the dashboard refreshes your server list.
  </Accordion>

  <Accordion title="The dashboard says the server is on a different shard">
    Larger deployments split servers across shards, and the dashboard can return a temporary error (status 503) for a server it cannot reach directly yet. Try again shortly. If it persists, ask in the [support server](https://discord.gg/HYSgTQ6SHR).
  </Accordion>

  <Accordion title="I can open the dashboard but a module is hidden">
    Modules appear only to members with the matching permission. If you got in through a dashboard access role rather than Administrator, you will only see modules for the permissions you hold. See the [module matrix](/reference/permissions#dashboard-module-access).
  </Accordion>

  <Accordion title="Server not found after choosing it">
    This usually means Bloom is not in that server. Re-invite Bloom, then reload the picker.
  </Accordion>
</AccordionGroup>

## Related pages

<CardGroup cols={2}>
  <Card title="Permissions and hierarchy" icon="user-lock" href="/getting-started/permissions">
    How dashboard access maps to the same permission checks Bloom uses for commands.
  </Card>

  <Card title="Permission reference" icon="shield-halved" href="/reference/permissions">
    The full table of which permission each dashboard module requires.
  </Card>

  <Card title="Invite and first setup" icon="rocket" href="/getting-started/first-setup">
    Add Bloom and set the basics before opening the dashboard.
  </Card>

  <Card title="Full command list" icon="list" href="https://bloombot.cloud/commands">
    Browse every command on the main Bloom website.
  </Card>
</CardGroup>