# 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
Enabling Social Requirements
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.
## Allow and Deny Players Whitelist
Allow and Deny List
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.
## 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
Lock via CMS
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.
#### Lock via Discord
Lock via Discord
Team locks can also be configured via [Discord bot](https://docs.sonoransoftware.com/cms/integration-capabilities/discord-bot-integration) by using the `/erlc lock` and `/erlc unlock` commands.
#### Lock Actions
Lock Actions
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.
### Team Restrictions
Team Restrictions
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.
## Vehicle & Livery Restrictions
Vehicle & Livery Restrictions
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.
## AOP (Area-of-Play)
AOP Restrictions
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.
