Accounts/Developers
What Is It For?
- Centrally manages registered person accounts (developers) on the portal
- Links an account to an organization and assigns Owner / Developer / Viewer
- Shows the account’s access surface via Accessible Apps, credentials, and products
- Lists multi-org memberships (role + status + joined) on one view
- Exports the account inventory to Excel
Who Uses It?
- Portal administrators: To open accounts, change status, and assign org roles
- Portal Business / Manager roles: For account operations in their scope
- Support: To verify which orgs and apps a user can reach
Apps belong to an organization, not to a person. An account reaches apps through ACTIVE memberships. Org operations: Portal Organizations. Consumer invite/member management: Portal Membership and Invitation.
Access
- Portal → Accounts/Developers (
/admin/portal-account) - Create:
/new· View:/:id/view· Edit:/:id/edit - Authorities: Admin, Portal Manager, Portal Business
- Scope: active portal (
portalId)
List
Filters
| Filter | Description |
|---|---|
| Search by Email | |
| Search by Full name | Full name |
| Organization | Multi-select orgs |
| Search by Status | Approved / Disabled |
Columns
| Column | Description |
|---|---|
| Link to view; description tooltip | |
| Full Name | |
| Organization | Primary org badge |
| Accessible Apps | App count from list-stats |
| Role | Highest ACTIVE membership role (Owner > Developer > Viewer) |
| Enabled | Approved = on, Disabled = off |
| Created Date |
Actions
- Export to Excel — export may still include a legacy “Organization Manager” Yes/No column; the UI uses the Role model
- Create
- Row ⋮: View · Edit · Remove
Create / Edit
The legacy Organization Manager boolean is removed from the Manager form; use Role instead.
| Field | Required | Notes |
|---|---|---|
| Enabled | — | APPROVED / DISABLED |
| Yes | Unique; existence check | |
| Full Name | Yes | Max 50 |
| Password | Create: yes; Edit: optional | Min 8 with upper+lower; blank on edit keeps current |
| Phone | No | |
| Organization | No | Clearable; primary org |
| Role | Default Developer | Owner / Developer / Viewer |
| Description | No | Max 1000 |
Save: Save and Deploy → view.
With an organization selected, an ACTIVE membership is upserted on the primary org. The last ACTIVE Owner cannot be downgraded.
Role capabilities
| Role | Summary |
|---|---|
| Owner | Invite/remove members, change roles, org settings + Developer capabilities |
| Developer | Create/edit apps, credentials (including secrets), subscriptions |
| Viewer | Read-only; never sees client secrets; no writes |
Allow Organization Administrator to Manage their own Accounts in Portal Settings is a separate feature flag, not the same as this page’s Role model.
View
Header
Name / email, Enabled/Disabled, Role badge, Organization badge; Edit / Delete.
Stat cards
Accessible Apps · Credentials · API Products (/{id}/detail).
Information
- Details: Email, Full Name, Phone, Organization, Enabled, Role, Created Date, Description
- Linked Resources: counts; optional Direct Credentials (no app) badges
Organization Memberships
| Column | Description |
|---|---|
| Organization | Link to org overview |
| Role | Owner / Developer / Viewer |
| Status | Pending / Active |
| Joined At | or Invited time |
Accessible Applications
Apps of orgs with ACTIVE membership: name, description, created, referenceId, credential and product badges.
Developer Portal profile
Consumer Profile is self-service (name, phone, description, change password). Email is not freely changed. Org/role management is via Manager or Portal Membership and Invitation. Consumer UI may still show a legacy “Organization Manager” tag; Manager uses Role.