Minecraft Bedrock Allowlist: Invite the Right Accounts

A Minecraft Bedrock allowlist controls which accounts can join a private dedicated server. Use it when the world should stay limited to a known group rather than anyone who receives the address.

Treat the allowlist as one part of administration. It does not grant or replace operator privileges, backups, or account security.

Gather the correct identities

Ask players for the exact account identity required by the server's current allowlist workflow. Display names in a chat app are not a reliable substitute.

Check the dedicated server's bundled instructions for the file format and supported commands. The official Bedrock server download page is the starting point for the distributed server package.

Keep private access information out of public screenshots and invitations.

Configure and test admission

Back up the relevant configuration before editing it. Use the server's documented allowlist controls and restart or reload only as its instructions require.

Test with an approved account, then with a test account that has not been approved. That second test confirms the server enforces the restriction rather than merely maintaining an unused list.

If a friend is refused, compare the account, address, and edition before changing security settings. Also check whether the panel overwrites manual file changes.

Maintain the list

Review entries when the group changes. Keep a record of who approves invitations and who can edit the list. Back it up alongside the server configuration.

Is the Bedrock allowlist identical to a Java whitelist?

They serve a similar admission purpose, but use the documentation and account format for the server you actually run.

For edition-specific hosting context, read our Bedrock hosting guide.

Choose your next step

Compare EZ Game Host Minecraft hosting for your group. Choose resources for your actual world and workload, then keep a downloadable backup before changing hosts.