This page describes how to use Apigee Spaces to implement granular Identity and Access Management control over your Apigee organization resources.
Apigee Spaces enables identity-based isolation and grouping of API resources within an Apigee organization. With Apigee Spaces, you can
have granular IAM control over access to your API proxies, shared flows and API products.
You can create multiple Spaces in the same organization for different teams, development projects,
or environments and set the IAM controls for each Space. Any API resources created under a Space will inherit
the IAM policies applied to that Space.
When to use Apigee Spaces
Managing IAM permissions for multiple teams working within a single Apigee
organization can be complex. Using Spaces can simplify IAM administration with granular controls and simplified permissions for accessing organization resources.
With Spaces, you can host multiple teams in an Apigee organization where:
Each team maintains their own independent set of API proxies, shared flows, and API products.
Team members have read/write access to the set of API proxies, shared flows, and API products.
Members of another team can be granted specific access (read, or read/write, or trace/debug access) to one or more
of the API proxies, shared flows, or API products.
Multiple teams can access a common set of API proxies, shared flows, and API products with fine-grained permissions.
There are several benefits to using Apigee Spaces, including:
Improved security: Using Spaces can improve security by
allowing you to control access to resources at a granular level. You can grant different users and groups
access to different Spaces, and control which resources are available in each Spaces.
This helps isolate and protect access to sensitive data or resources.
Simplified management: Spaces can help you simplify your management tasks
by providing a way to logically group your resources. You can manage all of the resources in a Space together,
and you can easily see which users and groups have access to each resource.
Increased flexibility: Spaces give you flexibility in how you manage your Apigee resources.
You can create as many Spaces as you need and you can move resources between spaces as needed, letting you adapt to
changing needs.
Spaces provide the ability to introduce resource isolation at a team level, providing a clear separation of resources
associated with different teams operating within the same Apigee organization.
In addition, IAM policies can be applied at the Space level, eliminating the need to manage permissions individually for every API proxy, shared flow, and API product.
Limitations
The following limitations apply to Apigee Spaces:
To use Apigee Spaces, Apigee hybrid customers must use hybrid version 1.13 or higher. For information on upgrading
to version 1.13, see Upgrade your Apigee hybrid organization.
[[["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-08-26 UTC."],[[["\u003cp\u003eApigee Spaces allows for identity-based isolation and grouping of API resources within an Apigee organization, enabling granular Identity and Access Management (IAM) control over API proxies, shared flows, and API products.\u003c/p\u003e\n"],["\u003cp\u003eSpaces simplify IAM administration by allowing multiple teams to operate independently within a single Apigee organization, each with its own set of API resources and specific access permissions.\u003c/p\u003e\n"],["\u003cp\u003eApigee Spaces provides improved security, simplified management, and increased flexibility by allowing granular control over resources, logical grouping, and adaptability to changing needs.\u003c/p\u003e\n"],["\u003cp\u003eA new set of permissions, such as \u003ccode\u003eapigee.spaces.create\u003c/code\u003e, \u003ccode\u003eapigee.spaces.update\u003c/code\u003e, and \u003ccode\u003eapigee.spaces.delete\u003c/code\u003e, are introduced to manage Spaces, and the custom role \u003ccode\u003eApigeeSpaceUser\u003c/code\u003e is required for viewing Space resources in the Google Cloud console.\u003c/p\u003e\n"],["\u003cp\u003eApigee Spaces has limitations such as not being supported in the Classic Apigee UI, certain management actions for spaces needing to be done via the API, a limit of 20 Spaces per organization, and a 10 QPS limit for certain \u003ccode\u003elist\u003c/code\u003e operations.\u003c/p\u003e\n"]]],[],null,["# Apigee Spaces overview\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\nThis page describes how to use Apigee Spaces to implement granular [Identity and Access Management](/iam/docs) control over your Apigee organization resources.\n\nApigee Spaces enables identity-based isolation and grouping of API resources within an Apigee organization. With Apigee Spaces, you can\nhave granular IAM control over access to your API proxies, shared flows and API products.\n\nYou can create multiple Spaces in the same organization for different teams, development projects,\nor environments and set the IAM controls for each Space. Any API resources created under a Space will inherit\nthe IAM policies applied to that Space.\n\nWhen to use Apigee Spaces\n-------------------------\n\nManaging IAM permissions for multiple teams working within a single Apigee\norganization can be complex. Using Spaces can simplify IAM administration with granular controls and simplified permissions for accessing organization resources.\n\nWith Spaces, you can host multiple teams in an Apigee organization where:\n\n- Each team maintains their own independent set of API proxies, shared flows, and API products.\n- Team members have read/write access to the set of API proxies, shared flows, and API products.\n- Members of *another* team can be granted specific access (read, or read/write, or trace/debug access) to one or more of the API proxies, shared flows, or API products.\n- Multiple teams can access a common set of API proxies, shared flows, and API products with fine-grained permissions.\n\nApigee Spaces can be used with Apigee [Subscription](/apigee/docs/api-platform/reference/subscription-entitlements)\nand [Pay-as-you-go](/apigee/docs/api-platform/reference/pay-as-you-go-updated-overview) organizations, including\n[Apigee hybrid-enabled](/apigee/docs/hybrid/v1.12/what-is-hybrid) organizations. Spaces can be used with Apigee organizations that have\n[data residency](/apigee/docs/api-platform/get-started/drz-concepts#summary) enabled.\nApigee hybrid organizations must use hybrid version 1.13 or higher. For information on upgrading\nto version 1.13, see [Upgrade your Apigee hybrid organization](/apigee/docs/hybrid/v1.13/upgrade).\n\nBenefits of Apigee Spaces\n-------------------------\n\nThere are several benefits to using Apigee Spaces, including:\n\n- **Improved security**: Using Spaces can improve security by allowing you to control access to resources at a granular level. You can grant different users and groups access to different Spaces, and control which resources are available in each Spaces. This helps isolate and protect access to sensitive data or resources.\n- **Simplified management**: Spaces can help you simplify your management tasks by providing a way to logically group your resources. You can manage all of the resources in a Space together, and you can easily see which users and groups have access to each resource.\n- **Increased flexibility**: Spaces give you flexibility in how you manage your Apigee resources. You can create as many Spaces as you need and you can move resources between spaces as needed, letting you adapt to changing needs.\n\nSpaces provide the ability to introduce resource isolation at a team level, providing a clear separation of resources\nassociated with different teams operating within the same Apigee organization.\nIn addition, IAM policies can be applied at the Space level, eliminating the need to manage permissions individually for every API proxy, shared flow, and API product.\n\nLimitations\n-----------\n\nThe following limitations apply to Apigee Spaces:\n\n- To use Apigee Spaces, Apigee hybrid customers must use hybrid version 1.13 or higher. For information on upgrading to version 1.13, see [Upgrade your Apigee hybrid organization](/apigee/docs/hybrid/v1.13/upgrade).\n- Apigee Spaces is not supported in the [Classic Apigee UI](https://apigee.google.com/edge). To view Spaces and manage Space resources, use the [Apigee UI in Cloud console](https://console.cloud.google.com/apigee) or the API.\n- The Apigee UI in Google Cloud console can't be used to perform the following actions:\n - Create, get, update, delete, or list Spaces\n - Manage IAM policies for Spaces\n\n These actions must be performed using the API.\n- The following limits apply when using Apigee Spaces:\n - There is a maximum of 20 Spaces per Apigee organization.\n - There is a limit of 10 queries per second (QPS) for `list` operations for API proxy, API product, and shared flow endpoints.\n\n For more information about Apigee limits, see [Limits](/apigee/docs/api-platform/reference/limits#spaces).\n\nWhat's next\n-----------\n\n- Learn how to [Create and manage Apigee Spaces](/apigee/docs/api-platform/system-administration/spaces/create-spaces).\n- Discover how to [Manage API resources in Apigee Spaces](/apigee/docs/api-platform/system-administration/spaces/manage-space-resources)."]]
