[null,null,["上次更新時間：2025-08-29 (世界標準時間)。"],[],[],null,["# Manage sign-in methods for your add-on\n\nThis page describes the best practices developers should observe when using\nsign-in methods for Google Meet add-ons. It lets users create an account or\nsign in to a website by eliminating the long registration or authentication\nprocess.\n\nHere are some important tips developers can use when implementing sign-in\nmethods for Meet add-ons:\n\n- Google [One Tap](/identity/gsi/web/guides/display-google-one-tap) sign-in is\n strongly recommended. For more information, see [Understand the One Tap user\n experience](/identity/gsi/web/guides/features).\n\n- Per the One Tap FAQ, apps should also [display a fallback Google sign-in\n button](/identity/gsi/web/guides/display-button). To know more, see [Sign in\n with Google button UX](/identity/gsi/web/guides/personalized-button).\n\n- If your app must authenticate the user through other mechanisms, or\n re-authenticate the user during Google sign-in or One Tap to link with an\n existing account, do that in a dialog window. Don't display user-password\n sign-in forms directly in iframes.\n\n| **Note:** Federated Credential Manager (FedCM) for Google Sign-in is unavailable for Meet add-ons.\n\n- Always use the default rendering of the One Tap prompt for Meet add-ons.\n\nRelated topics\n--------------\n\n- [Publish your Meet add-on](/workspace/meet/add-ons/guides/publish)"]]
