Passkeys and autofill are connected because modern phones surface passkeys through the same credential-selection flow used for saved passwords and other sign-in data. When a login field is detected, your operating system or password manager can offer a saved password or a passkey, then complete sign-in after biometric or device verification.

For Kuda Business, passkeys are the only way to sign in after your first setup. If autofill is disabled, pointed at the wrong provider, or only configured in the browser (not on the device), passkey prompts may not appear when you expect them.

How passkeys relate to autofill

Autofill is the user-facing mechanism that helps your device recognize sign-in fields and offer stored credentials without manual typing. A passkey is a passwordless credential tied to a specific site or app, but from your perspective it often appears through the same suggestion sheet or prompt used by autofill.

That is why passkey settings are usually grouped with passwords, passkeys, and autofill in the same part of system settings.

On Android, Google Password Manager stores passkeys and can offer them during sign-in as part of the credential flow.
On iPhone, passkeys work with AutoFill and Face ID or Touch ID, so the sign-in experience feels similar to standard autofill even though the underlying credential is different.

Why this matters for Kuda Business

A simple rule: passkeys depend on the same device-level credential plumbing as password autofill, even though passkeys are more secure than passwords.

When troubleshooting passkey issues on Kuda Business, checking autofill and your preferred credential provider is often one of the first practical steps—before assuming the app is broken.

What Kuda Business requires vs what we recommend:

Required: Passkeys for sign-in after your first setup (no ongoing password login).
Recommended on iPhone: iCloud Keychain with AutoFill Passwords and Passkeys — this is how iOS stores and offers passkeys.
Recommended on Android: Google Password Manager as your autofill service. Kuda does not block other password managers, but we recommend Google because most passkey issues we see come from the wrong autofill provider or a passkey stored in a different manager than the one offering credentials at login.

Where to check settings

iPhone

What	Where to check
Passkey storage and sync	Settings > [Apple ID] > iCloud > Passwords and Keychain — turn on Sync this iPhone
Passkey autofill at sign-in	Settings > Passwords > Password Options — turn on AutoFill Passwords and Passkeys, select iCloud Passwords & Keychain
Form autofill (web only)	Settings > Safari > AutoFill — for name/address/email in forms, not passkey login

Passkeys are surfaced through AutoFill and verified with Face ID, Touch ID, or your device passcode.

Android (including Samsung, Tecno, Infinix)

What	Where to check
Device autofill provider	Settings > Passwords, passkeys & accounts or Settings > System > Languages & input > Autofill service — we recommend Google
Samsung shortcut	Settings > General management > Passwords, passkeys and autofill — select Google if you use Google Password Manager
Google autofill toggle	Settings > Google > Autofill > Autofill with Google — turn ON
Chrome (web sign-in)	Chrome > Settings > Autofill services — confirm Google is active
Transsion / HiOS / XOS	Use the Settings search bar and look for autofill, passwords, or password manager if menus differ by model

If passkeys are stored with Google Password Manager, Android can surface them from the autofill interface during login.

Samsung Pass: We recommend Google Password Manager for Kuda Business passkeys. Kuda does not force a specific provider, but if Samsung Pass (or another manager) is your default autofill service, it may not offer a passkey that was saved in Google Password Manager.

Samsung Internet (web only)

If you use Samsung Internet instead of Chrome, also check Internet > Menu > Settings > Personal browsing data > Autofill forms. Browser-level form autofill is separate from device-wide passkey storage.

Device-level vs browser-level settings

Form autofill, password autofill, and passkey presentation can feel like one feature, but they may be controlled by different menus:

Device-level — which password manager (Google or iCloud) offers credentials to apps and browsers
Browser-level — Chrome or Samsung Internet autofill for web pages

If passkeys fail only in one browser, check both the phone's main autofill settings and that browser's autofill settings.

Practical troubleshooting steps

When passkeys do not show up for Kuda Business:

Confirm an autofill or password-manager service is selected at the device level and matches where your passkey is stored (we recommend Google on Android, iCloud on iPhone).
Verify the passkey was saved to that same provider and Google/Apple account you are signed into now.
Confirm screen lock and biometric unlock are enabled.
If the issue happens only on web, check the browser's autofill settings as well.
Update the Kuda Business app, your OS, and Chrome (if using web).

For Kuda-specific flows (QR sign-in, new phone, passkey reset), see Troubleshooting Passkey Issues on Kuda Business.