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
Auth
Auth
Active profilePlatform Flagship
Runtime postureRottay / modern
Operational admin patterns for the flagship platform experience.
Runtime controls
TenantRottay
Back to Platform
Auth
4 scenario rows
Tier mix 1P / 0S / 19Pr
Scenario summary
Auth in Platform is about controlled clarity, not ornamental UI.
Auth surfaces set the tone for platform credibility. They need to feel secure, legible, and unforgiving about ambiguity while still remaining humane. 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 parts14Distinct structures, patterns, and primitives in this category.
Dominant archetypeConfiguration flowThe prevailing interaction shape across these modules.
Operators
End users
Security admins
Integrations teams
The category has to stay legible for these roles even when a different tenant runtime shifts density or contrast.
Tempo and pressure
Entry-point and exception-driven
Use the scenario rows below to verify that hierarchy and control placement still hold up at this pace.
Design principles
3 guardrails
Principle 01Keep trust signals visible.
Principle 02Favor step clarity over visual novelty.
Principle 03Separate credential management from identity profile tasks.
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
Login Flow
Email/password login with social providers and remember-me toggle.
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.
02
Scenario module
MFA Setup
TOTP setup wizard with QR code, backup codes, and verification step.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix0P / 0S / 5Pr
Inspect forCheck whether sequence, progress cues, and handoff points remain easy to follow.
03
Scenario module
Password Reset
Password reset request and confirmation with strength indicator.
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.
04
Scenario module
API Key Admin
API key generation, rotation, and scope management for integrations.
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 stableAuth still needs to feel native for End users, Security admins, and 1 more even while the provider changes the surrounding chrome.
Stress pointEntry-point and exception-driven means hierarchy, action placement, and contrast cannot become ambiguous under a different runtime.
Read as one laneConfiguration flow should feel like one coherent chapter here rather than a stack of isolated component demos.