Multi-Organization

Multi-organization in Launchpad means one developer portal connected to more than one Apigee X organization. Developers see those Apigee orgs as workspaces by default. They are not separate portals — branding, pages, users, and navigation stay portal-wide.

Availability

Connecting more than one Apigee organization is available on Scale tier and above (multi_org).

What a workspace is

A workspace is an Apigee X organization the portal can call: API products, developer apps, teams (AppGroups), and monetization all run against that org. The portal stores the connection (org name, service account, display settings). Commercial and runtime data still live in Apigee.

Typical reasons to add more than one:

Business units — each unit has its own Apigee org and product catalog
Regions — separate Apigee orgs per geography
Environments — for example a sandbox org and a production org

Not isolated child portals

Users, branding, theme, navigation, and Page Builder pages are portal-wide. Adding a workspace does not create a second site, admin console, or login. If you need fully separate portals, provision separate Launchpad instances.

Add a workspace

You need Manage Organization and Manage Apigee Configuration. New connections are Apigee X only.

Open Manage Workspaces in the admin sidebar (/admin/apigee/organizations). The label follows your naming setting — it may say Regions or Organizations instead of Workspaces.
Click Add Workspace (the word follows your naming setting).
Enter the Apigee organization name as it appears in Google Cloud.
Paste the full GCP service account key JSON. The account needs Apigee API Admin, Apigee Analytics Viewer, and Apigee Developer Admin. See Apigee Integration.
Click Send request to test the connection, then create the workspace.

The portal uses the Apigee org name as the display name on create. You can rename and set primary/active later on the workspace detail page.

Display settings

From Manage Workspaces → Display Settings (/admin/apigee/settings):

Single Workspace — show API products from one selected org.
All Workspaces — show products from every active org. Developers can filter by workspace.
Show Workspace Label — badge the org on each product (recommended in All mode).
Group API Products by Organization — available in All mode; sections the catalog by org.

Naming

On the same Display Settings page, under Naming:

Singular / plural — what the portal calls an Apigee organization. Default is Workspace / Workspaces. Use Region / Regions if orgs are geographic.
Plans & billing area — developer-facing label for monetization (default Plans & Billing). The URL stays /monetization.

Apps and teams across workspaces

A developer or team can belong to more than one workspace. An app can attach products from several of those orgs and still share one credential (the same consumer key and secret) across them. The portal creates or updates an app unit in each Apigee org that contributes products.

On create or edit app, the product picker groups products by workspace and can mix orgs in one app.
Teams map to Apigee AppGroups. Membership and roles can differ per workspace. A team app is owned by the AppGroup, not by a member’s personal developer record.
Monetization wallets, billing type, and subscriptions are per workspace. Credit cannot move between orgs. A personal purchase does not cover a team app.

Same product name, different orgs

The same API product name can exist in two workspaces with different plans or none at all. Subscribe and attach in the org that actually sells that product.

What stays portal-wide

User accounts, roles, custom user fields, branding, theme, and navigation
Page Builder pages and Form Builder forms
SMTP, SSO, CAPTCHA, and search configuration

Assign users to the workspaces they should reach from Configuration → Users when editing a user. Sync developers into Apigee from the same Users screen so monetization and apps can key off the developer email in each org.