> ## Documentation Index > Fetch the complete documentation index at: https://docs.safesquid.com/llms.txt > Use this file to discover all available pages before exploring further. # Allow Anydesk > Allow AnyDesk and other remote desktop apps through SafeSquid with user profiles, SSL bypass, and request-type filters. ## Problem Security teams need predictable control over app and web usage to reduce policy bypass and data-risk exposure. ## Benefits You can enforce policy decisions consistently with SafeSquid while preserving legitimate business workflows. ## Advantages You keep actionable policy control close to operations, with verifiable outcomes in logs and policy behavior. ## Call to action Use the steps in this guide to implement the control, then validate behavior with a real user-flow test. ## Allow remote applications for specific users When all traffic is blocked for security, some users may need access to remote applications. SafeSquid allows the administrator to permit specific users or groups to access remote applications. ## How it works? When a user tries to access a remote application, First SafeSquid checks for that user and decides whether this user is allowed to access a remote application or not, if yes then SafeSquid gives access to that user, and before giving the access it will check for user-agent. If access is allowed to both users and the application, then only the user can able to access that application. If the user **Samidha wants access** to the XYZ application but is trying to access the **ABC** application, SafeSquid will block to user Samidha. ```mermaid theme={null} flowchart LR User[User request] CheckUser[Check user allowed] CheckApp[Check application] Allow[Allow] Block[Block] User --> CheckUser CheckUser -->|no| Block CheckUser -->|yes| CheckApp CheckApp -->|no| Block CheckApp -->|yes| Allow ``` :::note Remote applications like Anydesk® and Ammyadmin™ do not support SSO authentication. If SSO authentication is enabled, bypass it for these applications. ::: Remote applications like **Remote desktop applications, Download managers**, etc. (Anydesk and Teamviewer®) should get automatically blocked if HTTPS inspection is enabled. No need to configure any policy for blocking purposes. ## [Access the SafeSquid interface](/Configuration_Portal) ## Go to configure page Go to configure page to Allow anydesk ## Go to Real-time content security: HTTPS Inspection Select HTTPS Inspection option in Real time content security section to Allow anydesk Enabled Global section as true to allow anydesk Bypass SSL inspection by editing policy in Inspection policy section Select enabled as true of Bypass SSL Inspection policy to allow anydesk Save Bypass SSL Inspection policy to allow anydesk ## Go to Restriction Policies Select Access profiles in Restriction policies section to allow anydesk Default Restrict remote desktop application policies present in policies and profiles section Edit one of clone policy in policies and profile section to allow anydesk Edit and entry comment and request type in policy to allow anydesk Select Bypass SSL Inspection in added profiles section to allow anydesk Save Allow anydesk policy Save configuration of policy to allow anydesk ## Configuration on Anydesk® ### Set proxy on Anydesk application If authentication is enabled, specify the username and password in the AnyDesk application. AnyDesk does not use system proxy settings automatically. Configure the proxy in the AnyDesk application. AnyDesk and Ammyadmin do not support SSO; bypass SSO for them if enabled. ### Create policy without application signature Remote applications may already exist in SafeSquid Application Signatures. Check whether the application is categorized first. If an application is not categorized under default Application Signatures, find the User-agent using SafeSquid's extended logs or any other traffic-capturing tool. ### Add that User-agent or website into request types Bind that created user group and Request Type in Access Profiles and decide whether to block or allow. ## Verification and Evidence * **Interface Checks**: In [Configuration Portal](/Configuration_Portal), confirm Real-time content security → HTTPS Inspection has Bypass SSL Inspection policy enabled, and Restriction Policies → Access profiles show the allow policy for the remote desktop application with the correct request type and Bypass SSL Inspection profile. * **Log Analysis**: SafeSquid access logs should show successful CONNECT or requests for the remote app when allowed; blocked attempts appear with deny or policy response codes. * **Performance Validation**: From an allowed user and device, launch [AnyDesk](https://anydesk.com/) (or the configured app) with proxy set; connection should succeed. From a non-allowed user or app, access should be blocked. **Related**: [SSL Inspection](/SSL_Inspection), [Access Restriction](/Access_Restriction), [Architecture](/safesquid_swg/architecture/safesquid_swg), [Restrict AnyDesk](/Restrict_anydesk), [Troubleshooting](/Troubleshooting) ## Related topics - [Allow Remote Applications to Particular Users](/use_cases/access_restriction/allow_remote_applications_to_particular_users.md) - [Restrict AnyDesk](/use_cases/access_restriction/restrict_anydesk.md) - [Access Remote Desktop Applications Through SafeSquid](/use_cases/access_restriction/access_remote_desktop_applications_through_safesquid.md) - [Profiling Engine](/use_cases/profiling_engine/profiling_engine.md) - [Allow Specific Page on Facebook](/use_cases/content_modifier/allowing_specific_page_on_facebook.md)