A CRM for a roleplayproject and its factions.

A faction runs on order: everyone has a position, a term, penalties and reports. A-Faction carries that from the Discord application to the granted role, so leaders decide instead of merging spreadsheets.
The whole path of a newcomer: an application from Discord, an interview, a position and a role — with no manual checks.

Sound familiar?Almost every project lives like this.

Three complaints we hear from faction leaders most often.

“He was removed a week ago and still wears the Discord role”

The bot grants and removes roles the moment the action happens in the panel, so the roster and Discord never drift apart.

“We argue about a penalty: who issued it, what for, and was it there at all”

Counters follow your rules and the log cannot be edited — there is something to point at in an argument.

“Applications land in five different DMs and half of them get lost”

A form with a button collects applications in your channel and brings them to the panel together with the answers.

Why it fitsa roleplay project.

Three things that break first in a roleplay project — and how they work in the panel.
Roster

Positions are described once

Units, positions and terms live in the structure. After that a member card keeps the history itself: when they were appointed, what changed, which penalties there were. A Discord role is tied to the position, so it is granted and removed along with it.

The roster in the panel and the roles in Discord always match.

Recruiting

Applications and interviews in one place

A player presses a button in your channel and fills in the form — the application lands in the panel. The interview runs in a voice channel, the bot records everyone on a separate track, and the recording stays in the candidate card next to the decision.

Recruiting runs in waves instead of five officers’ direct messages.

Discipline

Penalties count themselves

You set the types, the limits and what they escalate into. The third verbal penalty becomes a strict one without reminders, while an appeal goes through its stages and is mirrored into a Discord forum thread.

The rules are the same for everyone and do not depend on who is on duty.

Three situationsevery faction leader knows.

  1. The roster drifted from Discord

    Someone was demoted but kept the role. On demotion and registration roles are granted and removed by the bot, so the gap never builds up.

  2. An argument about a penalty

    Counters follow the server's rules and the log cannot be edited — there is something to point at in a dispute.

  3. Recruitment comes in waves

    The form collects applications, the interview is recorded track by track, and the decision stays in the card next to the recording.

Questionsfrom roleplay projects.

Can the word faction be renamed?

Yes. In Terms the words are changed to fit your setting — department, division, branch. Data and permissions are untouched.

What if the project has several servers?

Each server is run separately: its own positions, permissions, coins and log. The server switcher sits in the panel header.

What does an ordinary member see?

Only what their position allows: section visibility and action permissions are configured independently of each other.

How many factions can one server hold?

As many as you need: units and positions are unlimited, and every organization can have its own notification channel and its own leaders.

What happens if the bot is temporarily unavailable?

The action in the panel still goes through, and a warning about the failed Discord delivery appears — the message can be sent again.