Runtime fingerprintToken readout from the active provider chain.
Live DS
Runtime
PlatformRottay
Rottay / ModernPlatform Flagship
Primary
#FFFFFFSecondary #A0A0A5
Radius
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
#FFFFFFRottay
Chrome
Modernrenderer posture
Radius
14pxsurface shape
Density
normalPlatform Flagship
Back to Platform
Permissions3 scenario rowsTier mix 1P / 1S / 13Pr
Scenario summary
Permissions in Platform is about controlled clarity, not ornamental UI.
Permissions are the governance heart of the platform, where safety, discoverability, and policy confidence need to coexist. 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 archetypeOperational indexThe prevailing interaction shape across these modules.
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
Role Manager
Role list with permission counts, user assignments, and hierarchy view.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix1P / 1S / 3Pr
Inspect forCheck whether scanning rhythm, action placement, and row density still feel safe and fast.
Supporting partsRepresentative pieces behind this scenario lane.
PatternDataTable
CollectionHeader
Tree
Badge
+1 more
02
Scenario module
Permission Matrix
Grid view of resource-action permissions with toggle controls.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix0P / 0S / 5Pr
Inspect forCheck whether scanning rhythm, action placement, and row density still feel safe and fast.
Supporting partsRepresentative pieces behind this scenario lane.
Table
Checkbox
Tag
Tooltip
+1 more
03
Scenario module
Policy Editor
Policy rule builder with conditions, actions, and effect preview.
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.
Supporting partsRepresentative pieces behind this scenario lane.
Operational admin patterns for the flagship platform experience.
Runtime controls
TenantRottay
EngineModern
Operators
SecurityAdminsCompliance owners
The category has to stay legible for these roles even when a different tenant runtime shifts density or contrast.
Tempo and pressureLow-frequency but high-risk configurationUse the scenario rows below to verify that hierarchy and control placement still hold up at this pace.
Design principles3 guardrails
Principle 01Show blast radius before save.
Principle 02Group resources into mental models, not raw IDs.
Principle 03Make inherited state visible.
Active provider
Runtime audit
Rottay is rendering this appendix.
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
PlatformRottay
Rottay / ModernPlatform Flagship
Primary
#FFFFFFSecondary #A0A0A5
Radius
Compact runtime evidence across 3+ token signals.
14pxxl 18px
Density
normalBorder-light cards
Accent
Badge
roundedtop bar ยท solid dividers
Motion
springHover lift 2px
Keep stablePermissions still needs to feel native for Security, Admins, and 1 more even while the provider changes the surrounding chrome.
Stress pointLow-frequency but high-risk configuration 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.