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

# How to Configure Whitelisting in DayZ

> Establish absolute control over server access. Learn how to implement player whitelisting for private events, streamers, and Roleplay (RP) communities.

## Managing Private Access Control

Whitelisting is an essential administrative protocol for private communities, streamers, and hardcore Roleplay (RP) environments. By implementing a whitelist, you ensure that only verified and authorized individuals can establish a connection to your server, effectively neutralizing the threat of stream-snipers, malicious griefers, or uninvited intruders. The FREAKHOSTING Game Panel supports both native vanilla whitelisting and advanced mod-based management for maximum flexibility.

<CardGroup cols={2}>
  <Card title="Difficulty" icon="gauge-low">
    Intermediate
  </Card>

  <Card title="Time" icon="clock">
    5 Minutes
  </Card>
</CardGroup>

***

## Access Control Methodologies

Choose the method that best aligns with your community's technical infrastructure and staff workflow.

<Tabs>
  <Tab title="VPPAdminTools (Recommended)">
    If your server uses the [VPPAdminTools Suite](/games/dayz/accessing-vpp-admin-tools), you can manage your whitelist through a powerful graphical interface.

    1. Open the VPP Dashboard in-game (**End** key).
    2. Navigate to the **Whitelist** module.
    3. Add players directly by their **SteamID64** or current in-game name.
    4. Configure a custom "Connection Rejected" message (e.g., "Join our Discord to apply for whitelist").
  </Tab>

  <Tab title="Vanilla Implementation (Manual)">
    This method uses the engine's native logic and does not require external modifications.

    1. In your `serverDZ.cfg`, locate and set `enableWhitelist = 1;`.
    2. Create a file named `whitelist.txt` within your server's root directory.
    3. Input the unique **BattlEye GUID** for every authorized survivor, with one entry per line.
       *Note: BattlEye GUIDs are technically distinct from SteamIDs, making this method more labor-intensive for administrators.*
  </Tab>
</Tabs>

***

## Identifying Unique Identifiers

To authorize a player, you must possess their specific network identifier.

<AccordionGroup>
  <Accordion title="Retrieving SteamID64">
    The 17-digit SteamID64 is the primary identifier used by most mods. You can retrieve this by inputting a player's Steam profile URL into tools like [SteamID.io](https://steamid.io).
  </Accordion>

  <Accordion title="Converting to BattlEye GUID">
    If using the vanilla whitelist, you must convert the SteamID64 into a 32-character BattlEye GUID. This conversion can be performed through various community-made online converters or administrative plugins.
  </Accordion>
</AccordionGroup>

<Warning>
  ### Maintaining Whitelist Integrity

  If you choose to enable the `enableWhitelist` variable in your configuration, the server will **strictly reject** any player whose identifier is not present in your registry. Ensure your administrative team is added to the list first to avoid locking yourself out of your own server.
</Warning>

***

<Note>
  ### Need Extra Help?

  If you encounter any issues, our support team is ready to assist:

  * **Live Chat:** Quick assistance via our website.
  * **Support Ticket:** [Open a Ticket](https://freakhosting.com/clientarea/submitticket.php)
  * **Discord:** [Join our Community](https://discord.gg/freakhosting)
  * **Email:** [support@freakhosting.com](mailto:support@freakhosting.com)
</Note>

<Tip>
  ### Save on Your Hosting

  Ready to get a new server? Use code **KB20** at checkout for **20% off** your first month!
</Tip>

***

<div align="center">
  **Last Updated:** January 2026 | **Moderation:** Verified players only.
</div>