# Whitelist

## Social Requirements

The `Social Requirements` section allows you to require that CMS accounts be linked to both Discord and Roblox accounts. When users have both social accounts connected, the ER:LC panel and Discord integrations can operate with full functionality.

### Enabling Social Requirements

<details>

<summary>Enabling Social Requirements</summary>

Toggle the `Roblox` and/or `Discord` requirement(s). Then, define custom actions to trigger when a user joins your ER:LC panel without having a linked Roblox or Discord account in the CMS.

Available actions include public or private in-game messages, Discord webhooks, push notifications, and more.

<div><figure><img src="/files/0D32XZCRhXXufazAlhKr" alt="" width="375"><figcaption></figcaption></figure> <figure><img src="/files/TQl2zWpxERmIANWBfuY0" alt="" width="243"><figcaption></figcaption></figure></div>

</details>

## Allow and Deny Players Whitelist

<details>

<summary>Allow and Deny List</summary>

The allow and deny lists let you control game access based on CMS ranks. These lists are activated once one or more ranks are configured.

When enabled, only users with a Roblox account linked to a CMS account that holds an **allowed rank** can join the server. Users without an allowed rank will be kicked automatically.

If a user’s CMS rank appears on the **deny list**, that restriction overrides the allow list — those users will be kicked upon joining.

<figure><img src="/files/aJyNjdSY5UUGSfTDncoE" alt="" width="375"><figcaption></figcaption></figure>

</details>

## Team Locks and Restrictions

### Team Locks

Each ER:LC team can be locked down to a maximum amount of players. Teams can be locked via the CMS **Lock** icon, or via Discord bot command.

#### Lock via CMS

<details>

<summary>Lock via CMS</summary>

Next to the team, select the **Lock** icon to enable or disable the lock, then enter a number into the **Max**

Use the **Shield** icon to add CMS ranks that bypass and ignore this lock.

<figure><img src="/files/oCEYZfNDl2p9fpJla7nL" alt="" width="375"><figcaption></figcaption></figure>

</details>

#### Lock via Discord

<details>

<summary>Lock via Discord</summary>

Team locks can also be configured via [Discord bot](/cms/integration-capabilities/discord-bot-integration.md) by using the `/erlc lock` and `/erlc unlock` commands.

<figure><img src="/files/Z3j8iEvBXgT9baaLZK29" alt=""><figcaption></figcaption></figure>

</details>

#### Lock Actions

<details>

<summary>Lock Actions</summary>

When a player joins a team that has already reached its maximum amount of players, custom actions can be used to kick the user off of the team, send a message, Discord webhook, and more!

Select **Actions** next to the team > Add a new action > And toggle the mode to **Lock** to apply this action whenever a team lock is reached.

<figure><img src="/files/mtlx0dDbGV80rfTO1GgV" alt="" width="375"><figcaption></figcaption></figure>

<div><figure><img src="/files/sBvifEyd4R2Qcg4yCcuI" alt="" width="286"><figcaption></figcaption></figure> <figure><img src="/files/XxZjgxg6umhDdsMyJmpH" alt="" width="286"><figcaption></figcaption></figure></div>

</details>

### Team Restrictions

<details>

<summary>Team Restrictions</summary>

Each team can also be locked to users with specific CMS ranks.

Select the **Shield** icon to configure which ranks are allowed to join the team.

Select the **Actions** panel to create actions that apply when a user joins a team without the proper CMS rank.

<div><figure><img src="/files/OzYeSrkUIMRzBvxEeCbW" alt=""><figcaption></figcaption></figure> <figure><img src="/files/JWUQ1LVVZx3BSg4guJBb" alt=""><figcaption></figcaption></figure></div>

</details>

## Vehicle & Livery Restrictions

<details>

<summary>Vehicle &#x26; Livery Restrictions</summary>

Vehicles and vehicle liveries can also be restricted to users with specific CMS ranks.

Just like teams, select the **Shield** icon to which ranks are allowed to use the vehicle and vehicle liveries.

Select the **Actions** panel to create actions that apply when a user uses a vehicle or livery without the proper CMS rank.

<div><figure><img src="/files/8ka6bnD0hTKDKott6rjo" alt="" width="375"><figcaption></figcaption></figure> <figure><img src="/files/dmMp3hIvgb00hJHIiTFO" alt="" width="246"><figcaption></figcaption></figure></div>

</details>

## AOP (Area-of-Play)

<details>

<summary>AOP Restrictions</summary>

Some communities wish to restrict users to an AOP (area-of-play) on the map.

In the CMS, use the polygon, square, or circle tool to create a custom AOP. Once created, the AOP can be enabled and disabled. Select the **Actions** tab to configure custom CMS automations that will fire once a player is outside of all enabled AOPs.

Select the **Rank** button to add CMS ranks that bypass AOP restrictions.

<figure><img src="/files/sfdbNNiUFjn5x2OBgJzz" alt=""><figcaption></figcaption></figure>

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sonoransoftware.com/cms/integration-capabilities/er-lc-game-panel/usage/whitelist.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.