In Discordofficer

Council

The federated guild's panel and what only the Council decides: applications, blacklist, cases and stepping into a core.

What it does: /council config opens the federated guild's panel: switching on and off, channels, roles, deadlines, names and rules, and the Council's seats. The Council approves or turns down applications with the buttons in the recruitment channel and handles the blacklist. /case open records a problem with someone: level 1 is just recorded, levels 2 and 3 go to a Council vote. /council intervene is the only door through which the Council touches a core.
Who sees it: Whoever has a seat on the Council, and the GM, who has one too. Whoever has Manage Server configures and gives seats, but does not approve, vote or intervene. Choosing the roles also takes Manage Roles. A core's Raid Leader and officers open a case about someone in their core.
Where to find it: /council and /case, in any channel where you can write; the panel and the replies only you see. Each case has a private thread in the cases channel, and each change is announced in the log channel.

The federated guild starts off, in each guild. Off, of its commands only /council shows up, which is how it is switched on, and /appeal.
The seat is what rules, not the Discord role. Manage Server gets through in the configuration and the seats, and in nothing else.
Choosing a role takes Manage Roles on the server, and the role coming in and the one going out have to be below your highest role. Never @everyone, an integration role, or a role with Administrator, Manage Server or Manage Roles.
Switching on the federation does not take a role from anyone. Whoever already uses the configured member role is recognized as a member on first contact.
Only a seat approves an application and touches the blacklist. An application from someone on the blacklist arrives flagged, and Approve is refused.
The case is read in a private thread with the Council, the core's Raid Leader and whoever opened it, never with the person it is about. In the vote, the target, whoever opened it and whoever was marked as involved stay out; the most-voted option wins, and the GM only breaks ties.
What the bot posts in the guild's channels goes out in the server's language. The panel and the replies only you see, including refusals, go out in your Discord's language.

A refused attempt does not show in the log channel. It is recorded, but a channel that repeats every wrong click is a channel nobody reads.
The Approve button shows for everyone who sees the recruitment channel. Whoever has no seat clicks and hears that they cannot.
The log channel says “case #12”, never about whom or what.
Your server calls the Council, the core or the Raid Leader by another name: the guild can rename all three in the panel.