In general, when you apply content or web filtering policies to a LAN network, those policies are typically enforced based on the IP addresses or IP ranges specified in the policy settings. If you add an IP address to a global whitelist (in this case, 192.168.22.10 to the Sangfor global whitelist), it usually means that the content filtering policies will not be applied to that specific IP address.

My understanding is that since the content and filters are deemed to satisfy all policies, there won't be any action taken.

There is absolutely no impact at all from going to Sangfor's global permission list where you create and add your LAN IP address, 192.168.22.10.

The LAN network's content/web filtering restrictions are normally not applied to IP addresses that are added to the Sangfor global whitelist, such as 192.168.22.10 (192.168.22.1/24). Sangfor NGAF typically gets around applied regulations for this IP address by whitelisting it, granting unrestricted access despite any limitations on the rest of the LAN network. Thus, the whitelisted IP would be unaffected by content filtering regulations, allowing it to access the internet and designated resources without any difficulty.

Yes, policies such as bandwidth, security, and application policies won't be applied to IP addresses that you place to the whitelist (in SOC).
However, bear in mind that this IP address is weak and could open a backdoor in your network security.
Thus, it is not advised.  

the IP address that you have on your global whitelist will not be affected by your policy. It is advised that you use a global whitelist to define a customized policy to accept or refuse communications for security purposes.

Whitelist mean allow your local address to communicate withe others some time these IP block then users faced some issue unable to open attachments, picture not displaying

No, the content/web filtering policy you applied to your LAN network will not be effective on the IP address 192.168.22.10 if it's added to the Sangfor global whitelist.

Here's how Sangfor NGAF prioritizes rules:

    Global Whitelist: Entries in the global whitelist take precedence over most other rules, including content/web filtering policies applied to specific networks.
    Network-Specific Policies: Rules applied to specific networks (like your LAN policy) are evaluated next.
    Default Policies: If no network-specific policies match, default policies are applied.

In your scenario:

    When traffic from 192.168.22.10 reaches the NGAF, it first checks the global whitelist.
    Since 192.168.22.10 is whitelisted, it's allowed to pass through without being subject to the LAN-specific content/web filtering policy.