Administration
The admin pages - members, devices, integration keys, ingest health and the audit log.
Admins are the members listed in ADMIN_DISCORD_USER_IDS or holding a role in
DISCORD_ADMIN_ROLE_IDS (see Discord setup). They get an
Admin menu. To everyone else, every admin page is a 404.
| Page | What you can do |
|---|---|
| Users | See every member and their state. Offboard a member, or restore one in their grace period. |
| Devices | See every paired RuneLite client, and revoke one. |
| Integrations | Create and revoke integration keys for guild services. See below. |
| Ingest health | Payloads per minute, rejected payloads, and rejections since the last start. |
| Raw payloads | Recent plugin payloads for debugging, with filters. Every view is audited. |
| Audit log | Who did what. Kept for AUDIT_LOG_RETENTION_DAYS. |
| Settings | The guild feed filter. |
| Configuration | The running configuration, with secrets redacted. |
| Decommission | Shut the hub down for good. See Decommissioning. |
Integration keys
An integration key (service key) is an API key that belongs to the guild instead of a person. Use one for a service the whole guild relies on, such as the OSRS Guild Map or a shared Discord bot.
Open Admin → Integrations and click Create integration key.
Give it a name, the categories the service needs and an expiry. The rate limit defaults to 600 requests a minute; you can set it anywhere from 1 to 6000.
Copy the key, which is shown once, into the service's configuration.
How it differs from a personal key:
- It belongs to nobody. Offboarding anyone, including the admin who created it, never revokes it.
- It sees what the guild sees: only categories whose audience is guild. There is no admin override.
- It has its own limits: 600 requests a minute by default, and 50 accounts per bulk request instead of 10.
- It sees
account_hash, so a service can match a hub account to a player without relying on the name. - "Today" is UTC, since the key has no creator whose time zone it could use.