Portal Membership and Invitation
What Is It For?
- Organizes API consumers inside an organization as a team on the portal
- Provides controlled onboarding via invitations and join requests
- Separates who can manage members, who can run app/credential work, and who can see secrets
- Prevents removing the last Owner so organization management is never orphaned
Who Uses It?
- Organization Owners: To invite members, assign roles, manage invitations, and approve join requests
- Developer members: To run application, subscription, and credential work
- Viewer members: For read-only monitoring
Access
- Developer Portal user menu → Organization (page: Organization / Organization Members)
- Accept invitation:
/organization/accept-invitation?token=… - For Manager-side organization operations (suspend, merge, revoke) → Portal Organizations
Roles and Permissions
| Role | Member management | App / subscription / credential write | Client secret |
|---|---|---|---|
| Owner | Yes (invite, role, remove, join request) | Yes | Visible |
| Developer | No | Yes | Visible |
| Viewer | No | No (read-only) | Not visible |
Rules:
- The last active Owner cannot be demoted or removed
- You cannot change your own role on your row
- Owner only: Invite / Resend / Cancel / Remove / Join Requests
Member statuses: Pending (Invited date) · Active (Joined Date)
Invite a Member
An Owner opens Invite Member.
E-mail (required) and Role (often default Viewer) → Send Invitation. The member appears as Pending.
The recipient opens accept-invitation?token=…. No account → Register (with invite email/org); no session → accept after login; logged in → immediate accept.
For pending invites use Resend invitation or Cancel invitation.
Join Requests
Users who self-signup / request to join from a verified email domain land in the Owner’s Join Requests queue. The Owner Approves (picking a role; UI default is often Developer) or Rejects.
Common errors: duplicate invitation, last-owner constraint, only owners manage members, invitation email mismatch, already a member.
Usage Scenarios
- An Owner invites Developers for a new integrator firm and gives Viewers monitoring-only access
- A self-signup from the company domain is approved via Join Request into the right role
- An Owner removes a former employee so secret and write access stop