The input identities contains an array of service accounts to grant access to the respective control plane resource, with each service account specified using the following format: serviceAccount:***service-account-name***.
The service-account-name is formatted like an email address. For example: my-control-plane-serviceAccount@my_project_id.iam.gserviceaccount.com
You might specify multiple service accounts, for example, if you have multiple environments and wish to assign a unique service account to each one.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-06-06 UTC."],[[["`ControlPlaneAccess` is used as both the request and response body for updating and retrieving control plane access information via the `organizations.updateControlPlaneAccess` and `organizations.getControlPlaneAccess` APIs."],["Input identities for control plane access are specified as an array of service accounts, formatted as `serviceAccount:`\\*\\*\\*service-account-name\\*\\*\\*, with each name resembling an email address."],["The JSON representation of `ControlPlaneAccess` includes `name`, `synchronizerIdentities`, and `analyticsPublisherIdentities`, where the last two are arrays of service accounts."],["`synchronizerIdentities` are service accounts granted access to control plane resources for the Synchronizer, and these service accounts must have the **Apigee Synchronizer Manager** role."],["`analyticsPublisherIdentities` are service accounts that are authorized to publish analytics data to the control plane, typically for the Message Processor component."]]],[]]