The rendering of fields in the Ory Elements components like

UserSettingsCard

or

UserAuthCard

depends on the configuration of your Ory Network project and the identity schema you have defined. If you have enabled passwordless flows, users should see the option to register a new hardware key in the settings page. If passwordless flows are disabled, the option to add hardware keys won't be visible in the UI. Make sure you have enabled the passkey strategy in your Ory Console or via the Ory CLI. For the passkey to work, you must define which field of the identity schema is the display name for the passkey. If you do not define the

passkey.display_name

field, the

webauthn.identifier

will be used as a fallback. If neither is defined, the passkey strategy will not work. Also, ensure that the required fields in your identity schema are correctly defined. If the fields are not marked as required, they may not be rendered as expected in the UI. If you're still facing issues, you might want to check the code of your settings page. The settings page is defined in the

settings.tsx

file and changes dynamically based on the configuration of your Ory Network project. You can find examples of this file for different frameworks (React, Preact, Next.js) in the Ory Elements GitHub repository. Sources: - [Passkeys with the dedicated passkey strategy - Identity schema](https://www.ory.sh/docs/kratos/passwordless/passkeys#identity-schema) - [Custom user interface with Ory Elements - Settings page](https://www.ory.sh/docs/kratos/bring-your-own-ui/custom-ui-ory-elements#settings-page) - [Passkeys with the dedicated passkey strategy - Configuration](https://www.ory.sh/docs/kratos/passwordless/passkeys#configuration) - [Customize identity schemas - Mandatory fields for registration](https://www.ory.sh/docs/kratos/manage-identities/customize-identity-schema#mandatory-fields-for-registration)