WARP settings define the WARP client modes and permissions available to end users.
- apply to all devices enrolled in your Zero Trust organization.
- may vary across devices depending on which is applied.
Enabled, end users can turn off the WARP client using a one-time code provided by an admin. This feature allows users to work around a temporary network issue (for example, an incompatible public WiFi, or a firewall at a customer site blocking the connection).
You can also set a Timeout to define how long the user is allowed to toggle on or off the WARP switch.
Retrieve the override code
To retrieve the one-time code for a user:
- Enable Admin override.
- Go to My Team > Devices.
- Select View for a connected device.
- Scroll down to User details and copy the 7-digit Override code.
- Share this code with the end user for them to enter on their device.
Enter the override code
To turn off the WARP client on a user device:
- In the WARP client, go to Settings > Preferences > Advanced.
- Select Enter code.
- Enter the override code in the pop-up window.
- Turn off the WARP switch.
The WARP client will now show Disabled by Admin Override and the time when the override code expires. The client will automatically reconnect after the , but the user can continue to turn off WARP until Admin override times out.
Captive portal detection
Captive portal detection is the ability for the WARP client to detect a third-party onboarding flow before Internet access is obtained. Captive portals typically occur in places such as airports, cafes, and hotels.
Enabled, the WARP client will automatically turn off when it detects a captive portal, and it will automatically turn back on after the Timeout duration.
Since captive portal implementations vary, WARP may not detect all captive portals. If captive portal detection does not work, you can provide end users with a temporary code. For more information, refer to the .
Lock WARP switch
Allows the user to turn off the WARP switch and disconnect the client.
Disabled: (default) The user is able to turn the switch on or off at their discretion. When the switch is off, the user will not have the ability to reach sites protected by Access that leverage certain device posture checks.
Enabled: The user is prevented from turning off the switch. The WARP client will always start in the connected state.
On new deployments, you must also include the
auto_connect parameter with at least a value of
0. This will prevent clients from being deployed in the off state without a way for users to manually enable them.
Allow device to leave organization
Enabled: (default) Users who manually enrolled their device are allowed to log out from your Zero Trust organization.
Disabled: Users who manually enrolled their device are prevented from leaving your Zero Trust organization. This disables the Logout from Zero Trust and Reset All Settings button in the WARP client interface. If the WARP client has been deployed with a management tool and a local policy exists, then this switch is bypassed and clients are always prevented from leaving.
Enabled, users will receive update notifications when a new version of the client is available. Only turn this on if your users are local administrators with the ability to add or remove software from their device.
We recommend keeping this set to a very low value — usually just enough time for a user to log in to hotel or airport WiFi. If any value is specified, the client defaults to the Connected state (for example, after a reboot or the initial install).
0: Allow the switch to stay in the off position indefinitely until the user turns it back on.
1440: Turn switch back on automatically after the specified number of minutes.
Enabled, the Send Feedback button in the WARP client appears and will launch the URL specified. Example Support URL values are:
https://support.example.com: Use an https:// link to open your companies internal help site.
mailto:[email protected]: Use a`mailto: link to open your default mail client.
- Gateway with WARP DNS and Device traffic is encrypted and processed by Gateway. This mode is required if you want to enable HTTP rules, Browser Isolation, Anti-Virus scanning and DLP.
- Gateway with DoH Enforcement of DNS policies only through DoH. All other traffic is handled by default mechanisms on your devices.
- Proxy Only Only traffic sent to the localhost proxy is encrypted by Gateway. This mode does not process DNS traffic.