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
BitHire
Workflows
Workflows
Active profilePlatform Flagship
Runtime postureRottay / modern
Recruiting-focused adaptations of the shared design system.
Runtime controls
TenantRottay
Back to BitHire
Workflows
3 scenario rows
Tier mix 0P / 0S / 15Pr
Scenario summary
Workflows in BitHire is built for speed, visibility, and decision support.
Workflow tooling scales recruiting operations by encoding repeatable transitions, notifications, and automation rules directly into the product. These scenarios stay BitHire-specific in workflow and copy, but the live visuals should still come from the active docs runtime instead of a local preset.
Scenario rows3Named modules that anchor this category's product story.
Unique parts9Distinct structures, patterns, and primitives in this category.
Dominant archetypeTask moduleThe prevailing interaction shape across these modules.
Operators
Talent ops
Recruiters
Admins
The category has to stay legible for these roles even when a different tenant runtime shifts density or contrast.
Tempo and pressure
Rule-based process optimization
Use the scenario rows below to verify that hierarchy and control placement still hold up at this pace.
Design principles
3 guardrails
Principle 01Make automations inspectable.
Principle 02Keep transition logic discoverable.
Principle 03Treat notifications as part of the workflow, not an afterthought.
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
Workflow Builder
Visual workflow editor with drag-and-drop stages, conditions, and action nodes.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix0P / 0S / 5Pr
Inspect forCheck whether the module still feels product-grade rather than like an isolated component demo.
02
Scenario module
Stage Transitions
Configurable stage transition rules with guard conditions and auto-actions.
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
Notification Rules
Event-driven notification configuration with templates and channel routing.
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.
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 stableWorkflows still needs to feel native for Talent ops, Recruiters, and 1 more even while the provider changes the surrounding chrome.
Stress pointRule-based process optimization means hierarchy, action placement, and contrast cannot become ambiguous under a different runtime.
Read as one laneTask module should feel like one coherent chapter here rather than a stack of isolated component demos.