Passcode Policy for iOS Devices

Passcode Policy allows you to create and enforce the passcode settings from Scalefusion Dashboard. This enables you to make sure that all your employees are forced to set a passcode on device thereby preventing accidental data loss.

In this tutorial we will learn on how to Create and Apply a Passcode Policy to iOS devices.

Video Guide:

Please watch the video below to get a visual walkthrough.

Creating a Passcode Policy

  1. Log-In to your Scalefusion Dashboard.
  2. Navigate to Device Profiles & Policies > Passcode Policy and click on iOS tab.
  3. Enable Require Passcode.
  4. Choose the type of passcode that you want to enforce, that is either Numeric or Alphanumeric.
  5. Select the length of the passcode. On iOS this needs to be a minimum of 4.
  6. Enable Enforce Complex Passcode if you want to enforce a passcode to contain Symbols
  7. Once you are done, click Save Policy.

Applying a Passcode Policy

  1. Navigate to Device Profiles & Policies > Passcode Policy.
  2. To apply the created Passcode policy, click on Apply to Device button.
  3. Choose the Device Profiles where you want to apply this to. Note - You can publish onto individual iOS devices.
  4. Click on SUBMIT.
  5. The device(s) associated with the Device Profiles where you have published this policy will show a dialog to set the passcode.
By default iOS gives a grace period of 60 minutes. Scalefusion currently does not offer a way to control this. Unless the grace period is complete, the passcode dialog is not shown unless user opens and minimises the Settings app on device.

Removing the Passcode from Devices

  1. Navigate to Device Profiles & Policies > Passcode Policy.
  2. Click on Delete icon.
  3. Select the Device Profiles from which you want to remove the passcode policy and click SUBMIT.
  4. Scalefusion will not enforce the passcode policy on the device and will also attempt to remove the passcode from the device.

If you still face any issues please contact at or send your feedback on this article itself.

How did we do?

Powered by HelpDocs (opens in a new tab)