Access Control#
Who can use Eimi, where, and what each user tier unlocks. This page explains what an access-denied message means and who to ask about it.
The short version#
Eimi's permissions have nothing to do with Discord roles. Being a Discord server owner or administrator grants you no bot powers. Every decision comes from the bot's own configuration: a global list, plus optional per-server lists.
Three things decide whether a command works for you:
- Your user tier (regular, VIP, or admin).
- The access mode that applies where you are (global, or the server's own).
- Whether you are on an allowed or blocked list.
User tiers#
| Tier | How you get it | What it unlocks |
|---|---|---|
| Regular | Default for anyone who passes the access check | Every command, standard job limit (currently 15 queued jobs), standard GPU power cap |
| VIP | A bot admin adds you | Everything a regular user gets, plus the VIP-only edit models and the cloud render backend, a separate job limit, and a separate GPU power cap |
| Admin | Configured by the maintainer | Access everywhere regardless of mode or lists, the /eimi admin panel, /manage in any server, other users' /history, and jobs hidden from public queue status |
A blocked user is not a tier. Being blacklisted overrides everything except admin status.
What VIP actually unlocks#
| Feature | Detail |
|---|---|
| Nano Banana, Nano Banana 2, Nano Banana 2 Lite, Nano Banana Pro | API edit models in /edit, the 🎨 Edit button, the remix edit-model picker, and the Edit model setting in /settings |
| GPT Image 2 | Same, as an edit model |
| Cloud render backend | When the maintainer has /render running on the cloud backend, only VIP members and admins may use it. Non-VIPs get "API video rendering is available to VIP members only." VIPs and admins also get the larger resolution tiers and longer clips |
Non-VIPs never see the VIP-only models in a dropdown at all. They are filtered out of the list rather than shown and refused.
Info
VIP is granted by a bot admin. There is no command to request it and no way to buy it. Ask whoever runs the bot.
It is not a status you own. VIP is a line in a config file that the maintainer edits by hand, so it can be added, removed or reset without warning, and what it unlocks changes whenever the model list does.
Access modes#
Both the global configuration and each delegated server have a mode.
| Mode | Meaning |
|---|---|
| Whitelist 🔒 (opt-in) | Only people on the allowed list can use the bot |
| Blacklist 🌐 (opt-out) | Everyone can use the bot except the people on the blocked list |
| Disabled (global only) | No access checking. Everyone can use the bot |
How the checks run#
In order, stopping at the first match:
- Bot admin -- allowed, everywhere, always.
- Globally blacklisted -- denied, everywhere, always.
- In a DM, or using a personal install -- only the global mode applies. Server lists are irrelevant.
- In a server that has not been delegated -- only the global mode applies.
- In a delegated server, in this order:
- the server's designated owner is allowed (so an owner cannot lock themselves out),
- anyone on the server's blocked list is denied,
- anyone on the global whitelist is allowed,
- in whitelist mode, only people on the server's allowed list are allowed; in blacklist mode, everyone else is allowed.
A delegated server's lists apply only inside that server. They do not follow you into DMs or into another server.
"You don't have access"#
The wording tells you which list to chase.
| Message | What it means | Who to ask |
|---|---|---|
| "You don't have access to use the bot in DMs." | The global mode is whitelist and you are not on the global list | A bot admin |
| "You are globally blacklisted from using this bot." | You are on the global blocked list | A bot admin |
"You don't have access to use the bot in this server. Ask the server owner to add you with /manage add" |
This server is delegated and you are not on its allowed list | The server's delegated owner |
| "Access denied." | The generic fallback | A bot admin |
| "Only the server owner or bot admins can use this command." | You ran /manage without being either | A bot admin, to delegate the server to you |
| "This server is not delegated." | Nobody has been given control of this server yet | A bot admin |
| "Job Limit Reached" | You are not blocked, you just have too many jobs queued | Wait, or ask for a higher limit |
Warning
A newly delegated server starts in whitelist mode with an empty allowed list. If
the bot has just arrived in your server and refuses everyone, that is why. The
delegated owner fixes it with /manage add or by switching the server to blacklist
mode. See /manage.
Guild install vs user install#
There are two ways Eimi can be present, and it changes whether your results are public.
| How you reach Eimi | Where you use it | Your results are |
|---|---|---|
| Guild install -- a server admin added the bot to the server | That server, in a channel where the bot can post | Public, visible to the channel |
| Guild install, but the bot lacks permission to post in that channel | That server | Ephemeral, visible only to you |
| User install -- you added Eimi to your own Discord account | Any server, group DM, or private channel | Ephemeral, visible only to you |
| User install | Your DM with the bot | Public in that DM |
A user install lets you take Eimi into servers where it is not installed, at the cost of results only you can see. Your access is still checked against the global lists in that case, because the server's own lists do not apply to a personal install.
Buttons follow visibility#
| Message type | Extra button | What it does |
|---|---|---|
| Public | 🗑️ Delete | Removes the message from the channel |
| Ephemeral | 📤 Post | Posts the result publicly, so other people can see it |
Everything else on the card -- 🔄 re-roll, 🎲 remix, 🔍 details, ⬆️ upgrade, 🎨 edit, ✨ detailer -- is the same either way. See Buttons.
Note
/settings and /history are always ephemeral no matter how you reached the bot. /manage is guild install only and does not work in DMs at all.
Limits that apply once you are in#
| Limit | Resolved in this order |
|---|---|
| Queued jobs per person | Per user, then per channel, then per server, then by VIP status, then the global default (currently 15) |
| GPU power cap during a job | Per channel, then per server, then per user, then by user tier |
Both are configured by bot admins only, and both are numbers in a config file rather than a policy, so they move when the maintainer feels like moving them. See Bot Behavior for the queue system itself.