Customer Portal
Customer Portal is the end-customer self-service SPA for organizations that hold licenses — not Vendor Console and not Reseller Portal.
Who it is for
| Role | Typical use |
|---|---|
Organization administrator (PortalRole = OrgAdministrator) | Org licenses, devices, membership role view/change within the org |
Organization member (OrgMember) | Read org licenses and devices; no membership role mutation |
Portal access is membership-scoped (active membership in a customer organization). Vendor Console RBAC codes (customers.*, …) are a different plane.
What you can do (product narrative)
| Surface | Behavior |
|---|---|
| Licenses | List licenses assigned to the caller’s organization(s) |
| Devices | List devices derived from active device↔license bindings for those org licenses (unbound / unassigned stay invisible — honest empty) |
| Organization / memberships | OrgAdmins see memberships and can patch portal role only; invite/create/remove membership remains vendor-managed |
Seat allocate/release, device register/activate from the portal, and vendor catalog editing are out of this surface.
Naming boundaries
- Customer Portal ≠ Vendor Console (product catalog, policies, key issue).
- Customer Portal ≠ Reseller Portal (partner delegation).
- SaaS PlatformPlan checkout ≠ license packaging — see Checkout and payments.
Related
- License Keys · Products · Entitlements
- Choose your path · Core Concepts
- Integrator APIs (Management portal routes as published): API Reference
Next steps
- Getting Started
- Buyer SaaS / commerce: Checkout and payments
- Partners: Reseller Portal