“We gave someone temporary access and forgot to take it back”
Permissions belong to a position, not to a person: the role changes and so does the access.
A CRM for a studioand a working team in Discord.
When a team lives in Discord it needs scoped access, internal documents and announcements that look like announcements. The panel covers that without moving the work to other services.Release week: the build is ready, QA gets access, the checklist is updated, the announcement goes out.
Sound familiar?A familiar working week.
Three situations where a studio loses time for nothing.“The guideline is pinned somewhere, but nobody remembers in which channel”
Documents live in the panel, and search looks inside the text, not only at the title.
“We posted the announcement in chat and it sank within an hour”
The builder composes an embed and the bot sends it to the right channel on behalf of the community.
Why it fitsa studio and a working team.
Three things that usually rest on a handshake in a team. Access
Permissions belong to a position
Menu visibility and action permissions are set separately: a person can see reports without being able to change settings. The matrix is shared by the server, and the profile audit shows what a specific person can do right now.
Nobody carries extra permissions after a role change.
Documents
Guidelines that can be found
Internal documents live in the panel with a built-in editor, and search looks for words inside the text. Create and delete rights come from the matrix, so a random person will not remove a guideline.
The answer is found in seconds instead of scrolling pinned messages.
Announcements
Announcements that look the part
Title, text, color, fields and an image are composed in the builder, and the preview shows the result before sending. The channel is picked from your guild list — no IDs to type.
The announcement does not sink in chat and looks the same every time.
Three situationsin a working team.
A newcomer got too much
Section visibility and action permissions are granted separately, so access opens exactly on the needed area.
The regulation got lost in chat
The document lives in the panel and belongs to the server, and a clause is found by a phrase from the text.
The announcement sinks in the feed
A composed embed with a title, a colour and an image gets read, and the bot posts it to the right channel.
Questionsfrom studios and teams.
Can settings be moved to a second server?
Yes, with a settings template: structure, permissions, penalties and the planner move over, while the guild link, channels, webhooks and secrets never do.
Are third-party services needed for announcements?
No. The message is composed in the builder and sent by the bot to a channel picked from your guild list.
How do I know what a person can do?
The permission audit in their profile answers exactly that, while the action matrix answers the reverse — who can perform a given action at all.
Can a contractor be let into the panel?
Yes: give them a position with narrow permissions — they will see only the sections you opened and nothing else.
Can settings move to a second studio server?
Structure, permissions, penalties and the planner export to a file and apply on another server. 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
Permissions and accessThree layers of access and an audit that shows what a person can do.DocumentsInternal documents with an editor and search inside the text.Webhooks and announcementsAn embed builder: title, fields, color and an image — sent on behalf of the bot.AutomationsIf-then rules: leaves, blacklist entries and stuck requests.
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.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.Large Discord serversAutomations, separated access, search and portable settings.