> ## Documentation Index
> Fetch the complete documentation index at: https://docs.purpify.host/llms.txt
> Use this file to discover all available pages before exploring further.

# Whitelist Bedrock players

> Restrict a native Minecraft Bedrock Edition server to approved Xbox Gamertags.

Use the allowlist to restrict a native Minecraft Bedrock Edition server to approved Xbox Gamertags. Minecraft Bedrock Edition uses the term `allowlist`, although it also accepts `whitelist` as a command alias.

<Warning>
  Add yourself before enabling the allowlist. Otherwise, you may be unable to reconnect until you add yourself through the Purpify game panel console.
</Warning>

## Before you begin

* Start the server and wait until it finishes loading.
* Use each player's exact Xbox Gamertag, including spaces and capitalization.
* Put a Gamertag in quotation marks when it contains spaces, such as `"Example Player"`.
* Confirm that this is a native Bedrock server. For Bedrock players joining through Geyser, use the Java server's allowlist or permission system.

## Enable the allowlist

<Steps>
  <Step title="Add approved players">
    Open the game panel console and add each player's exact Xbox Gamertag. Enter console commands without a leading `/`.

    ```text theme={"dark"}
    allowlist add "Example Player"
    ```
  </Step>

  <Step title="Stop the server">
    Stop the server before editing `server.properties` so the running process does not overwrite your change.
  </Step>

  <Step title="Enable the allowlist">
    Open the file manager, edit `server.properties`, and set `allow-list` to `true`. Save the file.

    ```properties theme={"dark"}
    allow-list=true
    ```
  </Step>

  <Step title="Restart the server">
    Start the server and watch the console for startup errors.
  </Step>

  <Step title="Check the approved players">
    List the allowlisted players and confirm that the expected Gamertags appear.

    ```text theme={"dark"}
    allowlist list
    ```
  </Step>
</Steps>

## Manage the allowlist

| Task                                     | Method                                                                                |
| ---------------------------------------- | ------------------------------------------------------------------------------------- |
| Add a player                             | `allowlist add "Example Player"`                                                      |
| Remove a player                          | `allowlist remove "Example Player"`                                                   |
| List approved players                    | `allowlist list`                                                                      |
| Reload `allowlist.json` after editing it | `allowlist reload`                                                                    |
| Disable the allowlist                    | Set `allow-list=false` in `server.properties`, save the file, and restart the server. |

Removing a player from the allowlist prevents the next connection attempt. If the player is already connected, [kick the player](/bedrock/kick-player) as well.

## Fix common problems

<AccordionGroup>
  <Accordion title="An approved player cannot connect">
    Run `allowlist list` and compare the Gamertag exactly. Add the player again if needed, then run `allowlist reload`.
  </Accordion>

  <Accordion title="The command is unknown">
    Confirm that the server is running native Minecraft Bedrock Edition. Enter commands without `/` in the game panel console and with `/` in Minecraft chat.
  </Accordion>

  <Accordion title="The player joins through Geyser">
    Geyser provides Bedrock-to-Java cross-play. Manage the player with the Java server's allowlist or plugin permission system instead of this native Bedrock procedure.
  </Accordion>
</AccordionGroup>