[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-05 (世界標準時間)。"],[[["\u003cp\u003eAppGroups provide a way to organize and manage app ownership by associating multiple apps with a group of responsible individuals.\u003c/p\u003e\n"],["\u003cp\u003eAppGroups allow for flexible tracking of app ownership, such as by partner, business unit, or other custom corporate entities, and can have a multi-level structure.\u003c/p\u003e\n"],["\u003cp\u003eIAM roles and permissions control the management of AppGroups, with the Apigee Developer Admin role providing the ability to manage all aspects of AppGroups and their associated apps and keys.\u003c/p\u003e\n"],["\u003cp\u003eAppGroups can be managed through Apigee APIs and Drupal-based portals, with the Apigee Team module for Drupal being the primary management interface, and at this time, AppGroups do not support Monetization.\u003c/p\u003e\n"],["\u003cp\u003eApp ownership can also be tracked, although less comprehensively, through developer-app association.\u003c/p\u003e\n"]]],[],null,["# Organizing client app ownership\n\nThis page describes tools and strategies used to organize client app ownership.\n\nUsing AppGroups to organize app ownership\n-----------------------------------------\n\nThis section provides an overview of AppGroups and how to manage them.\n\n### What are AppGroups?\n\nAn AppGroup represents a relationship between one or more apps that are managed by the same\nset of people.\n\nAn AppGroup is associated with another system that is responsible for managing the roster of\npeople who share responsibility for these apps, such as a portal. Both Apigee apps and\nApigee developers are associated to the AppGroup.\n| **Important:** AppGroups themselves do not control permission to access an API. API access is managed at the credential level for each app. Permissions and API key management are handled separately from AppGroup membership.\n\nAppGroups provide:\n\n- A method of organizing and viewing app ownership and associations.\n- The ability to create a roster for a portal or API storefront of workers who are responsible for an app. For example, you might set up different AppGroups for billing purposes.\n- Flexibility for tracking app ownership by partner, business unit, product line, division, or other corporate entities.\n- A potentially multi-level structure for tracking how apps are logically related to app owners and developers.\n\n### IAM roles and permissions\n\nTo control permissions required for AppGroup management, you can view and grant roles using the permissions panel on the **IAM \\& Admin \\\u003e IAM**\npage in your Google Cloud project.\n\n[Go to IAM \\& Admin](https://console.cloud.google.com/iam-admin/serviceaccounts)\n| **Note:** If a role is assigned to a user then all the associated permissions of the role are automatically assigned to the user.\n\nThe following table lists the role and the corresponding individual permissions required to\ncreate and manage AppGroups resources.\n\n### Viewing and managing AppGroups\n\nThis section shows how to view and manage AppGroups. You can manage\nAppGroups and AppGroup apps\n[via the Apigee APIs](#managing-appgroups-using-the-apigee-apis) and\n[Drupal portals](#managing-appgroups-using-drupal-based-portals).\n| **Note:** AppGroup management in Apigee UI in Cloud console will be considered in a future release.\n\n#### AppGroup settings\n\nAppGroups include these settings:\n\n#### Managing AppGroups using Drupal-based portals\n\nApigee's Team module for Drupal works with AppGroups in Apigee X and hybrid and is the primary interface for managing AppGroups. For information on Drupal-based portals, see [Building your Portal using Drupal](https://cloud.google.com/apigee/docs/api-platform/publish/drupal/open-source-drupal).\n\n\u003cbr /\u003e\n\n#### Managing AppGroups using the Apigee APIs\n\nUse these APIs to manage AppGroups in your orgs:\n\n### AppGroups limitations and known issues\n\nIn Apigee hybrid, AppGroups are available in versions 1.10.0 and later.\n\nAt this time AppGroups do not support [Monetization](/apigee/docs/api-platform/monetization/overview).\n\n### Migrating from Apigee Edge for Drupal users\n\nMigrating a company-developer and its role involves creating an AppGroup representing the\ncompany, and adding the company-developer and its role(s) as custom Attributes of the AppGroup.\nThe expected syntax to store this is: \n\n```text\n[{\n \"developer\":\"\u003cdeveloper email\u003e\",\n \"roles\":[\n \"\u003crole(s)\u003e\"\n ]\n },\n ...\n]\n```\n\nUsing developer-app association to organize app ownership\n---------------------------------------------------------\n\nA less comprehensive and flexible method of tracking app ownership than AppGroups is tracking\napps by developer association.\n\nFor information on managing developer-app associations, see\n[Registering app developers](/apigee/docs/api-platform/publish/adding-developers-your-api-product)\nfor information on registering developers and associated apps."]]
