[[["容易理解","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-04 (世界標準時間)。"],[[["\u003cp\u003eThis content covers Apigee and Apigee hybrid, detailing how global users are defined and assigned roles within organizations to manage APIs.\u003c/p\u003e\n"],["\u003cp\u003eGlobal users in Apigee are defined by their first name, last name, email address, and password, which serve as their login credentials for the Apigee UI and API requests.\u003c/p\u003e\n"],["\u003cp\u003eGlobal users must be assigned a role within an organization to perform actions, with roles specifying CRUD-based permissions (create, read, update, delete), and there are predefined roles like Organization Administrator and Read-only Organization Administrator.\u003c/p\u003e\n"],["\u003cp\u003eApigee organizations differentiate between organization users, who are global users managing APIs, and developers, who are customers building apps that consume those APIs and typically do not have global user accounts.\u003c/p\u003e\n"],["\u003cp\u003eApigee offers both pre-defined roles and the possibility to create custom roles with custom permissions within an organization.\u003c/p\u003e\n"]]],[],null,["# About global users\n\n*This page\napplies to **Apigee** and **Apigee hybrid**.*\n\n\n*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*\n\nAll Apigee users are called global users because they are created outside of any Apigee\norganization. Once created, a global user can then be assigned to one or more organizations:\n\n| **Note:** Your ability to add new users may depend on your account type. For more information, see [Apigee Pricing](https://cloud.google.com/apigee/pricing).\n\nWhen you assign a user to an organization, you must specify the user's role in that\norganization. The user's role determines the actions that the user is allowed to perform in that\norganization. For example, some users are allowed to create APIs, while others can view APIs but\ncannot modify them.\n\nA global user can also be assigned to the role of Apigee organization administrator or Apigee\nread-only administrator. An organization administrator performs all administrative tasks required\nto maintain Apigee, including creating new global users.\n\nWhat information defines a user?\n--------------------------------\n\nAn Apigee user is defined by the following:\n\n- First name\n- Last name\n- Email address\n- Password\n\nThe email address and password function as the user's credentials when logging in to the\nApigee UI and when making requests through the Apigee API.\n\nWhat are roles?\n---------------\n\nOn its own, a global user cannot do anything in Apigee. For a global user to be able to\nfunction, the user must be assigned to an organization role.\n\nRoles are essentially CRUD-based permission sets. CRUD means \"create, read, update, delete\".\nFor example, a user may be given a role in an organization that permits read, or \"get\", access to\ndetails about a protected entity, but not write permission to update or delete it. The\norganization administrator is the highest-level role in the organization, and can perform any\nCRUD operation on any entity in the organization.\n\n### About predefined organization roles\n\nAll Apigee organizations are created with the following roles with a\n[predefined set of\npermissions](/apigee/docs/api-platform/system-administration/apigee-roles):\n\n- Organization Administrator\n- Read-only Organization Administrator\n- Operations Administrator\n- Business User\n- User\n\nYou can also create custom roles, with custom permissions, in your organization.\n\n### About the administrator roles\n\nApigee supports the following administrator roles:\n\n- Read-only administrator role\n- Organization administrator role\n\nApigee organization administrators can:\n\n- Create organizations and environments\n- Add additional components to an Apigee installation\n- Configure TLS/SSL\n- Create additional administrators\n- Perform all other Apigee administrative tasks\n\n| **Note:** While it is not required, you can assign a read-only administrator to an organization, typically as an organization administrator. Unless assigned to an organization, the read-only administrator cannot even log in to the [Apigee UI](https://apigee.google.com).\n\nFor details about administrator permissions, see\n[Apigee roles](/apigee/docs/api-platform/system-administration/apigee-roles).\n\nAssigning global users to an organization\n-----------------------------------------\n\nThe following image shows the structure of an Apigee organization:\n\nAn organization contains two distinct types of users:\n\n- **Organization users** : Create, modify, and deploy APIs, create and manage entities such as API products, developers, and developer apps, generate analytics reports, and perform other administrative tasks. **Organization users are Apigee global users** assigned to an organization with a specific role.\n- **Developers** : Build the apps that make requests to your APIs. **A\n developer is not an Apigee global user.** Think of developers as your API customers. To access the APIs in your organization, a developer must register with the organization and then request an *API key*. A developer can be registered with multiple organizations to consume APIs from different organizations.\n\nThe big difference between users and developers in an organization is that **users are\nApigee global users that build and maintain APIs** , while **developers are customers\nthat build apps that consume those APIs**. Developers typically do not have global user\naccounts on Apigee, and cannot log in to the Apigee UI. The exception to this is an\norganization user who creates their own developer and developer apps for testing purposes.\n| **Note:** There is actually one more type of user that you have to be concerned with - the **app user** . This is the person who uses the apps created by **developers**. However, app users are not defined or controlled by Apigee. It is up to you to decide how to implement authentication and authorization for app users. For example, an app might require the app user to log in. How you process that log in is up to you, possibly by accessing a backend LDAP service or other type of authentication mechanism.\n\nFor more on developers, see\n[Publishing overview](/apigee/docs/api-platform/publish/publishing-overview)."]]
