Platform Administration
Summary
Platform exposes authenticated administrative surfaces for tenant control-plane data, provisioning, commercial records, entitlements, operations, and reporting. This page describes capability groups, not sensitive procedures.
Audience
- Platform and customer administrators
- Implementation, support, architecture, and security teams
Purpose
Use this inventory to assign ownership and review supported administration without relying on undocumented endpoints or bypass mechanisms.
Reference Content
| Capability | Confirmed administrative scope | Status |
|---|---|---|
| Tenants and clients | List, retrieve, create, update, activate, deactivate, suspend, restore, and soft-delete tenant/control-plane records | Implemented |
| Company and branding | Retrieve and update organization profile and tenant presentation metadata | Implemented |
| Provisioning | Validate, provision, inspect status, retry, and resume; manage onboarding metadata | Implemented; some handoffs are Foundation |
| Plans and subscriptions | Create and version plans; assign and transition subscriptions; inspect usage and commercial summaries | Implemented records and endpoints; policy Requires confirmation |
| Licensing | Maintain license records, evaluate status and capacity, report usage, and apply administrative suspension/reactivation | Implemented |
| Features and entitlements | Maintain catalog entries, plan packaging, tenant overrides, limits, and effective-access resolution | Implemented |
| Configuration | Maintain tenant settings, service configuration records, tenant overrides, and secret references | Implemented foundation |
| Platform jobs | Inspect durable work and status | Implemented foundation |
| Usage and commercial records | Record usage and manage charge, invoice, payment, and summary records | Implemented foundation; business policy Requires confirmation |
| Service monitoring | Register/probe services, record heartbeats and health history, and present operational summaries | Implemented |
| Analytics | Read platform dashboards, activity, provisioning, entitlement, usage, job, service, and export-oriented views | Implemented |
Architecture
All platform administration is expected to pass through authenticated service boundaries. Whether a user may administer the platform or a specific tenant remains an authorization decision; possession of tenant identifiers alone is not authority.
Business concepts
Administration changes should be tenant-scoped where applicable, audited, and separated from Identity credential management. Client and tenant records coexist, so an operator should confirm linkage before changing client-owned branding, commercial, or entitlement records.
Technical implementation
Endpoint groups are registered by the Platform service and use persistence-backed application services. Compatibility surfaces remain Transitional. Source also includes development-oriented and internally restricted operations; these are intentionally excluded from public procedures.
Source References
microservices/src/platform-service/Program.csmicroservices/src/platform-service/Api/PlatformAdminEndpoints.csmicroservices/src/platform-service/Api/PlatformClientEndpoints.csmicroservices/src/platform-service/Api/PlatformCommercialEndpoints.csmicroservices/src/platform-service/Api/PlatformLicensingEndpoints.csmicroservices/src/platform-service/Api/PlatformEntitlementEndpoints.csmicroservices/src/platform-service/Api/PlatformAnalyticsEndpoints.csmicroservices/src/platform-service/Api/PlatformServicesEndpoints.cs
Related Articles
See Also
Keywords
- Platform administration
- Control plane
- Administrative capabilities
Revision Information
- Status: Draft
- Last reviewed: 2026-07-14
- Review cycle: Quarterly