> ## Documentation Index
> Fetch the complete documentation index at: https://perplayerkit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# PerPlayerKit Admin Commands for Staff and Operators

> Reference for PerPlayerKit admin and staff commands: managing the kit room, inspecting player kits, saving public kits, and migrating storage backends.

Admins and staff members use a dedicated set of commands to set up the plugin, build out the Kit Room, publish public kits for all players, inspect individual player inventories for moderation, and migrate kit data between storage backends. These commands are intentionally locked behind elevated permissions to keep your server's kit data secure and under operator control.

<Note>
  `kit.admin` is a shorthand permission that grants `perplayerkit.admin`. Likewise, `kit.staff` grants `perplayerkit.staff`. Assign the shorthand nodes in your permission plugin for cleaner group configuration.
</Note>

## Admin Commands

The following commands require the `perplayerkit.admin` permission.

| Command                                        | Permission           | Description                                                                                                    |
| ---------------------------------------------- | -------------------- | -------------------------------------------------------------------------------------------------------------- |
| `/kitroom`                                     | `perplayerkit.admin` | Open the Kit Room editor GUI to build and organize the server's shared kit offerings.                          |
| `/savepublickit`                               | `perplayerkit.admin` | Save your current inventory contents as a new public kit, making it available to all players via `/publickit`. |
| `/perplayerkit migrate <source> <destination>` | `perplayerkit.admin` | Migrate all kit data from one storage backend to another.                                                      |

## Staff Commands

The following commands require the `perplayerkit.staff` permission. Use them to inspect player kit data during moderation or support requests.

| Command                | Permission           | Description                                                |
| ---------------------- | -------------------- | ---------------------------------------------------------- |
| `/inspectkit <player>` | `perplayerkit.staff` | Open the specified player's kit inventory for inspection.  |
| `/inspectec <player>`  | `perplayerkit.staff` | Open the specified player's enderchest kit for inspection. |

## Storage Migration

The `/perplayerkit migrate` command lets you move all kit data from one database backend to another without losing any player kits. Supported backends include `sqlite`, `mysql`, and `postgresql`.

<Warning>
  Always create a full backup of your current kit data before running a migration. If the migration is interrupted or fails, restoring from a backup is the only recovery path.
</Warning>

```text theme={null}
# Migrate from SQLite to MySQL
/perplayerkit migrate sqlite mysql

# Migrate from MySQL to PostgreSQL
/perplayerkit migrate mysql postgresql

# Migrate from PostgreSQL back to SQLite
/perplayerkit migrate postgresql sqlite
```

Run the command in-game or from the server console. PerPlayerKit will read from the source backend and write all kit records to the destination backend. After a successful migration, update your `config.yml` to point to the new backend and restart the server.