To add an admin to an Arma Reforger server, paste their Bohemia identity ID into the admins array inside the game block of config.json, then restart the server so it picks up the change. From that point the player can run #login and use admin commands like #kick and #ban directly from in-game chat. This guide covers both the LPV5 panel method and the manual config edit, plus the security practices that keep your admin team from becoming an attack surface.
Two Ways to Become an Admin in Reforger
Arma Reforger has two admin paths and you usually want both. The first is the admins array in config.json, which is a static list of trusted identity IDs that always have admin rights. The second is the admin password, set in passwordAdmin, which any player can use with #login to gain admin rights for that session. The admin password is a fallback; the admins array is the production setup.
- Use the admins array for your real staff
- Keep the admin password as a one-time fallback in case a staff member's ID is wrong
- Listed admins still typically run #login to flag themselves as active admins in chat
- Both methods are controlled by the same config.json file; there is no separate admin file
Collecting Your Admins' Identity IDs
Before you edit anything, gather every admin's Bohemia identity ID. Each admin can read theirs from the main menu Profile screen in Arma Reforger. Get them all in one pass so you only have to edit config.json once.
- Ask each admin to launch Arma Reforger and open Profile from the main menu
- Have them copy the Bohemia identity ID and send it back to you
- Drop every ID in a Discord channel or shared note in copy-paste form
- Double-check none of them contain stray spaces or quotation marks
- Never accept screenshots; typos on long IDs are very easy to miss when transcribing
Adding Admins on the LPV5 Panel
On Loafhosts the LPV5 Config Editor inside LoafHub gives you a structured view of config.json so you can edit the admins array without writing raw JSON. It is the fastest path for adding several admins at once.
- Open hub.loafhosts.com and select your Arma Reforger server
- Open the Config Editor
- Locate the admins field inside the game block
- Paste each identity ID as a quoted string into the array
- Save the config
- Restart the server so the new list takes effect
- The Config Editor flags invalid JSON before you save, which prevents a typo from breaking the server
Adding Admins by Editing config.json Directly
If you prefer raw JSON, the LPV5 file manager lets you open config.json in place. The field you want is the admins array under the game block.
- Open the LPV5 file manager and locate config.json
- Open it for editing
- Find the game block and the admins array
- Add each identity ID as a quoted string, separated by commas
- Make sure there is no trailing comma after the last entry
- Save the file and restart the server
"admins": ["abcdef1234567890", "0011223344556677"]"passwordAdmin": "long-random-secret"- config.json must be valid JSON; a single missing comma or quote stops the server from starting
Using Admin Commands In-Game
Once a player is in the admins array, they can authenticate from in-game chat and use the admin commands. The chat console is opened with the chat key and admin commands are prefixed with #.
#login changeme#kick 5 AFK in main#ban 5 60 spam- Run #players first so you know the exact slot or identity ID before kicking
- If a command does not respond, run #login again; admin status only lasts for the current connection
Removing an Admin
Removing an admin is the same flow in reverse. Delete their entry from the admins array, save config.json, and restart. There is no in-game command that revokes an admin who is listed in the array; the source of truth is the config file.
- Open the Config Editor or the file manager
- Find the admins array under the game block
- Delete the identity ID line for the admin you are removing
- Save and restart the server
- Rotate passwordAdmin if the removed admin knew it
- If the removed admin knew the admin password, change passwordAdmin immediately or they can still #login
Admin Security Best Practices
Admin rights mean the power to kick, ban, and disrupt a session, so treat the admin list like a key list. A few habits keep the system safe.
- Use a long, random passwordAdmin and only share it with people you have vetted
- Rotate passwordAdmin any time a staff member leaves
- Keep the admins array small and review it monthly
- Use LoafHub sub-users to give staff panel access instead of sharing your account
- Log major admin actions in a Discord channel so your team has a paper trail
- Do not paste your admin password in screenshots, public chats, or unredacted log uploads