Google 的研究表明，许多用户将生物识别与安全性相关联。虽然通行密钥不需要生物识别信息（例如，通行密钥可以与设备 PIN 码搭配使用），但将通行密钥与生物识别信息相关联可让用户更熟悉通行密钥，并提升用户对安全优势的感知度。例如，在 Google 账号中，通行密钥始终与熟悉的安全性功能（可启用通行密钥）紧密结合在一起：指纹、人脸扫描或其他设备屏锁。
[null,null,["最后更新时间 (UTC)：2025-07-26。"],[[["\u003cp\u003ePasskeys are a new, more secure way to sign in, and associating them with familiar concepts like biometrics can improve user understanding and adoption.\u003c/p\u003e\n"],["\u003cp\u003eWhen introducing passkeys, highlight benefits relevant to your users, such as speed, convenience, or enhanced security, depending on your platform and target audience.\u003c/p\u003e\n"],["\u003cp\u003eProvide clear, visible information about passkeys at every step of the user journey, including before, during, and after interactions with OS dialogs for creation and usage.\u003c/p\u003e\n"],["\u003cp\u003eDesign passkey creation to include a username (ideally an email for recovery) and a display name for easy user identification within credential lists.\u003c/p\u003e\n"],["\u003cp\u003eTreat passkeys as a primary authentication method in account settings, giving them equal prominence to options like username/password or two-factor authentication.\u003c/p\u003e\n"]]],[],null,["# Communicating passkeys to users\n\n| **Note:** This article is a part of a series about designing passkeys user experiences on the web that includes [Passkeys user journeys](/identity/passkeys/ux/user-journeys) and [Passkeys user interface design](/identity/passkeys/ux/user-interface-design).\n\nPasskeys are a new technology that enables creating online accounts and signing\nin to them without using passwords. They are more convenient and secure, but\nthey are also unfamiliar to a lot of users. These guidelines will help you\novercome that by creating content design that improves user experience and\nhelps your users be successful with passkeys.\n\nAssociate passkeys with familiar concepts\n-----------------------------------------\n\nBecause passkeys are a new concept, whenever possible in your content design\nassociate them with familiar concepts, visuals, and experiences, such as\nbiometrics or passwords. We recommend that you use the term passkeys explicitly\nin your UI because it's a step towards educating users and making passkeys a\ncommon term.\n\nGoogle's research has shown that many users associate biometrics with security.\nWhile passkeys don't require biometrics (a passkey can be used with a device\nPIN, for example), associating them with biometrics makes them more familiar\nand can boost user perception of security benefits. For example, in\nGoogle Accounts passkeys are consistently nestled amongst the familiar security\nexperiences that enable passkey use: fingerprint, face scan, or other device\nscreen lock.\n\n\u003cbr /\u003e\n\nPasskeys in Google Accounts are mentioned alongside with fingerprint, face scan, or other device screen lock.\n\n\u003cbr /\u003e\n\nEmphasize benefits relevant to your user base\n---------------------------------------------\n\nWhen introducing users to passkeys, emphasize the practical benefits that\ndirectly align with their needs and preferences.\n\nUse clear and concise language that emphasizes the benefits that will resonate\nwith your user base, such as speed, ease of use, and the familiarity of screen\nlock features that eliminate the need to remember unique usernames and\npasswords.\n\nKeep in mind that different user bases may have different priorities and tailor\nyour messaging to highlight the benefits that are most relevant to your\naudience.\n\nThe UX for passkeys on Google Accounts highlights speed and convenience which\nhas proven effective, and similar advantages may resonate with your users as\nwell.\n\nFor example, if your platform is an e-commerce service, the convenience and\nspeed might be the most attractive features.\n\nAnother example are banks or services that handle sensitive information, where\nemphasizing the enhanced security that passkeys provide could be a compelling\nselling point for users.\n\nCarefully identify what is most valuable to your users and craft your messaging\nto highlight those specific benefits.\n\n\u003cbr /\u003e\n\nGoogle Accounts page for creating passkeys, highlighting the simplicity of user experience. \n\nA mockup of a fitness app, highlighting the speed of signing in with passkeys. \n\nA mockup of a bank app, with the next image showing a pop-up prompt suggesting that the user upgrade to Passkeys.\n\n\u003cbr /\u003e\n\nShow helpful information about passkeys at every step\n-----------------------------------------------------\n\nFor any passkeys related actions, show users clear messages in your app UI\nbefore triggering the operating system (OS) dialogs. After the passkeys OS\ndialogs are completed or dismissed, show the resulting status of the task. For\nexample, when creating a passkey, use clear \"create passkey\" messaging before\ntriggering the OS dialog and a success message after.\n\n\u003cbr /\u003e\n\nThe success page after creating a Passkey.\n\n\u003cbr /\u003e\n\nThis helps establish that your website and the OS are working together with\npasskeys and helps users become more familiar with the process of creating\nand using passkeys.\n\nMake helpful information about passkeys visible in the user interface by\ndefault, rather than hiding it behind clicks. For example, keep the text that\nexplains what passkeys are and where they're used in the account settings even\nafter a passkey is created.\n\n\u003cbr /\u003e\n\nPasskeys management page within Google Accounts, with the helpful information highlighted.\n\n\u003cbr /\u003e\n\nWhat information to use to create a passkey\n-------------------------------------------\n\nA passkey is made up of a username and displayname.\n\nThe username serves to identify your user when they sign in to their account.\nIt can be helpful to use an email address as a username so if a user deletes\nall their passkeys or otherwise loses access to your service, they can use the\nemail address as an account recovery method. If other ways to recover accounts,\nsuch as using a phone number, are more common for your users, then including\nthem as an option during account or passkey creation can help prevent problems\ndown the road.\n\nThe displayname is an easily readable name that can help your users find the\nright passkey in a list of credentials. It can act as a familiar name\n(like a nickname) in a way that's easy for a user to understand.\n\nIn this list Elisa Beckett is the displayname,\n[elisabeckett@gmail.com](mailto:elisabeckett@gmail.com) is the\nusername, and there's a passkey icon.\n\n\u003cbr /\u003e\n\nA passkey for Elisa's account.\n\n\u003cbr /\u003e\n\nMake passkeys a primary option in account settings\n--------------------------------------------------\n\nPresent passkeys in the same way that you present other authentication items\nsuch as username, password, or two-factor authentication within a user's account\nsettings. For example, if other sign in options within settings are labeled\nwith an H2 heading, then label \"Passkeys\" with an H2 heading, too.\n\n\u003cbr /\u003e\n\nGoogle Accounts settings present passkeys in the same way as other authentication options.\n\n\u003cbr /\u003e\n\nLearn more about passkeys content principles\n--------------------------------------------\n\nFIDO Alliance User Experience Working Group has conducted user research and\ncreated content principle guidelines. Read more in [FIDO UX content principles](https://fidoalliance.org/ux-guidelines-for-passkey-creation-and-sign-ins/#content-principles)."]]
