> ## 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 Private Access Control in BeamMP

> Secure your driving environment. Learn how to manage server visibility and implement private access control for leagues and closed-group BeamMP sessions.

## Securing Your Digital Driving Sanctuary

Establishing a private environment is essential for hosting organized league races, dedicated technical testing, or exclusive social cruises with a specific group of friends. By correctly configuring your server visibility and implementing access control, you ensure that your session remains protected from uninvited intruders and randomized griefers. The BeamMP (BeamNG.drive Multiplayer) engine provides several technical methods for managing accessibility, ranging from masterlist exclusion to specialized ID-based whitelisting.

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

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

***

## Strategic Visibility Calibration

The primary method for restricting access is governing how the server communicates with the global BeamMP masterlist.

<Steps>
  <Step title="Initialize Maintenance">
    Log in to the [Game Panel](https://games.freakhosting.com) and **Stop** your server.
  </Step>

  <Step title="Access the Configuration">
    Navigate to the **Files** tab and open the `ServerConfig.toml` file.
  </Step>

  <Step title="Update Visibility Policy">
    Locate the `Private` parameter. Set this value to **`true`**.

    * **Technical Result:** Your server will no longer appear in the public in-game browser. It will not broadcast its existence to the global masterlist.
  </Step>

  <Step title="Apply and Restart">
    Save the file and **Start** your server.
  </Step>
</Steps>

***

## Technical Access Methodology

When a server is configured as `Private`, participants must use the **Direct Connect** protocol to establish a connection.

* **Onboarding Workflow:** Instruct your community members to open the BeamMP launcher and navigate to the **Direct Connect** tab.
* **Identification:** They must manually input your numerical FREAKHOSTING IP address and specific Port (e.g., `191.96.94.100:30005`).

***

## Advanced Security: ID-Based Whitelisting

Because vanilla BeamMP lacks a native password field in many build versions, administrators requiring high security should implement a specialized **Lua Whitelist Resource**.

<AccordionGroup>
  <Accordion title="Implementing a Whitelist Script">
    Deploy a reputable whitelisting resource into your `/Resources/Server/` directory. These scripts programmatically intercept the `onPlayerJoin` event and verify the participant's **BeamMP User ID** against your authorized registry. If the identifier is missing, the script forcefully disconnects the client before they can spawn a vehicle.
  </Accordion>

  <Accordion title="Strategic Advantages">
    Whitelisting is technically superior to a shared password, as it allows you to grant access to individual users without the risk of a single password string being leaked or shared publicly.
  </Accordion>
</AccordionGroup>

***

<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 | **Security:** Total access control.
</div>