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 five sections there: Banned Players (Native), PalDefender Bans, 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.
The three PalDefender lists need a server restart to take effect. 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, ping and IP. 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_76561198012345678, gdk_..., ps5_....
PalDefender keeps a SECOND ban list of its own, at Pal/Binaries/Win64/PalDefender/Banlist.json, and checks it in addition to the native one. It is the Settings > Player Management > PalDefender Bans section, it lets you record a reason, and changes to it need a server restart.
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 - remove them from PalDefender Bans in Settings > Player Management as well, and restart.
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_76561198012345678 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.
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 also has an admin IP whitelist: Settings > Player Management > PalDefender Admin IPs, enforced by the "Use Admin Whitelist" toggle on the same PalDefender tab. 127.0.0.1 is included by default so the platform itself keeps working. Both need a restart.