/manage#
Controls who is allowed to use Eimi in your server. /manage is for the person a bot
admin has delegated a server to, and for bot admins themselves.
Synopsis#
/manage [add:<user>] [remove:<user>] [blacklist_add:<user>] [blacklist_remove:<user>]
[blacklist_list:<any text>] [mode:<whitelist|blacklist>] [list:<any text>]
[status:<any text>]
Guild channels only. /manage does not work in DMs, and it is only available where Eimi
was added to the server itself (not through a personal install). Every reply is ephemeral.
Run /manage with no options to get a help card listing everything below.
Who can run it#
/manage requires no Discord permission at all. Being the Discord server owner, or
having Administrator or Manage Server, grants you nothing on its own.
You can run it if either of these is true:
| You are | How you got there |
|---|---|
| A bot admin | Configured by the maintainer |
| The delegated owner of this server | A bot admin delegated this server to your user ID |
Anyone else gets "Only the server owner or bot admins can use this command."
If the server has never been delegated, even the right person gets
"This server is not delegated." A bot admin has to delegate it first from the /eimi
admin panel, supplying the server ID, the owner's user ID, and optionally a nickname and
notes.
A new delegation starts locked down
A freshly delegated server begins in whitelist mode with an empty allowed list.
That means nobody can use Eimi there except you (the delegated owner), bot admins,
and anyone on the bot's global whitelist. Everyone else gets an access-denied message
until you add them with /manage add.
This is the single most common source of confusion. Either add people one by one, or
switch the server to blacklist mode with /manage mode: blacklist.
Parameters#
Supply exactly one option per invocation. Passing two gives you "Please specify only one action at a time."
| Parameter | Value | What it does |
|---|---|---|
add |
@user or user ID |
Adds the user to this server's allowed list |
remove |
@user or user ID |
Removes the user from this server's allowed list |
blacklist_add |
@user or user ID |
Blocks the user in this server |
blacklist_remove |
@user or user ID |
Unblocks the user in this server |
blacklist_list |
any text | Lists the blocked users as mentions plus raw IDs |
mode |
whitelist or blacklist |
Switches this server's access mode |
list |
any text | Shows the access mode plus the full allowed and blocked lists |
status |
any text | Shows the server name, owner, mode, list counts, delegation date, admin notes, and a command cheat sheet |
list, blacklist_list, and status take a value only because of how the options are
typed. Any text at all triggers them, so /manage status: x is fine.
/manage add: @friend
/manage mode: blacklist
/manage blacklist_add: 123456789012345678
/manage list: x
Note
You cannot add or block a bot admin -- they have global access regardless. You also cannot block the delegated server owner, since the owner check runs before the block check so an owner cannot lock themselves out.
Access modes#
| Mode | Meaning |
|---|---|
| Whitelist 🔒 (opt-in) | Only people on your allowed list can use Eimi in this server |
| Blacklist 🌐 (opt-out) | Everyone can use Eimi in this server except the people you have blocked |
In both modes, bot admins, the delegated owner, and globally whitelisted users always get through, and blocked users are always denied. The full order of checks is described in Access Control.
Your server's lists apply only to your server. They have no effect in DMs, in other servers, or when someone uses Eimi through a personal install.
Notes, limits, and the alert channel#
These are set by a bot admin from the /eimi panel, not by /manage, but they are what
shapes your server's experience:
| Setting | Who sets it | Effect |
|---|---|---|
| Notes and nickname | Bot admin, when delegating or editing the server | Free-text admin notes shown in your /manage status output |
| Job limit | Bot admin | How many jobs one person may have queued at once. Resolved per user, then per channel, then per server, then by VIP status, then the global default (currently 15) |
| GPU power limit | Bot admin | Watt cap applied while a job runs. Resolved per channel, then per server, then per user, then by user tier |
| Alert channel | Bot admin | A channel in your server where Eimi posts error and warning alerts |
Exceeding your job limit gives you "Job Limit Reached / You have N job(s) in the queue. Your limit is M." Ask a bot admin if your server needs a higher one. Every one of these is edited by hand by the maintainer, so there is no form to fill in and no turnaround time to expect -- you ask, and they change it when they get round to it.
Note
If Eimi is removed from your server, the delegation entry is cleaned up automatically. Re-adding the bot means asking for the server to be delegated again.
What per-server config does not cover#
- No per-server generation defaults. There is no server-wide default model, upscaler, aspect ratio, or prompt. Every generation setting is per user, in /settings.
- No NSFW channel gating. Eimi does not check whether a Discord channel is marked age-restricted, and there is no way to allow or block NSFW per channel. NSFW is purely a per-user toggle that changes how the prompt is composed.
- No per-server queue priority. Jobs are processed in the order they arrive.