Your whole rosterin one table.

Members, their positions and units, access permissions and history — all in one place, while Discord roles are granted automatically.

How the roster worksand who sees what.

You describe the structure once, and the panel keeps data and roles from drifting apart.
Your own structureUnits, positions and role templates to fit your format: departments, divisions or tracks — the words can be renamed too.
Permissions down to the buttonSection visibility is set by position, and action permissions by a separate matrix. The audit in a profile shows what a specific person can do.
Nothing gets lostMembers who leave move to the archive with their position and reprimand history, so a returning person’s past tenure is visible.

When a spreadsheetstops being enough.

Twenty people fit into a pinned message. Trouble starts when the roster grows and several leaders hand out positions at once.
  1. Recruitment comes in waves

    After every wave some newcomers end up without roles or positions. The roster table shows what is missing, and the Discord role is granted straight from the card.

  2. Several leaders

    When three or four people edit the data, you need to know who changed what. Every action on a member lands in the log together with its author.

  3. Someone came back

    People who left move to the archive with their history of positions and penalties. On return you see their previous record, not a blank page.

Common questionsabout the roster.

How do members get into the panel?

Two ways: a person registers through the bot — with /registration or an application form — or a leader adds them manually. On registration the panel checks the person against the blacklist.

Can I run several communities from one account?

Yes, the server switcher sits in the panel header. Positions, permissions, coins, reports and the log belong to each server separately and are never added up.

Who sees the full member card?

Section visibility is set by position and department, and action permissions by a separate matrix. The permission audit in a profile shows what a specific person can do.

What happens to the data when a member leaves?

The record is not deleted — it moves to the archive with the history of positions and penalties. The log cannot be edited, so the past stays verifiable.