（省略可）One Tap でトークンをリクエストする: 選択したアドオンは、アクティブな Google セッションがある場合、Google One Tap を使用して、ログイン情報とユーザーが承認したスコープを含むトークンをリクエストします。
（省略可）Google が ID トークンを返す: ID トークンにはユーザー ID 情報が含まれています。
Google Workspace Marketplace のアドオン
Google Workspace アドオンは、Gmail、Google ドキュメント、Google スプレッドシートなどの Google Workspace アプリケーションと統合されるカスタマイズされたアプリです。これにより、デベロッパーは Google Workspace に直接統合されるカスタマイズされたユーザー インターフェースを作成できます。アドオンを使用すると、コンテキストの切り替えを減らして効率的に作業できます。
Google Workspace Marketplace では、ユーザーと管理者が Google Workspace と統合されているサードパーティのエンタープライズ アプリを見つけてインストールできます。Marketplace は、公開された Google Workspace アドオンを管理する中心的な場所でもあります。ユーザーは、公開されたアドオンをインストールおよびアンインストールできます。管理者は、ユーザーがインストールできるアドオンを制限できます。
[null,null,["最終更新日 2025-08-29 UTC。"],[],[],null,["# Meet add-on concepts\n\nGoogle Meet add-ons are used to build experiences directly into Google Meet.\nTo create add-ons, you must understand how a\nGoogle Workspace add-on is developed and eventually published in\nthe Google Workspace Marketplace.\n\nArchitecture\n------------\n\nThe following sequence diagram shows the architecture of how a\nGoogle Meet add-on uses Google Workspace resources.\n**Figure 1.** Architecture of how a Google Meet add-on uses Google Workspace resources.\n\nUsing a Google Meet add-on in a meeting works like this:\n\n1. **Load add-on panel** : The user clicks the meeting tools button in Meet to load the list of [installed add-ons](/workspace/meet/add-ons/guides/overview#installed-add-ons) into the add-on panel.\n2. **Select add-on**: A user selects an add-on in the add-on panel.\n3. **Load add-on iframe**: Meet loads the add-on side panel iframe URL that the developer specified in the manifest.\n4. **Create AddonSession** : The add-on creates an [`AddonSession`](/workspace/meet/add-ons/reference/websdk/addon_sdk.addonsession). This indicates to Meet that the add-on is loaded and is ready for use.\n5. **Add-on initialized**: The add-on is ready for use.\n6. **(Optional) Request token with One Tap** : The selected add-on uses [Google One Tap](/identity/gsi/web/guides/display-google-one-tap) to request a token with the sign-in information and user-approved scopes if there's an active Google session.\n7. **(Optional) Google returns ID token**: The ID token contains the user identity information.\n\nGoogle Workspace add-ons in the Marketplace\n-------------------------------------------\n\nGoogle Workspace add-ons are customized apps that integrate with Google Workspace\napplications, such as Gmail, Google Docs, and Google Sheets. They\nallow developers to create customized user interfaces that are directly\nintegrated into Google Workspace. Add-ons help users work more\nefficiently with less context switching.\n\nThe [Google Workspace Marketplace](https://workspace.google.com/marketplace/)\noffers users and administrators a way to find and install third-party enterprise\napps that are integrated with Google Workspace. The\nMarketplace is also the central place for managing\npublished Google Workspace add-ons. Users can install and uninstall published\nadd-ons. Admins can restrict the add-ons users can\ninstall.\n\nTypes of add-ons\n----------------\n\nIn general, there are two types of add-ons you can build: [Google Workspace add-ons](/apps-script/add-ons/concepts/types#google-workspace-add-ons)\nand\n[Editor add-ons](/apps-script/add-ons/concepts/types#editor-add-ons).\n\nFor the Meet add-ons SDK, you must build your add-ons\nusing Google Workspace add-ons.\n\nWith a Google Workspace add-on, you can extend multiple Google Workspace\napps such as Gmail, Google Calendar, and Google Drive. You specify\nwhich app the add-on is targeting, along with other\ndetails, in the [add-on manifest\nfile](/apps-script/add-ons/concepts/workspace-manifests). For the\nMeet add-ons SDK, you must declare a `meet` object within the `addOns`\nsection of the manifest file. For more information, see [Create a\ndeployment](/workspace/meet/add-ons/guides/deploy-add-on#create-deployment).\n\nA Google Workspace add-on can be developed in two different ways: either in\nGoogle Apps Script, or as a self-hosted add-on using\nyour preferred tech stack. Each of these add-ons contains a\nmanifest, which is made up of different sections. The Meet\nsection of the manifest contains information specific to how your\nadd-on is loaded from Google Meet and is unrelated to\nwhether the rest of your add-on is self-hosted or uses\nApps Script. Add-ons for Meet are\nloaded in an iframe and must reference web pages rather than [Card-based\ninterfaces](/apps-script/add-ons/concepts/card-interfaces).\n\nFor example, a manifest for a Google Workspace add-on might have a section for\nGmail that uses\n[`ComposeTrigger`](/apps-script/manifest/gmail-addons#composetrigger) and\n[`ContextualTrigger`](/apps-script/manifest/gmail-addons#contextualtrigger)\nobjects to return card interfaces, and a section for Meet that\nuses web, iOS, and Android objects to point to your web page and mobile app.\n**Figure 2.** An example manifest with Meet and Gmail sections.\n\nPublish an add-on\n-----------------\n\nWhen you publish your Google Workspace add-on, you make it available for\nothers to find, install, and use.\n\nFor more information, see [Publish your\nMeet add-on](/workspace/meet/add-ons/guides/publish).\n\nRelated topics\n--------------\n\n- [Deploy a Meet add-on](/workspace/meet/add-ons/guides/deploy-add-on)\n- [Best practices](/workspace/meet/add-ons/guides/best-practices)\n- [Add-ons types](/apps-script/add-ons/concepts/types)\n- [Gmail manifest resource](/apps-script/manifest/gmail-addons)"]]
をクリックして、インストール済みのアドオンのリストをアドオン パネルに読み込みます。