다음 표에는 AppGroups 리소스를 만들고 관리하는 데 필요한 역할과 해당 개별 권한이 나와 있습니다.
IAM 역할 이름
역할 범위
필수 권한
설명
Apigee 개발자 관리자
Apigee 리소스의 개발자 관리자
AppGroup 관리:
apigee.appgroups.list
apigee.appgroups.get
apigee.appgroups.create
apigee.appgroups.update
apigee.appgroups.delete
AppGroup 앱 관리:
apigee.appgroupapps.list
apigee.appgroupapps.get
apigee.appgroupapps.create
apigee.appgroupapps.manage
apigee.appgroupapps.delete
AppGroup의 앱 키 관리:
apigee.appkeys.get
apigee.appkeys.create
apigee.appkeys.manage
apigee.appkeys.delete
AppGroup과 관련 앱 및 키를 관리할 수 있습니다. 이 역할이 있는 사용자는 개별 권한이 삭제되지 않는 한 AppGroup의 모든 측면을 관리할 수 있습니다.
AppGroup 보기 및 관리
이 섹션에서는 AppGroup을 보고 관리하는 방법을 보여줍니다. Apigee API 및 Drupal 포털을 통해 AppGroup 및 AppGroup 앱을 관리할 수 있습니다.
AppGroup 설정
AppGroups에는 다음 설정이 포함됩니다.
설정
설명
이름
필수 항목입니다. AppGroup 이름입니다. AppGroup 이름은 조직 전체에서 고유해야 합니다.
허용되는 문자는 영숫자와 특수문자(._\-$ %)입니다.
AppGroup ID
자동으로 생성되며 수정할 수 없습니다. 'OrgName@@@AppGroupName' 형식으로 생성됩니다. 예를 들어 Apigee 조직 이름이 XYZDev이고 AppGroup 이름이 ABCMarketing이면 AppGroup ID는 XYZDev@@@ABCMarketing입니다.
표시 이름
(선택사항) AppGroup의 친숙한 표시 이름입니다.
channelId
(선택사항) AppGroup을 만들고 관리하는 시스템을 식별합니다.
오프라인 매장 또는 마켓일 수 있습니다. 여러 AppGroup이 동일한 channelId를 공유할 수 있습니다.
channelUri
(선택사항) AppGroup에 대한 책임을 공유하는 사용자 그룹을 참조합니다. channelUri는 개발자 포털 또는 Apigee의 Drupal Teams 모듈과 같은 다른 시스템의 그룹이나 팀에 연결하거나 참조하는 경우가 많습니다.
Drupal 기반 포털을 사용하여 AppGroup 관리
Drupal을 위한 Apigee의 팀 모듈은 Apigee X 및 하이브리드의 AppGroups와 함께 작동하며 AppGroups 관리를 위한 기본 인터페이스입니다. Drupal 기반 포털에 대한 자세한 내용은 Drupal을 사용하여 포털 빌드를 참조하세요.
[[["이해하기 쉬움","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(UTC)"],[[["\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."]]
