Tenant Concepts
Summary
Platform uses related control-plane concepts rather than a single tenant record for every concern. This page defines only concepts confirmed in source.
Audience
- Platform and customer administrators
- Implementation partners, developers, solution architects, and product owners
Purpose
Use these definitions when designing integrations, reviewing tenant changes, or interpreting administration and provisioning state.
Architecture
This is a conceptual relationship diagram, not a database schema.
Business concepts
| Concept | Purpose and ownership | Relationships and lifecycle relevance | Status |
|---|---|---|---|
| Tenant | Platform-owned configuration root with stable platform identity, tenant key, name, and status | Links control-plane records and anchors tenant-scoped administration | Implemented |
| Tenant key | Human-meaningful tenant identity used for lookup and context | Uniqueness is validated during creation and provisioning | Implemented |
| Platform client | Customer/control-plane record associated with tenant registration and commercial setup | Links subscriptions, licenses, entitlements, branding, and provisioning requests | Implemented; Transitional overlap with Tenant |
| Company | Tenant-owned legal, display, contact, locale, and regional profile | Created or updated during administration and provisioning | Implemented |
| Tenant metadata | Status, identifiers, domain state, settings, audit, and timeline information | Changes across onboarding and operations | Implemented |
| Branding | Client-linked visual and email presentation metadata | Established during provisioning and mutable through administration | Implemented |
| Configuration | Platform, service, or tenant-scoped settings and secret references | Supports defaults and tenant-level values without publishing secrets | Foundation / Implemented records |
| Plan | Versionable commercial package definition with configured features and limits | Selected by subscriptions | Implemented |
| Subscription | Tenant/client association with a plan and lifecycle state | Drives plan-derived feature access and commercial timing | Implemented |
| License | Client or tenant validity and capacity record | Evaluated with usage and grace state; related but distinct from packaging | Implemented; multiple models are Transitional |
| Feature entitlement | Plan inclusion or tenant-specific grant/deny/value | Evaluated against tenant and subscription state | Implemented |
| Feature flag | Tenant-scoped runtime on/off record | Materialized independently from catalog packaging | Implemented |
| Module | Tenant-scoped module enablement or catalog grouping | Derived or reconciled from effective access | Implemented; model overlap is Transitional |
| Usage and billing | Metering, charge, invoice, payment, and limit records | Relates subscriptions and licenses to reported consumption | Foundation / Implemented records and endpoints |
Technical implementation
The platform persistence context contains these aggregates and endpoint groups read or mutate them. Because Tenant and Platform Client, Client License and enterprise License, and catalog versus runtime feature records coexist, integrations should use the owning endpoint contract rather than treating similarly named concepts as interchangeable.
Source References
microservices/src/platform-service/Data/PlatformDbContext.csmicroservices/src/platform-service/Domain/Entities/Tenant.csmicroservices/src/platform-service/Domain/Entities/PlatformClient.csmicroservices/src/platform-service/Domain/Entities/Company.csmicroservices/src/platform-service/Domain/Entities/Plan.csmicroservices/src/platform-service/Domain/Entities/Subscription.csmicroservices/src/platform-service/Domain/Entities/License.csmicroservices/src/platform-service/Domain/Entities/Feature.csmicroservices/src/platform-service/Domain/Entities/TenantFeature.csmicroservices/src/platform-service/Domain/Entities/TenantBranding.cs
Related Articles
See Also
Keywords
- Tenant identity
- Platform client
- Commercial relationship
- Runtime controls
Revision Information
- Status: Draft
- Last reviewed: 2026-07-14
- Review cycle: Quarterly