Cloudflare Docs
Learning Paths
Edit this page
Report an issue with this page
Log into the Cloudflare dashboard
Set theme to dark (⇧+D)

Define device enrollment permissions

  2 min read

Device enrollment permissions determine which users can connect new devices to your organization’s Cloudflare Zero Trust instance. Once the user registers their device, the WARP client will store their identity token and use it to authenticate to services in your private network.

​​ Set device enrollment permissions

  1. In Zero Trust, go to Settings > WARP Client.
  2. In Device enrollment permissions, select Manage.
  3. In the Rules tab, configure one or more Access policies to define who can join their device. For example, you could allow all users with a company email address:
    Rule typeSelectorValue
    IncludeEmails ending
  4. In the Authentication tab, select the identity providers users can authenticate with. If you have not integrated an identity provider, you can use the one-time PIN.
  5. Select Save.

​​ Only allow corporate devices

Device posture evaluation happens after a device has already enrolled in your Zero Trust organization. If you want only specific devices to be able to enroll, we recommend adding a mutual TLS authentication rule to your device enrollment policy. This rule will check for the presence of a specific client certificate on the enrolling devices.

To check for an mTLS certificate:

  1. Add an mTLS certificate to your account. You can generate a sample certificate using the Cloudflare PKI toolkit.

  2. In Associated hostnames, enter your Zero Trust team domain: <team-name>

  3. In your device enrollment permissions, add a Common Name or Valid Certificate rule. For example, the following policy requires a client certificate with a specific common name:

    ActionRule typeSelectorValue
    AllowRequireCommon Name<CERT-COMMON-NAME>
  4. On your device, add the client certificate to the system keychain.

​​ Best practices

Most businesses use a single identity provider as the source of truth for their user directory. You should use this source of truth to onboard your corporate users to Zero Trust, for example by requiring company email addresses to login with your primary identity provider. Later on, you can add other login methods or identity providers as necessary for any contractors, vendors, or acquired corporations who may need access to your network.