Match this symptom
Friends who could previously join are refused after one user was added to permittedlist.txt, or display names do not work as entries.
The answer first
Back up the world and all permission files, then either list every intended player or intentionally clear permittedlist.txt. Valheim treats a non-empty permitted list as exclusive, and each line must contain the exact case-sensitive [Platform]_[User ID] value from F2 or the server log—not a display name.
Protect world and access-control state together
Permission files live in the save root and should travel with every world backup. Stop with CTRL+C, wait for process exit and copy adminlist.txt, bannedlist.txt, permittedlist.txt, the matched world pair and launch script before editing access.
Do not post the full server log publicly to obtain IDs. It can contain network, platform and filesystem details; extract only the required identifiers into a private working note.
- 1Warn connected players and stop with CTRL+C.
- 2Copy all three permission files and the active world pair.
- 3Redact join passwords, addresses and unrelated player IDs from support evidence.
Understand the exclusive-list behavior
Iron Gate says that once permittedlist.txt contains a user, everyone not in the file is refused. It is not a list of exceptions layered on top of normal public admission; it becomes the server's allowlist.
Choose one policy deliberately: keep the file empty for ordinary password-based admission, or maintain every approved platform identity. Do not leave a single test entry behind after diagnosing another player's access.
- Empty permittedlist: no allowlist restriction from this file.
- One or more entries: only listed users are admitted.
- bannedlist remains a separate denial control.
Use the exact platform-qualified identifier
Permission entries are case-sensitive and follow [Platform]_[User ID]. Iron Gate directs administrators to collect the value from the server log or the in-game F2 panel. A Steam/Xbox display name is not a stable substitute.
Cross-play makes this distinction important because two stores can represent identity differently. Copy the exact value reported by the current server/client rather than translating an old Steam ID guide by hand.
- 1Have the player attempt a join or open F2 in a controlled session.
- 2Copy the exact platform-qualified value, preserving case.
- 3Put one complete identifier per line with no commentary or display-name suffix.
Test admission and administration as separate permissions
permittedlist controls who may join; adminlist grants in-game admin commands, and bannedlist denies users. Adding a player to one does not imply membership in the others.
Restart, wait for Game server connected, and test with a non-owner account that should be admitted but not privileged. Then test an administrator's F5 command access. Keep the backup until both results match policy.
- Approved ordinary player: permitted, not automatically admin.
- Administrator: exact ID in adminlist, with separate admission requirements satisfied.
- Banned player: denied even if an old allowlist copy still contains the ID; verify current behavior after 1.0.