Define how users navigate your application - multi-level screen structures, role-based paths + hierarchical data views that adapt to user permissions without separate builds per audience.
CAPABILITY OVERVIEW
One application, many user journeys.
Rayven's screen flows + hierarchies capability lets you define the navigation structure of any application built on the platform.
Configure multi-level screen hierarchies, conditional screen paths based on user role or Label + drill-down views that move from summary to detail. The same application layout serves different user groups with different navigation paths + data scopes - without building separate applications per audience.
Screen flows are configured using the visual builder + deploy across web, tablet + mobile interfaces without separate mobile builds.
Data sources feeding dashboards include:
User role + Label assignments (for conditional screen routing)
Live Cassandra + MySQL data (driving dynamic content per screen)
Workflow execution results (updating screen state in real time)
Form submissions + control widget actions (navigating between screens)
Outbound connections include:
Role-based screen path routing for different user audiences
Drill-down navigation from summary to entity-level detail views
Define parent and child screen relationships that create logical navigation structures across your application. Summary screens link to detail screens; operational overviews drill down to individual asset or entity views. Hierarchies are configured visually + adapt their content per user role and Label assignment.
Role-based screen paths
Configure different navigation paths for different user roles within the same application. An operator's journey through the app differs from a manager's or a compliance officer's - different screens are accessible, different data is visible + different actions are available, all within a single application configuration.
Label-filtered data views
Apply Label filters to screen content so each user sees only the data matching their Label assignment. A site manager sees their own site's screens. A client in a multi-tenant portal sees only their own records. The same screen template presents different scoped data per authenticated user.
Conditional screen logic
Show or hide screens + navigation elements based on runtime conditions - user role, data state, workflow outcome or user interaction. Screens can appear or disappear based on what's happening in the operation - for example, an exception screen that only appears when an alert is active.
Drill-down from summary to detail
Build applications where users navigate from an aggregate overview to progressively more detailed views - fleet to site to asset to reading level. Each screen in the hierarchy connects to the appropriate granularity of data for that level, maintaining context throughout the navigation path.
Mobile-responsive deployment
Screen flows adapt their layout to the device automatically. The same navigation structure and content hierarchy renders across desktop, tablet + mobile browser interfaces without separate mobile builds or parallel configuration. Breakpoints are configurable per screen.
HOW IT CONNECTS: EXPLAINER
Where Screen Fllows + Hierarchies fit in theRayven Platform stack.
Screen Flows + Hierarchies sit in the Presentation Layer as the navigation architecture layer above individual widgets + interface components.
Each screen in a hierarchy is a configured collection of widgets pulling from the Data Layer + Execution Layer.
Role + Label assignments in the Security Layer govern which screens each user can access and what data they see.
User navigation events between screens can trigger workflow events in the Execution Layer.
The same screen flow structure deploys across web + mobile interfaces without separate builds.
Asset monitoring application with drill-down navigation
An energy operator builds a fleet monitoring application with a three-level screen hierarchy: fleet overview (all 500 assets as KPI tiles) ? site view (assets per site with status indicators) ? asset detail (full telemetry, maintenance history + ML prediction for a single asset). Each level is a screen in the hierarchy. Users drill down from the fleet level with two clicks. Label filtering scopes each engineer's view to their assigned sites.
Multi-role facilities management portal
A facilities management firm builds one application serving three user groups with different screen paths. Technicians navigate to work order screens + field inspection forms. Supervisors navigate to team workload dashboards + approval queues. Clients navigate to service request submission + status tracking screens. All within the same application - role-based screen paths route each user to the correct starting point.
Partner building a white-label multi-client SaaS portal
An MSP builds a multi-tenant portal where each client has their own branded entry point. Label-based screen filtering ensures each client only navigates through their own data hierarchy - from a portfolio overview down to individual asset and event detail screens. The MSP manages one application configuration; each client experiences a purpose-built portal.
Rayven Screen Flows + Hierarchies FAQs:
A dashboard is a single-page view displaying multiple widgets simultaneously. A screen flow defines the navigation structure between multiple screens in an application. Dashboards are individual screens; screen flows define how users move between them, which screens are accessible per role + how data scopes change as users navigate.
Yes. Role-based screen paths route different user types to different starting screens, accessible navigation options + visible content - all within the same application configuration. An operator's navigation path, accessible screens + visible data differ from a manager's or client's without any separate build required.
Yes. Navigation events between screens can be configured to trigger workflow steps - for example, navigating to an asset detail screen can trigger a workflow that logs the view, updates a 'last accessed' timestamp or fetches fresh data from an external system.
Yes. Screen hierarchy configuration, role-based path definitions, Label filters + conditional screen logic are all set within the visual builder without code. HTML + JavaScript is available for advanced interface behaviours within individual screens where bespoke interaction is required.
There is no hard limit on the number of levels in a screen hierarchy. Practical application design typically uses two to five levels - from aggregate overview to granular entity detail. Deeper hierarchies are supported where the use case requires it.
Yes. Screen flows deploy across web, tablet + mobile browser interfaces using the same configuration. Layouts adapt automatically to screen size using configurable breakpoints. No separate mobile build is required for the same screen flow to work across all devices.
Yes. Conditional screen visibility rules can evaluate data conditions, workflow outcomes + user interactions to determine which screens appear in the navigation. An exception screen can appear only when an active alert exists; a summary screen can show or hide based on whether data meets a threshold.
Shared component patterns can be applied across multiple Rayven application instances. For multi-tenant deployments, the same screen flow configuration serves multiple clients with Label-based data isolation, eliminating the need to maintain separate configurations per client.
User navigation events that trigger workflow steps are logged as workflow execution records in Cassandra. For applications where tracking user journeys + data access patterns is a compliance requirement, workflow-based audit logging captures the relevant events with user identity + timestamp.
Application screens have configurable URL structures that support direct navigation to specific screens within a hierarchy. This enables deep-linking from external systems, bookmarking of frequently accessed views + URL-based navigation from notifications or external communications.
/Website%202026/Industries%202026/Manufacturing/Manufacturing%20Images%202026/Manufacturing-Leader.webp?width=338&height=561&name=Manufacturing-Leader.webp "Manufacturing-Leader")
