// Demo
The dashboard, without signing in.
This is what it looks like with Fylgra running on your server. On the left you click through the same navigation as in the real dashboard: first the table of permissions, then polls, planner and tickets. No server is connected – every name and number here comes from a made-up example server.
The home page: what's running, what's open and how the server is put together.
Overview
Module health, incidents and your Discord server at a glance.
Example Server
Permission matrix HistoryRecent changes
3 open tickets
see all1 scheduled entry
see allCommunity Night
1 active poll
see allWhich role may see which channel? A click in the table changes nothing on Discord yet – it's collected below.
This is the server as seen by someone who holds only this one role. Next to every channel is the reason the result comes out that way.
each row outranks the one above it; the bottom row is what counts in the end
And this is how one particular member sees it, with every role they currently hold. Discord adds up the permissions of all their roles; Fylgra works it out the same way.
each row outranks the one above it; the bottom row is what counts in the end
Nothing reaches Discord before you confirm it here. Only what's in the list is changed; everything else about the channel is left alone.
| Role | Channel | Permission | Change | |
|---|---|---|---|---|
| Member | #media | View Channel | denied→allowed | |
| Member | #introductions | Send Messages | denied→allowed | |
| @everyone | #welcome | Add Reactions | neutral→denied |
Every apply is stored as one package. You undo a whole package or single rows from it; the undo is itself a package again. Deleted channels and roles don't come back this way, though.
Every change that went through Fylgra, as a readable sentence. Expand one to see the state before and after.
Polls run as an ordinary Discord poll in the channel. Here you see the result, even weeks later.
dashboard · active poll
1 active poll
see allWhatever is prepared waits here for its moment. Fylgra then publishes it on its own.
dashboard · scheduled entry
1 scheduled entry
see allCommunity Night
The same request from three angles: how your team sees it in the dashboard, how it looks in Discord, and how you set the ticket type up.
ticket history · discord ↔ web
discord · panel message and form
a click on “Report a bug” opens the form on the right
What's it about?
What did you do last?
Affected area
Screenshot
dashboard · setup assistant
creates the panel message from “In Discord”
Editing “Report a bug” – step 4 of 4
That was one slice. Tickets, polls, events, the planner, self-assign roles, server rules, live announcements and member management are already running in the daily life of a server, along with Community Pulse and the welcome for new members. Fylgra is now open to every server: Add to Discord. When you invite it, Fylgra only asks for the permissions it uses, no Administrator (which ones, and what for). What's finished and what comes next is on the home page.