Admin panel overview

The Admin panel is the detailed record-management area at /admin/. It is useful when the normal dashboard does not expose a record you need to inspect, or when you need to manage a large number of collectibles, player records, packs, or command entries at once.

It is not the same thing as Discord’s /admin slash-command group. Discord admin commands manage the bot from Discord. The Admin panel manages records from a browser. For normal day-to-day settings such as spawn pace, module toggles, response wording, and card design, use the regular dashboard first.

Opening the right view

Open the Admin panel from the Admin panel… control on Dashboard when it is available, or visit /admin/ while signed in. The dashboard link is the safest starting point because it keeps you aware of the bot instance you are managing.

There are three access modes:

• Instance owner: sees records belonging to their own bot instance. The panel hides the instance field and platform-only fields, then automatically applies the correct instance when a new record is saved.
• Dashboard helper: sees only the record types the owner has explicitly granted. A helper may be allowed to view a page without being allowed to add, change, or delete records on it.
• Global administrator: can see platform-wide pages, such as users, instances, deployment, billing, and global add-ons. A global administrator can choose an instance from the Dashboard Admin panel… menu to enter a filtered view for that instance. Choose Global Admin Panel from the same menu to clear that filter.

If an expected model is missing, do not assume it was deleted. First check the selected instance, the account you signed in with, and whether a helper was granted access to that record type. Some pages are deliberately visible only to global administrators because they control hosting, billing, or other instances.

Navigation at a glance

The Admin panel home groups records by application. Select a model name to open its list. A list page has the same basic parts:

• The breadcrumb at the top shows where you are. Click Home or an earlier breadcrumb to go back up a level.
• The page title names the record type, such as Collectibles, Players, or Packs.
• Add [record] creates a new record of that type, when your account has permission.
• Each row is one record. Click a linked value or the row’s main identifier to open its change form.
• The search field searches the fields that make sense for that model. Use the filter area for states such as enabled, active, openable, or status.
• Checkboxes on the left are for bulk actions. Select only the rows you intend to affect, choose an action, then apply it. If no useful action is selected, do not submit the form.
• Pagination at the bottom moves through the result set. Lists are deliberately limited to 50 rows per page so large instances remain usable.

Use the browser Back button only after confirming there are no unsaved form edits. On a change form, use the Admin panel’s save controls instead: Save stores the record and returns to the list, Save and continue editing stores it but leaves the form open, and Save and add another stores it and opens a clean form for the next item. The exact labels can vary slightly with the installed admin theme.

A safe workflow for any record

1. Confirm the selected instance in the Dashboard before opening the Admin panel.
2. Open the correct model list and search for the existing record before pressing Add. Duplicates are harder to repair than edits.
3. Open the record and read all filled fields before changing anything. Pay particular attention to enabled states, ownership, player IDs, tradeable flags, and dates.
4. Change one small thing, save it, and check the success message.
5. Test the relevant player-facing result in Discord when the change affects commands, a collectible, a spawn, a pack, or a payment.
6. Use History on the record when you need to see who changed it and when. History is an audit trail, not an automatic undo button.

If a change touches a Discord token, privileged intent, or command structure, return to Dashboard and use Restart or Sync commands as appropriate. A record change that only affects future spawns, packs, or reward selection will not change a message or transaction that already exists.

Instance safety built into the panel

When an instance owner or helper opens an instance-scoped list, Kompendium automatically filters it to that one bot. Foreign-key dropdowns and autocomplete suggestions are also constrained to the same instance whenever possible. This prevents accidentally attaching a collectible, player, pack, or template from another bot.

Do not attempt to work around the filter by pasting a global ID into an autocomplete field. Start typing the local name, code, Discord user ID, or number, then choose a suggestion from the list. The chosen result carries the correct local record reference.

The panel also hides internal fields such as the instance, owner, version, and loaded version from owner-mode forms. They are managed by Kompendium. Global administrators may see more technical fields; changing them should be reserved for an identified support or operations task.

The difference between the dashboard and Admin panel

Use the dashboard for guided tasks: enabling modules, editing command replies, configuring spawns, creating visual card templates, managing packs, creating data jobs, and adding dashboard users.

Use the Admin panel for record-level work: locating one player’s inventory, editing a collectible’s catchable names, reviewing a trade, searching a list of packs, changing a special’s dates, inspecting an import record, or granting a helper access to selected admin model pages. The two areas work on the same selected instance but are designed for different jobs.

Continue with Search, filters, and record editing before making bulk edits. Then use Admin panel records to find the model page you need.