Safari password AutoFill not saving passwords on iOS after switching from ChromeSolved

Participant
Discussion
4 days ago Nov 18, 2026

We recently changed an iOS policy so users open a web app in Safari instead of Chrome. When the same site was opened in Chrome, users could save their passwords. After moving to Safari, they are reporting that passwords are not being saved.

In the Hexnode policy, Safari AutoFill is allowed under the iOS restrictions. Does Safari need something else enabled separately on the device, or should it work automatically because Chrome was already saving passwords?

Replies (3)

Marked SolutionPending Review
Participant
4 days ago Nov 18, 2026
Marked SolutionPending Review

So enabling password saving in Chrome does not automatically enable it for Safari? We assumed it would carry over since it is the same iPad and same website.

Marked SolutionPending Review
Hexnode Expert
4 days ago Nov 18, 2026
Marked SolutionPending Review

Yes @yu-yan , Safari password saving also depends on the local AutoFill settings on the iOS device.

If Safari AutoFill is allowed in the Hexnode UEM policy, the policy is not blocking the feature. However, users must still ensure that AutoFill is enabled on the device itself.

Check the following settings on the iOS device:

  1. Go to Settings > Safari > AutoFill and enable the available AutoFill options.
  2. Go to Settings > Passwords > Password Options and make sure AutoFill Passwords and Passkeys is enabled.

Once these settings are enabled locally, Safari should be able to save and AutoFill passwords for websites, provided the website itself supports password saving.

Regards,
Isabel Lora
Hexnode UEM

Marked SolutionPending Review
Hexnode Expert
4 days ago Nov 18, 2026
Marked SolutionPending Review

iOS treats Safari, Chrome, and password AutoFill settings as separate areas. A password-saving setup that worked in Chrome does not automatically mean Safari AutoFill is enabled or configured.

Hexnode UEM can allow or restrict Safari AutoFill through policy, but the user-side iOS settings still control whether Safari can actually use AutoFill. After switching the workflow from Chrome to Safari, users should verify the Safari AutoFill and Password Options settings directly on the device.

Regards,
Isabel Lora
Hexnode UEM

Save