> For the complete documentation index, see [llms.txt](https://doc.engenius.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.engenius.ai/fitcon100_um/configuring-networks/access-control.md).

# Access Control

In some cases, it is necessary to block a specific client on a  network. This configuration will apply to the whole network and will affect the client immediately.&#x20;

## Blocked List

Navigate to **Configure** > **Access Control** to access this screen.&#x20;

<figure><img src="https://2151473698-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2YGYl5TQ7IhZchwv09Ji%2Fuploads%2FHfeZXRK1slNvgdNLbbaR%2Fimage.png?alt=media&amp;token=1b2798a9-9529-41f8-9d30-5868839a5a08" alt=""><figcaption></figcaption></figure>

You could block clients in the current network or on SSID basis depending on your requirement. This blocked list displays which you added the blocked clients in **SSID** > **Access Control** and  **Manage > Clients** . So you could manage whole blocked clients easily in single lists. Noted that there is a limit of **1000** **clients** for blocking.&#x20;

### How to block clients

1. Click **Add** in the top-right corner .

&#x20;  2\. Enter the **Mac Address**  , select the **Scope** ( Current Network or  SSID basis) , then click **Apply**&#x20;

### How to Unblock clients

&#x20; 1\. Select the clients on the lists&#x20;

&#x20; 2\. Click **Unblock**

## VIP Lists

<figure><img src="https://2151473698-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2YGYl5TQ7IhZchwv09Ji%2Fuploads%2FKCtycsXYI9pUNuQQuR9o%2Fimage.png?alt=media&amp;token=91601518-3842-4a91-8c3a-0a20f6de8cf2" alt=""><figcaption></figcaption></figure>

All VIP clients can bypass Captive portal.   **Wired** VIP client can bypass L2 isolation .&#x20;

If **wireless** printer/scanner/IoT to be accessible, pls make sure the wireless printer/scanner/IoT devices are under SSID of

* **Bridge** mode
* L2 Isolation is **disabled**
* Optional: If captive portal is enabled on the SSID, the “VIP” can let the IoT skip captive portal entry

If **wired** printer / scanner / IoT device to be accessible, then

* Make the devices be “**VIP**” to all SSID’s (or to the SSID’s for the wireless clients to be able to access)
* Any wireless client can access.  No matter if NAT/Bridge mode.  L2 Isolation can be enabled / disabled

You could add the VIP clients in the current network or on SSID basis depending on your requirement. This VIP list displays which you added the VIP clients in **SSID** > **Access Control** and  **Manage > Clients** . So you could manage whole VIP clients easily in single lists. Noted that there is a limit of 50 **clients** for VIP.&#x20;

### How to Add VIP clients

<figure><img src="https://2151473698-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2YGYl5TQ7IhZchwv09Ji%2Fuploads%2FojNya6RW6I7uq0B4EUFU%2Fimage.png?alt=media&amp;token=3f24c5ce-2545-413f-9e64-bf0a27897a55" alt=""><figcaption></figcaption></figure>

1. Click **Add** in the top-right corner .

&#x20;  2\. Enter the **Mac Address**  , select the **Scope** ( Current Network or  SSID basis) , then click **Apply**&#x20;

### How to remove VIP clients

&#x20; 1\. Select the clients on the lists&#x20;

&#x20; 2\. Click **Delete**

{% hint style="info" %}

\
If L2 isolation is enabled, the whitelist clients will be excluded, which means clients under the subnet can access this client even L2 isolation is on (Only wired client can take effect )

If NAT mode, no whitelist client will be allowed. That means Under NAT mode, “client isolation” will be enabled automatically&#x20;
{% endhint %}

##


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.engenius.ai/fitcon100_um/configuring-networks/access-control.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
