Managing Players on Your Palworld Server
List, kick, ban and unban players from the panel or in game - including the whitelist PalDefender gives you.
Where Player Management Lives
Open the Settings tab and pick Player Management from the category list on the left. It is a tab inside Settings, not a top-level sidebar entry.
A Palworld server gets four sections there: Banned Players (Native), PalDefender Whitelist, PalDefender Admin IPs, and an information-only Admin Access panel. Click one to expand it.
Each list shows the identifiers in it with a remove button, and an input box with an add button. There is no roster of everyone who has ever connected - the lists are editors for files on the server.
PalDefender reads its two lists when the server starts. To apply a change without restarting, run Reload PalDefender Config from the Command Manager, which tells PalDefender to read its config and whitelist again. The native ban list is Palworld's own.
Listing Online Players
From the panel: the Dashboard tab on the Game Tools page shows everyone connected, with name, level and ping. Player IP addresses are never shown. The Console tab answers ShowPlayers with the same roster including each player's id.
In game: /ShowPlayers lists the connected players with their ids.
The id is what kick and ban need. On a crossplay server it carries a platform prefix: steam_ (then the SteamID64) for Steam, gdk_ (then the XUID) for Xbox, ps5_ (then the PSN id) for PlayStation. Copy it exactly - there is no partial match.
Kicking Players
/KickPlayer [PlayerID] in game disconnects a player. They can rejoin immediately unless you also ban them.
From the panel: type KickPlayer <id> in the Console tab, without a leading slash.
Use a kick for temporary removal - a player is being disruptive but you want to give them a chance to cool down and come back.
Banning Players
/BanPlayer [PlayerID] in game bans a player, and the ban persists across restarts. From the panel, BanPlayer <id> in the Console tab does the same.
The native ban list is the file Pal/Saved/SaveGames/banlist.txt. Settings > Player Management > Banned Players (Native) is the panel editor for it, and adding an entry there is the same thing as banning by command.
Use the platform-prefixed id: steam_7656119XXXXXXXXXX, gdk_..., ps5_....
PalDefender keeps ban records of its own, at Pal/Binaries/Win64/PalDefender/Banlist.json, and checks them in addition to the native list. They are written by PalDefender itself: its anti-cheat (when Ban Cheaters or IP Ban Cheaters is on in the PalDefender tab) and its in-game /ban and /ipban commands. Each record keeps who banned the player, when and why, and an unban is recorded rather than deleted, so the file is a ban history rather than a list of ids. The panel does not list or edit it.
Banned players cannot rejoin. Use bans for griefers, cheaters, or players who repeatedly break your rules.
Unbanning Players
/UnBanPlayer [PlayerID] in game removes a player from the native ban list, and they can rejoin immediately. UnBanPlayer <id> in the Console tab does the same.
If PalDefender also has them banned, unbanning from the native list is not enough. An admin lifts a PalDefender ban in game with PalDefender's own command, /unban <id> (for example /unban steam_7656119XXXXXXXXXX), which updates its ban records for you. PalDefender's documentation advises against editing Banlist.json by hand.
If you are not sure of the exact id, read it off the Banned Players (Native) list in the panel.
Whitelisting
Vanilla Palworld has no whitelist. GameGrid gives you one anyway, because the platform installs PalDefender on every Palworld server.
The list is Settings > Player Management > PalDefender Whitelist, backed by Pal/Binaries/Win64/PalDefender/WhiteList.json. Add each player's id - steam_7656119XXXXXXXXXX and so on.
Adding entries is not enough on its own: the whitelist is only enforced once "Use Whitelist" is turned on in the PalDefender tab of the Game Tools page, under the Whitelist category. Turn it on, save, and restart (or run Reload PalDefender Config from the Command Manager).
PalDefender also accepts IP addresses on its whitelist. The panel adds player ids only; an address someone put there another way shows as [ip-hidden], and you can still remove it.
Add everyone before you restart. Once enforcement is on, anybody not on the list is refused.
A Server Password is the simpler alternative if your group is small. It is one shared secret, so it does not survive being passed around.
PalDefender Admin IPs
PalDefender only lets an admin use its commands from an address on its admin list, when "Use Admin Whitelist" is on in the PalDefender tab (it is on by default). The list is Settings > Player Management > PalDefender Admin IPs, which edits the adminIPs entry of Pal/Binaries/Win64/PalDefender/Config.json and leaves every other setting in that file as it was.
Type an IPv4 address, such as 203.0.113.7, or a range with * in place of the last parts, such as 203.0.113.*. Once added, an address is shown as [ip-hidden]: GameGrid never shows player IP addresses to server owners, and the addresses on this list are often your admins' rather than your own. To change one, remove it and add the new address. 127.0.0.1 is the server itself; it is on the list by default and is shown as it is.
The list is no longer in the PalDefender tab's Admin category; that category points here. Changes apply at the next restart, or straight away after Reload PalDefender Config in the Command Manager.