New: Fylgra is now open to every server

Discord bot · with a control room on the web

Change permissions without guessing.

Fylgra lays out in one table which role may see and use which channel. You stage your changes, have Fylgra work out who gets in where afterwards, and only then send them to Discord. If something was wrong, you take single rows back.

Add to Discord See the demo first

Fylgra only asks for the permissions it uses when you invite it – no Administrator. Which ones, and what for

changes only go live at the press of a button every change can be undone one by one tickets, polls, events and a planner in the same bot
fylgra · permission matrix Example Server
roles × channels · #community
Role \ Channel introductionsmediasupport
Team
Moderator
Member
@everyone
3 pending changes
Simulator · role “Member” · #media now not visible after applying visible

// Permissions

You see the result before it happens on the server.

In Discord, permissions don't hang off the role alone. Every channel can carry its own exceptions on top, and they apply in a fixed order: first what goes for everyone, then the member's roles, last an exception for the individual person. After a few months of running a server, nobody is quite sure any more who actually sees a channel. Fylgra works it out and writes down what comes of it.

B Example Server
permission matrix · #community
Role \ Channel Generalwelcomeintroductionsmedia
Team
Moderator
Member
@everyone
3 pending changes

A backup helps once something has already gone wrong. This helps beforehand.

Undo edits too

Pro

If someone renamed, reconfigured or moved a role or channel through Fylgra, you set it back to how it was. Before undoing, you see what will change. The history then reaches back 90 days instead of 30. You can still undo permission changes from the last 30 days for free.

Backups & server templates

In progress

Coming next for Pro: back up your whole server and rebuild deleted roles and channels, with their permissions and settings. The messages in them don't come back. You'll also be able to carry a server's structure over to a new one as your own template. This doesn't exist yet. As soon as it's done, it will say so here.

// Modules

Everything else runs in the same bot.

Tickets, polls, events, live announcements, self-assign roles, server rules: plenty of servers bring in six different bots for that. Each one wants setting up separately, and each has its own idea of who's allowed to operate it. With Fylgra it's one bot and one setup. What you may do in the dashboard follows from your roles in Discord.

fylgra · overview Example Server

Overview

Module health, incidents and your Discord server at a glance.

All quiet 6/6 modules on · no open incidents 09:36:07

Example Server

Permission matrix History
1 role with the Administrator permission Team
284Members
4Roles
18Channels
5Categories
last synced with Discord 2 min ago

Recent changes

3 change(s) to introductionsMira · 24 min ago
Channel “media” createdJonas · 48 min ago

3 open tickets

see all
#12 · 🐛 Report a bug🟢 Open

1 scheduled entry

see all

Community Night

fires Fri 18/09, 18:00

1 active poll

see all

Which event on Saturday?

Movie Night52%
Community Tournament33%
Chill & Talk15%
142 votes · ends in 2 hrs
Modules
Server Structure Core module · always on Polls 1 active poll Events 1 upcoming event Planner 1 scheduled entry Ticket system 3 open tickets Twitch running · —

The home page with several modules switched on.

Four of them you can look at right here: a click on the card opens up how it actually looks in the dashboard and in Discord.

Ticket system

Live

You create your own ticket types, each with its own form, its own people in charge and a private channel per ticket. Whether you reply in Discord or in the dashboard makes no difference: it's the same thread.

Polls

Live

Polls and date-finding run as an ordinary Discord poll in the channel. In the dashboard you still see the result weeks later.

Planner

Live

Prepare a post, a poll or an event at your own pace and set a time. Fylgra publishes it then, even if none of you happen to be online.

Community Pulse

Live

How many people join in, on which days your server is busiest and who stays after joining. You see numbers, never message content. With Pro the insights go a lot deeper, down to a list of the most active members that only admins see.

Also already included

Events
Create Discord events, see who said yes, look up past ones.
Self-assign roles
Members give themselves a role with a button or a reaction. You see beforehand how the message will look in Discord.
Server rules
Whoever agrees gets the role and with it the access. Members who have been around for ages you add in one step.
Twitch
When your stream goes live, Fylgra posts it to the server. For your own channel and for channels you add yourself.
Giveaways in Twitch chat
Viewers enter by typing a keyword in your chat. The draw happens in the dashboard, checked against conditions you set yourself. You can let a mod draw as well, without giving them anything else.
A welcome for new members
A fixed welcome post with your own banner, optionally a direct message and a short greeting in chat as well. You see beforehand how it will look in Discord.
Feedback & wishes
Report a bug or a wish straight from the dashboard. I reply right there, with no detour through email.
Manage members
Roles, nicknames, timeouts. Who may do this in the dashboard follows from their Discord permissions. Anything beyond that is granted by the server owner alone, one at a time, and an access grant shows as such.

New: the dashboard in three looks

Next to the default dark blue there's now Cyberpunk, with bevelled frames and red light over a city at night, and Neon with glowing violet-blue edges. You pick yours in your profile under “Appearance”; the choice applies to the browser you make it in.

The dashboard overview in the Fylgra · Dark theme
Fylgra · Dark
The dashboard overview in the Fylgra · Cyberpunk theme
Fylgra · Cyberpunk
The dashboard overview in the Fylgra · Neon theme
Fylgra · Neon

// Security

Which permissions Fylgra needs, and what for.

Fylgra may change the roles and channels of your server and throw members out. That's a lot of trust for a bot you're seeing for the first time. So this is where it says what each single permission is needed for, before you grant it. Fylgra only asks for what it uses itself.

Fylgra asks for these permissions, and only these

Posting its own messages
View Channels · Send Messages · Send Messages in Threads · Embed Links · Attach Files · Add Reactions · Use External Emoji · Create Polls · Pin Messages · Manage Messages · Mention @everyone, @here, and All Roles
For ticket forms, polls, server rules and live announcements. “Pin Messages” for its own status posts. “Manage Messages” so Moderation can delete messages that break a rule and the role buttons can remove old reactions in “one role only” mode. “Use External Emoji”, because the role buttons let you enter an emoji from another server as well. Mentions only if you set up alerts that way: Fylgra pings nobody of its own accord – neither @everyone nor @here nor a role.
Manage Roles and Manage Channels
Manage Roles · Manage Channels
This is how Fylgra sets who may see which channel, hands out the roles from the role buttons and the server rules, and creates ticket channels or a missing announcement channel.
Reading history and the audit log
Read Message History · Manage Threads · View Audit Log
Fylgra reads the history only where a module you switched on needs it. “Manage Threads” only because Discord won't hand out the list of private threads otherwise – Fylgra changes no threads with it. In the audit log, Fylgra looks up who invited it (for the welcome message), who deleted a message (message log) and whether another bot is deleting things in bulk (backups & templates).
Events
Create Events · Manage Events · Connect · Mute Members · Move Members
To create Discord events and keep them up to date. Discord requires the last three for events in a voice channel. Fylgra joins no voice channel with them, mutes nobody and moves nobody.
Moderation
Kick Members · Ban Members · Timeout Members · Manage Nicknames
Only when a moderator triggers it in the dashboard. Kicking also when someone declines the server rules: Fylgra sends them a message with the reason first.
Welcome
Manage Server
Only when someone who holds “Manage Server” in Discord themselves clicks “Apply in Discord” in the dashboard. Fylgra then sets which channel shows Discord’s system messages and turns Discord’s own join message on or off, and on Community servers the rules channel too. Fylgra changes none of this on its own. You can undo the last step, as long as nobody else has changed it in Discord since.
Reading the member list and message content privileged
Discord unlocks these two separately. The member list shows who holds which role. Fylgra reads messages only when a module needs to: in ticket channels, when you switch on the message log, and when you give Moderation rules to enforce. Moderation checks in memory and keeps only what breaks a rule, time-limited and with message texts encrypted. Everything else Fylgra throws away at once.

What Fylgra doesn't do: it sends no voice messages, joins no voice channel, creates no webhooks, and changes your server settings only when you click (see “Welcome”). The greeting for new members mentions only the newcomers themselves, and only if you set it up that way.

No Administrator

Fylgra doesn't ask for Administrator when you invite it. Only for certain actions – ticking “Administrator” on a role, or restoring a role with the Administrator permission from a backup – can you give it to Fylgra yourself; the dashboard shows you the link right there. Channels your channel permissions don't let Fylgra see, it can't manage either.

Discord only lets a bot give a role the permissions it holds itself. If you want to give a role a permission in the dashboard that Fylgra doesn't have, or restore a role with the Administrator permission with backups & templates, Fylgra shows you right there what's missing. You can then tick it in Discord yourself, or give Fylgra's own role the missing permission under Server Settings → Roles. If you invited Fylgra before, it keeps the permissions it had.

Fylgra only ticks “Administrator” on a role when the server owner or someone who is an administrator themselves does so in the dashboard, just like in Discord. Moderators with Fylgra access grants never can.

Roles Fylgra won't hand out

A role anyone can give themselves at the press of a button is a different thing from one a moderator hands out by hand. So Fylgra checks every role before it even appears in the picker. Never handed out: @everyone, roles managed by Discord or another app, roles that sit above Fylgra itself in the role list, and every role with far-reaching permissions – Administrator, Manage Server, Manage Roles or Manage Channels, Ban Members or Kick Members, Manage Webhooks, Mention @everyone.

And anyone who kicks, bans or grants a role from the dashboard has to be allowed to do it in Discord anyway, and has to sit above that person in the role list. Nobody can edit themselves or the server owner. So Fylgra gives nobody more power than they already have in Discord.

Data

What is stored?
How your server is put together – which roles and channels there are –, the settings of the modules you switched on, and a record of what was changed through Fylgra. Two modules store more, and only for as long as they are switched on: the analysis of your community records, for each member, when they joined, when they were last active and when they left; giveaways store the name and the ID of the Twitch viewers who took part. Welcoming new members keeps their Discord ID only briefly in a cache, for 7 days at most.
For how long?
The server's access logs for 14 days. Your sign-in for 7 days at most, and the moment you sign out. The change log until your server's data is deleted. Backups for 14 days at most. Entries in a giveaway 30 days after it ends; the draw itself keeps no names after 90 days. What the community analysis records for each member, 90 days after that member leaves; the times of joining, leaving and first activity for the analysis of newcomers after 13 months.
Where?
On a rented server in a data centre in Germany.
And if I remove the bot again?
Whatever is stored for that server stays for now – invite Fylgra back and it's all there again. It's deleted automatically no earlier than 30 days after the removal; if a plan above the free one is running on your Fylgra account, no earlier than 30 days after that plan ends. On request we delete it sooner.

Privacy · Terms of Service · Imprint (German)

// Progress

Where things stand.

One module after another. Each one runs for a while in the daily life of a real server before the next one starts.

MOST RECENTLY FINISHED
  • Community Pulse image cards in Discord (Pro)
  • Undo edits to roles and channels (Pro)
  • Community Pulse: times of day, channel details, year view and export (Pro)
  • Two new looks for the dashboard
  • A welcome for new members
UP NEXT
  • Backups and server templates (Pro)
  • New posts from YouTube, Instagram and X in the channel
Open now

Bring Fylgra to your server.

You invite the bot, sign in with Discord, and the Setup Assistant walks you through setup. If you'd rather look first, click through the demo, no sign-in needed.

Most of it is free. Pro unlocks deeper insights, a longer history, more you can undo and higher limits, for example for more servers and ticket panels. You see what it costs and where the limits are in the dashboard after signing in, before you buy anything.

Add to Discord See the demo

Fylgra only asks for the permissions it uses when you invite it – no Administrator. Which ones, and what for

Important after inviting: in Discord, drag Fylgra's role all the way to the top under Server Settings → Roles. Discord places a new bot's role at the very bottom at first, and a bot may only manage roles and members that sit below its own role.