Portal Organizations
What Is It For?
- Centrally manages consumer organizations in the portal context
- Shows members, subscriptions, applications, and limits together on the organization page
- Handles risky or duplicate organizations safely via deactivate, merge, and consumer revoke
- Uses verified email domains so signups become join requests to the right organization
- Reduces incorrect manual edits on LDAP-sourced organizations with read-only fields
Who Uses It?
- Portal administrators: To manage the consumer organization inventory and lifecycle
- Support / operations: To see a troubled organization's subscriptions and apps in one place
- Identity / security teams: To apply critical actions such as deactivate, revoke, and merge
Access and Permissions
- In the admin panel follow Portal → Consumers → Organizations
- The same list and organization page also open under Identity → Consumer → Organizations
- From Portal you work in the active portal context; from Identity you work in the identity-management context. The tabs of the organization page follow the menu that opened it
List
From the list you search organizations and open the organization page.
Filters: Project, Search by name, accounts, apps, consumer search. Columns include name, source, parent organization, account/app/consumer/sub-org counts, last synchronized, and status (Pending approval, Rejected, or Merged badges when it applies).
Row menu (⋮): Open · Duplicate · Delete · Move to Global — for a synchronized (LDAP-sourced) row, Duplicate and Delete are not offered.
Organization Page
The header shows the organization name, an Active / Deactivated indicator (or a Pending approval / Rejected / Merged badge), and a Synced badge for organizations that come from a directory. The How to Read button explains each tab.
Tabs
| Tab | Content |
|---|---|
| Overview | Code, names, parent organization, verified e-mail domains, source type, member since, status, and notification mails. Configure on a card opens its form; Save first shows what changes and where it applies, then saves and deploys. |
| Members | Portal accounts of the organization with their roles. Portal context only. |
| Consumers/Applications | The API identities of the organization. Identity context only. |
| Apps & Subscriptions | Subscriptions with plan and status (Active, Waiting for approval, Rejected, Disabled, Unsubscribed), and the apps with their registered products and consumer metadata. Secrets are never shown. Portal context only. |
| Limits | Limit plans of the organization: the organization total, or a counter for each API client, consumer, or sub-organization under it. Identity context only. |
| Metadata | Key-value pairs added to the tokens of its consumers; a consumer's own key wins. |
| Source | Manual, or bound to an identity directory. A synchronized organization takes its code, names, and parent from the source. |
Adding a member on the Members tab: since a consumer organization is not tied to a single portal, the "add member" picker lists accounts from every portal that can reach the organization, not only the active one; accounts already a member of the organization are excluded automatically. Each row also shows the account's portal name so people with the same display name in different portals stay tellable apart.
Critical operations
Open the ⋯ menu at the top of the page.
| Action | Effect |
|---|---|
| Status > Deactivate / Activate | Deactivate rejects the requests of every consumer, application, and API client of the organization and of its sub-organizations right away. Nothing is deleted. Activate lets them work again, unless an organization above it is deactivated; a consumer disabled on its own stays disabled. Both show the same dialog first. |
| Organization > Revoke consumers | Permanently revokes the consumers filed directly under the organization and every consumer of its apps, including the ones disabled before. It cannot be undone, a later Activate does not reopen them, and the apps need new consumers. Tokens already issued to the API clients under the organization and its sub-organizations stop working as well. Revoking does not lift a deactivation; the only way to lift it is an explicit Activate. |
| Organization > Merge into… | Merges into another organization; members, apps, and subscriptions move; quota counters continue; irreversible |
| Transfer | Export and Move to Global |
| History > Audit and Rollback | Shows the change history and restores an earlier version |
Verified e-mail domains: Portal signups from these domains do not create a new organization — they become a join request. Member approval is done by an Owner on the Developer Portal → Portal Membership and Invitation.
Client secrets are never shown on this screen. Revoke and Merge are irreversible; confirm impact first. Delete can affect account access / apps / consumers.
Roles and Statuses
| Role | Meaning (portal membership) |
|---|---|
| Owner | Member management + write access |
| Developer | App / subscription / consumer write |
| Viewer | Read-only; does not see client secrets |
Organization status: Active · Pending approval · Rejected · Merged
Usage Scenarios
- Deactivate a consumer organization whose contract has ended
- Merge two duplicate organizations into one inventory
- Check the subscriptions and apps of an organization that opened a support ticket
- On LDAP-sourced orgs, treat code/name as read-only and use operational actions only