“A request has been hanging for three days and nobody noticed”
An if-then rule looks at the data every 10 minutes and sends the reminder itself.
A CRM for a largeDiscord server.
When there are hundreds of members and dozens of admins, manual management breaks first. The panel takes over reminders, scoped permissions and search across the roster.A server on autopilot: rules check themselves, a new admin gets narrow rights, a person is found in seconds.
Sound familiar?This is how a large server lives.
Three things that break earliest on a large server.“Forty admins and everyone has the same rights”
Permissions belong to a position down to a single button, and the audit shows what a person can do now.
“Finding a person on the roster is a quest of its own”
Ctrl + K searches sections, members and quick actions from any page.
Why it fitsa large server.
Three things that stop scaling first. Automations
Reminders without a duty officer
An if-then rule watches the panel data: stuck requests, expired leaves, silence in the log. The check runs every 10 minutes, and a rule fires once per entry.
Nobody guards deadlines by hand.
Permissions
Access down to a single button
Menu visibility and action permissions are set separately, and the matrix is shared by the server. The profile audit answers the reverse question: what can this exact person do.
A new admin gets nothing extra by default.
Log
The history a dispute is settled by
Every action is written with the actor and the target, in Moscow time. The log is never edited, and the AI member review is built on the same numbers.
A review takes minutes instead of a thread in three chats.
Three situationson a large server.
More than ten administrators
Every action is signed by its author in the log, and permissions are granted precisely instead of everything to everyone.
Requests pile up faster than they are handled
A rule reminds whoever has to decide, and never sends the same thing twice.
A second server for the project
Settings move over as a template, while data, coins and the log stay separate for each server.
Questionsfrom large servers.
Do data add up across servers?
No. Positions, permissions, coins, reports and the log belong to each server and are never combined.
How many people can the panel handle?
There is no cap on roster size: the member table works with pages, filters and search.
How do I find a person quickly?
Ctrl + K on any page, ⌘ + K on Mac. Search shows only what your permissions allow.
Will the log survive a constant stream of entries?
That is what it is built for: entries are always written, and you can search both by the actor and by the person acted upon.
Can settings move to a second server?
Yes: structure, permissions, penalties and the planner export to a file. The guild, channels, webhooks and secrets are never transferred.
The kind of community changes nothing: the panel fits any of them that has a structure and rules — the terms are renamed to match yours.
Sections that cover this
AutomationsIf-then rules: leaves, blacklist entries and stuck requests.Permissions and accessThree layers of access and an audit that shows what a person can do.Search and notificationsCtrl + K across modules, members and actions plus a bell with decisions and reminders.Terms and presetsYour own names for modules in three forms and ready configuration sets for a new server.
Other kinds of communities
Roleplay projects and factionsRoster, penalties, interviews and applications in one panel instead of a dozen spreadsheets.Clans and guildsRoster, internal currency, an event schedule and a blacklist without spreadsheets.Esports teamsPractice schedule, reports, absences and a log of decisions.Studios and working teamsAccess by role, documents, announcements and automatic reminders.Moderation teamsDiscipline, a log of decisions and separated permissions for server moderators.Creators and their communitiesRecruiting moderators, announcements from the bot and rewards for activity.Learning communitiesGroup rosters, materials, a class schedule and reporting.