Runtime fingerprintToken readout from the active provider chain.
Live DS
Runtime
Platform
Rottay
Rottay / ModernPlatform Flagship
Primary
#0A0A0ASecondary #6B6B6B
Radius
14pxxl 18px
Density
normalBorder-light cards
Accent
Badge
Compact runtime evidence across 3+ token signals.
Published DS package · Tenant Showcase · Rottay / modernShared route metadata for the active runtime, kept inline so the shell reads like a thin header band.
Palette
#0A0A0ARottay
Chrome
Modernrenderer posture
Radius
14pxsurface shape
Density
normalPlatform Flagship
Platform
Tenancy
Tenancy
Active profilePlatform Flagship
Runtime postureRottay / modern
Operational admin patterns for the flagship platform experience.
Runtime controls
TenantRottay
Back to Platform
Tenancy
3 scenario rows
Tier mix 1P / 2S / 12Pr
Scenario summary
Tenancy in Platform is about controlled clarity, not ornamental UI.
Tenancy views carry the white-label promise of the platform: each customer has branding, billing, domains, and lifecycle state that operators must govern safely. The workflow stays Platform-specific, but the live rendering should still come from the active docs runtime rather than a local preset.
Scenario rows3Named modules that anchor this category's product story.
Unique parts14Distinct structures, patterns, and primitives in this category.
Dominant archetypeAnalytics surfaceThe prevailing interaction shape across these modules.
Operators
Platform ops
Customer success
Billing admins
The category has to stay legible for these roles even when a different tenant runtime shifts density or contrast.
Tempo and pressure
Periodic configuration plus exception handling
Use the scenario rows below to verify that hierarchy and control placement still hold up at this pace.
Design principles
3 guardrails
Principle 01Show tenant identity before controls.
Principle 02Separate billing from brand setup.
Principle 03Make environment state auditable.
Scenario rows
Scenario modules
Each row below captures a product-grade module, the component spread behind it, and what to scrutinize when the runtime changes.
Read orderStart with the title and archetype, then inspect composition balance and the part sample.
Proof checkConfirm the lane still reads like one product module after the runtime changes tone, density, and contrast.
01
Scenario module
Tenant List
Multi-tenant directory with plan badges, usage stats, and quick actions.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix1P / 1S / 3Pr
Inspect forCheck whether chart emphasis, contrast, and labels stay legible under the active provider.
02
Scenario module
Tenant Settings
Company profile editor with branding, billing, and domain configuration.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix0P / 0S / 5Pr
Inspect forCheck whether grouping, spacing, and field hierarchy still feel calm when the runtime changes.
03
Scenario module
Tenant Dashboard
Usage metrics, subscription status, and resource consumption overview.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix0P / 1S / 4Pr
Inspect forCheck whether chart emphasis, contrast, and labels stay legible under the active provider.
Use this page as a reference sheet: the scenario modules stay constant, while contrast, shell tone, and component personality respond to the active docs runtime.
Runtime
Platform
Rottay
Rottay / ModernPlatform Flagship
Primary
#0A0A0ASecondary #6B6B6B
Radius
14pxxl 18px
Density
normalBorder-light cards
Accent
Badge
Motion
Compact runtime evidence across 3+ token signals.
roundedtop bar · solid dividers
springHover lift 2px
Keep stableTenancy still needs to feel native for Platform ops, Customer success, and 1 more even while the provider changes the surrounding chrome.
Stress pointPeriodic configuration plus exception handling means hierarchy, action placement, and contrast cannot become ambiguous under a different runtime.
Read as one laneAnalytics surface should feel like one coherent chapter here rather than a stack of isolated component demos.