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
Identity
Identity
Active profilePlatform Flagship
Runtime postureRottay / modern
Operational admin patterns for the flagship platform experience.
Runtime controls
TenantRottay
Back to Platform
Identity
4 scenario rows
Tier mix 2P / 5S / 13Pr
Scenario summary
Identity in Platform is about controlled clarity, not ornamental UI.
Platform identity surfaces are about trust at scale: fast lookup, stable user context, and clear control over sessions and profile state. The workflow stays Platform-specific, but the live rendering should still come from the active docs runtime rather than a local preset.
Scenario rows4Named modules that anchor this category's product story.
Unique parts18Distinct structures, patterns, and primitives in this category.
Dominant archetypeOperational indexThe prevailing interaction shape across these modules.
Operators
Admins
Support
Security teams
The category has to stay legible for these roles even when a different tenant runtime shifts density or contrast.
Tempo and pressure
High-frequency operational review
Use the scenario rows below to verify that hierarchy and control placement still hold up at this pace.
Design principles
3 guardrails
Principle 01Keep user state obvious.
Principle 02Make account actions reversible when possible.
Principle 03Surface role and session context early.
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
User List
Paginated user table with search, filters, bulk actions, and role badges.
Composition balanceStructure-led compositionA quick read on which layer is carrying most of the scenario weight.
Tier mix1P / 2S / 2Pr
Inspect forCheck whether scanning rhythm, action placement, and row density still feel safe and fast.
02
Scenario module
User Detail
User profile view with activity timeline, session list, and edit form.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix0P / 2S / 3Pr
Inspect forCheck whether grouping, spacing, and field hierarchy still feel calm when the runtime changes.
03
Scenario module
Profile Settings
Self-service profile editor with avatar upload and MFA configuration.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix0P / 1S / 4Pr
Inspect forCheck whether grouping, spacing, and field hierarchy still feel calm when the runtime changes.
04
Scenario module
Session Manager
Active session list with device info, location, and revoke actions.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix1P / 0S / 4Pr
Inspect forCheck whether scanning rhythm, action placement, and row density still feel safe and fast.
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 stableIdentity still needs to feel native for Admins, Support, and 1 more even while the provider changes the surrounding chrome.
Stress pointHigh-frequency operational review means hierarchy, action placement, and contrast cannot become ambiguous under a different runtime.
Read as one laneOperational index should feel like one coherent chapter here rather than a stack of isolated component demos.